Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


The Respository Connector Plugin can be used for example to deploy artifacts to target servers and it uses the Sonatype's Aether API internally to resolve artifacts from a repository and to determine the sorting order of version listsversions.


The build parameter 'Maven Repository Artifact' can be used for allows easy version selection and the build step 'Artifact Resolver' to lets you download the artifact from the a Maven repository without the need to install Maven.

It is possible to use the version selection feature of this plugin alone and let a Maven POM do the artifact download, or you let Jenkins also do the download before a script is invoked. The way you use the plugin is completely up to you.

Using only the version selection feature only makes sense when you have Maven installed anyway and you want to have all aspects of the artifact processing under version control . That basically means you let the job just select the version and leave the task to download the artifact and to deploy it to a target server(see example below)

Version Selection

String Parameter


The 'Artifact Resolver' build step allows you to download the specified artifact in a build step. The location where the artifact is downloaded to can be specified by the parameters "target directory" and "target filename":

Image Modified

Global Configuration

The repositories to resolve the artifacts from, can be configured in Jenkins' global configuration section:

Image Modified


The following Maven POM downloads the artifact, and passes the path to the artifact to a shell script for further processing. The shell script also gets an environment parameter which comes from a "Choice Paramater" to determine the target environment on which to deploy the artifact.

Code Block
titleExample deployment POM
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="" xmlns:xsi=""
  <name>Maven deployment template</name>

	<!-- The selected version is currently set as the name of the repository, given for the Maven repository -->






			    <!-- dump all available properties -->
			    <echoproperties />
                <exec dir="." executable="cmd" osfamily="windows">
                  <arg value="/c"/>
                  <arg value="deploy.cmd ${} ${environment} ${distversion}"/>
                <exec dir="." executable="/bin/bash" osfamily="unix">
                  <arg value="-c"/>
                  <arg value="./ ${} ${environment} ${distversion}"/>

Help and Support

Jira Issues
titleOpen issues

For Help and support please use the Jenkins Users mailing list.
The comment list below is not monitored.

Version History

1.1.1 (28. Feb 2015)

1.1.0 (2. Feb 2015)

1.0.1 (16. Aug. 2014)

1.0.0 (18. July 2014)

  • fix JENKINS-17541 target directory does not expand token macro parameters
  • integrate PR #3 (thanks to mrumpf!)
    • Sort the list of Maven repositories in the global configuration page
    • Added I18N and translated all help files and texts to german
    • Extracted the global configuration from the ArtifactResolver and moved it into the central class GlobalConfiguration
    • Added the version selection build parameter
    • When your ArtifactResolver build step and the build parameter is used in one job, the version, selected by the builld parameter overrides the version of the ArtifactResolver build step.
    • Added proxy support which makes the plugin usable in corporate environments

0.8.2 (18. Feb. 2012)

0.8.0 (18. Sep. 2011)

  • add support for variable resolving in configuration


  • update to aether 1.12 and fix a classloader issue


  • update to aether 1.11 and fix update policy issue


  • now supports to configure the repository update policy (for earch builder individually)


  • Inital