Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

Plugin Information

View Repository Connector on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

Repository Connector adds features around resolving artifacts from a Maven repository like Nexus or Artifactory.

When installing this plugin, you'll get an additional build parameter 'Maven Repository Artifact' and a build step called 'Artifact Resolver'.


The build parameter 'Maven Repository Artifact' can be used for version selection and the build step 'Artifact Resolver' to download the artifact from the 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 let Jenkins also do the download before a script is invoked. The way you use the plugin is completely up to you.

Using 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

Version Selection

String Parameter

You can use a simple string build parameter (e.g. 'VERSION') to enter a version as free text:

  • 1.0.0 - a regular version
  • RELEASE - the latest release version
  • LATEST - the latest version, which is usually a SNAPSHOT version
  • [0-SNAPSHOT,) - a version range

This string parameter can be used in the later stages of the job by specifying the property ${VERSION}. It can even be used in the version field of the Artifact Resolver build step.

Maven Repository Artifact Parameter

The version selection feature is provided by the build parameter 'Maven Respository Artifact':

When you click on "Build with Parameters" you will see a drop-down box with all the versions that have been found in the Maven repository.

The special versions "LATEST" and "RELEASE" are added to the list where the latter is the default selection (see JENKINS-28323).

The selected version is passed in 2 properties to the build:

  • <groupId>.<artifactId>=<version> (e.g. "commons-collections.commons-collections=1.0.0")
  • <global-repo-name>=<version> (e.g. "central=1.0.0")

Respository Connector uses sonatypes aether api to resolve artifacts from a repository.



...instead of a fix version, you can also use 'RELEASE' or 'LATEST' to identify the newest release or the latest build of an artifact. Version ranges are supported too, e.g. [0-SNAPSHOT,)

one is also able to define a job as parametrized and use the parameter within each field in the config - e.g. define a string parameter called 'VERSION' and use it as ${VERSION}

within the Version field in the config.


The repositories to resolve the artifacts from, can be configured in global config:

Help and Support

type key summary

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

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
  • No labels