External Resource Dispatcher

compared with
Current by Robert Sandell
on Aug 06, 2013 11:49.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (5)

View Page History
{jenkins-plugin-info:externalresource-dispatcher|jiraComponent=external-resource-dispatcher}
{jenkins-plugin-info:externalresource-dispatcher|jiraComponent=external-resource-dispatcher|sourceDir=external-resource-dispatcher-plugin}
{excerpt}This plugin adds support for external resources in Jenkins. An external resource is something external
attached to a Jenkins slave and can be locked by a build, which thus gets exclusive access to it, then released after the
build is done. Examples of external resources are phones, printers and USB christmas trees.
{excerpt}
*Note that even though the 'b' fell off in the latest release, this plugin is still considered to be in beta stage.*

h2. Quick usage guide

For a build with a locked resource, we expose all the properties of the resource as environment variables, with the names:
MD_name_of_the_property. MD_EXTERNAL_RESOURCES_LOCKED\__NAME_OF_THE_PROPERTY_IN_CAPS_. These can be used to refer to the locked resource from build steps.

h2. Administrator settings
Requires that the user has the LockRelease permission set for the node that the resource is on.

h3. Integration with the Build Flow Plugin

There is an extension point for [JENKINS:Build Flow Plugin] that can be used for easy access to the resource manager from within the build flow script like:

{code}
def manager = extension.'externalresource-dispatcher'
manager.lock(...)
{code}

h3. Change Log