Skip to end of metadata
Go to start of metadata

Overview

The Jenkins Artifactory Plugin supports Ivy build jobs, allowing your build jobs deploy artifacts and resolve dependencies to and from Artifactory, and then have them linked to the build job that created them. 

As described below, using the   Jenkins Ivy Plugin together with the Jenkins Artifactory Plugin your Ivy builds will publish artifacts and build information to Artifactory whenever an ivy:publish task is executed.

Install the Jenkins Ivy Plugin

 To use the Jenkins Artifactory Plugin with Ivy builds you need to install the Jenkins Ivy Plugin

JDK compatibility

From version 3.0.0, the plugin no longer supports building with JDK 7.


Publishing to your local file cache repository is the best way to go (i.e. you do not need to publish to Artifactory). The plugin will intercept the publish events and will replay them against Artifactory according to the configuration. Using an ivy:publish task that publishes directly to Artifactory will result in (redundant) double publishing.

Page Contents

Integration Benefits


Configuring Ivy-Ant Builds


Artifactory Server
Artifactory server as defined in the Artifactory plugin configuration. The selected server will be used for artifacts resolution and build info deployment.
Target releases repository

Repository to deploy release artifacts to.

Using the text mode will enable you to also use placeholders for environment variable which will be replaced with your environment value at build time.

Override default credentials
Override default credentials.
Override build name

Override Artifactory default build name.

Publish artifacts to Artifactory
Check if you wish to publish produced build artifacts to Artifactory.
Use Maven compatible patterns
Whether to use the default Maven patterns when publishing artifacts and Ivy descriptors, or to use custom patterns. Dots in [organization] will be converted to slashes on path transformation.
Ivy pattern
The pattern to use for published Ivy descriptors.
Artifact pattern
The pattern to use for published artifacts.
Filter excluded artifacts from build Info
Add the excluded files to the excludedArtifacts list and remove them from the artifacts list in the build info.
Deployment properties
Semicolon-separated list of properties to attach to all deployed artifacts in addition to the default ones (build.name, build.number, vcs.revision, etc.).
Property values can take environment variables.
For example: p4.cl=${P4_CHANGELIST};buildStatus=RC;platforms=win386,win64,osx,debian
Capture and publish build info

Publish build information to Artifactory.

Include environment variables
Check if you wish to include all environment variables accessible by the builds process. Jenkins-specific EnvVars are always included. Note: including all environment variables as part of the captured build information may result in very large build objects and may slow down deployment.
Discard old builds from Artifactory (requires Artifactory Pro)
Automatically remove old builds stored in Artifactory according to Jenkins’s configured policy for discarding old builds.

Build Configuration


  • No labels