Before You Begin

Setting-up Jenkins/Hudson

The Jenkins/Hudson Plug-in

To integrate with Jenkins you must install the OSS Artifactory Jenkins Plug-in from Jenkins's Plug-ins Manager.

The plug-in provides:

• Easy setup for deploying to Artifactory.
• Enhanced deployment transferring additional important build information to Artifactory.
• UI integration allowing moving from a Jenkins build directly to Artifactory.
• Release Management with Staging and Promotion.

Supported Build Technologies:
The plug-in currently supports: Maven 3, Maven 2, Gradle, and Ivy/Ant builds.

Installing and Configuring the Plug-in

To install the Jenkins Artifactory plug-in please follow the instructions on the Jenkins's Plug-in Center.

The configuration involves two steps:

1. Setting up Jenkins to recognize your Artifactory server
2. Pointing a Jenkins build at a target local repository in Artifactory to which it should deploy the build artifacts - Jenkins queries Artifactory's available target repositories using Artifactory's REST API and allows you to select one.

It is recommended that you also configure Jenkins to use Artifactory for dependency resolution.

This is currently not part of the plug-in and is performed in the regular way that a build is configured, typically by changing the settings.xml or the ivysettings.xml.xml of the user running Jenkins.

Navigating Between Jenkins and Artifactory

Each build viewed in Artifactory corresponds to its Jenkins job counterpart and contains a build history of all runs, that reflect the build history in Jenkins:

For each build item in the history you can drill down and obtain more details about it.

You can also view the build in the CI server by selecting 'Show in CI Server'.

You can also navigate back to Artifactory from Jenkins, as shown below: