External workspace manager plugin archive#
External workspace manager plugin code#

If populated, the global configuration will be used. In other words, it matches the most recent stable build of the same

The template element values match the corresponding build parameter values.

It defines build parameters names that match the template element names between jobName and buildNumber.

The search is linear and goes from the most recent build in history,Īll the way to the oldest build in existence, or until a matching build

Variables are used to search the history for builds matching these The plugin uses a template to compute the workspace value. Is the current build number rather than the upstream build number. Job (not the upstream job) rather than after the upstream job, and the build number When a copy is made, the workspace path is simply named after the current In this case, you can specify the copy: true option: def workspace = externalWorkspace root: '/root/path', upstream: 'builder', copy: true An example of this situation is when you need to run multipleĬoncurrent downstream builds. However, there are cases where taking a copy of the other job workspace is

External workspace manager plugin code#

It does not make much sense to hard code a build number value, but aīuild parameter value can be passed as well: def workspace = externalWorkspace root: '/root/path', upstream: 'builder', buildNumber: UPSTREAM_BUILD_NUMBERīy default, this plugin allows a job to run using another job's workspace. Thisīehavior can be changed by passing a specific build number to the plugin: def workspace = externalWorkspace root: '/root/path', upstream: 'builder', buildNumber: '13' Stable upstream build number is used when computing the workspace. Changing the upstream build numberīy default, when the upstream argument is specified, the most recent Stable build, an exception is thrown and the build fails. If the history of the upstream job does not contain at least one If the upstream job does not exist, an exception is thrown and the buildįails. The most recent stable upstream workspace.

So when specifying the upstream argument, the downstream build uses

The most recent upstream stable build number is used instead of the current (downstream) job build number.

The name of the upstream job is used instead of the name of the current (downstream) job.

When the upstream argument is specified, two important things happen build something on /root/path/$upstream/$mostRecentUpstreamStableBuildNumber Then set the path as shown above when allocating the workspace for The upstream job when the plugin is instantiated by the downstream job: // downstream jobĭef workspace = externalWorkspace root: '/root/path', upstream: 'builder' To reuse the same workspace in a downstream job, specify the name of $JOB_NAME also includes the folder name(s). Is builder and the BUILD_NUMBER is 12, then the workspace is To the workspace path, resulting in the folowing workspace path: The plugin automatically adds the job name and the build number build something on /root/path/$JOB_NAME/$BUILD_NUMBER The workspace is computed by calling the workspace.path method whenĪllocating the workspace for the node using the ws() step. This plugin is initially written for Pipeline jobs, so all examples areįirst the plugin is instantiated in a Pipeline script: // upstream jobĭef workspace = externalWorkspace root: '/root/path' To that effect to the build result page of the corresponding builds. When a workspace has been shared between builds, this plugin adds a note This plugin is only concerned about workspace sharing, and not about

The workspace path can be computed with a user configurable template.

It allows jobs which are NOT linked, triggered, or in a pipeline, to share or reuse the same workspace.

It provides a persistent default workspace unique to each build.

This differs from the Jenkins build-in custom workspace feature in the Scenarios such as Git pull-request delivery pipelines.

External workspace manager plugin archive#

ItĮliminates the need to copy, archive or move files in some common Itįacilitates workspace share and reuse across jobs and builds. This plugin implements an external workspace management system. The rest of the document is here for reference only. This is the ORIGINAL proposal for the external workspace manager plugin for Jenkins, the ACTUAL plugin is a Google Summer of Code Project under the Jenkins organization.