Jenkins : Pipeline Classpath Step Plugin

Plugin Information
Distribution of this plugin has been suspended due to unresolved security vulnerabilities, see below.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

Pipeline DSL step to add path to the groovy classpath

Features

From your pipeline groovy code, call addToClasspath <path>. This will add a directory to the groovy classpath, allowing you to do things like import groovy classes. The [tests contain an example|https://github.com/jenkinsci/pipeline-classpath-step-plugin/blob/f61f6d4a9ad4b53a2bbbe128069ca5cd10ed15bf/src/test/java/cprice404/plugins/workflow/steps/AddToClasspathStepTest.java#L35-L40] of what usage might look like.

Because of the way that pipeline scripts are loaded by Jenkins, it's not currently possible to use this step *and* do an import from your main Jenkinsfile / pipeline script. You *can* call addToClasspath from that script, and then call load to load other scripts. The loaded scripts will be able to use import and similar statements. There is a branch in the github repo which contains [a test illustrating this limitation|https://github.com/jenkinsci/pipeline-classpath-step-plugin/blob/7a799452ee3412bcbeb3dd51d4ca41996f8030bf/src/test/java/cprice404/plugins/workflow/steps/AddToClasspathStepTest.java#L35-L36], and it's something I'd like to provide a solution for in a future release if the upstream doesn't come up with a more elegant solution.