Artifactory provides tight integration with Bamboo through the Bamboo Artifactory Plug-in. Beyond managing efficient deployment of your artifacts to Artifactory, the plug-in lets you capture information about artifacts deployed, dependencies resolved, environment data associated with the Bamboo build runs and more, that effectively facilitates fully traceable builds.
From version 1.4.0 the Bamboo Artifactory Plug-in provides powerful features for release management and promotion. For details please refer to Bamboo Artifactory Plugin - Release Management.
Build Runner Support
The Bamboo Artifactory Plug-in currently provides full support for Maven 3, Gradle and Ivy builds. Generic Deployment Tasks are available for all builder types.
Installing the Plug-in
Download the latest version of the plugin according to the compatibility matrix below:
Plugins are deployed to Bamboo by placing the packaged plugin into the
For more details please refer to the Bamboo documentation for Installing a New Plugin.
To use the Bamboo Artifactory plug-in you need to set up your Artifactory server(s) in Bamboo's server configuration. You can then set up a project builder to deploy artifacts and build-info to a repository on one of the configured Artifactory servers.
Configuring Maven 3, Gradle and Ivy Builders
Before you begin with any Artifactory-specific setup, ensure that Maven 3, Gradle and/or Ivy builders are available for project configurations.
These builders are defined as Server Capabilities in Bamboo
To define Server Capabilities for builders:
Configuring System-wide Artifactory Server(s)
To make Artifactory servers available to project configurations, they must be defined under Administration | Plugins | Artifactory Plugin.
Enter the Artifactory server URL in the Add New Server Configuration fields.
Configuring a Project Builder
To set up a project task to deploy build-info and artifacts to Artifactory:
Selecting Artifactory Servers and Repositories
Select an Artifactory server URL for resolving artifacts and to deploy build artifacts in the corresponding fields.
If you have configured the System Wide Artifactory Servers correctly with the required credentials, then once you select an Artifactory server, the corresponding fields are populated to let you choose a Resolution Repository and Target Repository.
The Target Repository field is populated with a list of available target repositories as returned by the server (queried with the credentials in the server configuration, if provided).
If the repository list remains empty, ensure the specified Artifactory server URL and credentials (if provided) are valid.
Select the target repository you want Bamboo to deploy artifacts and build-info to.
Running Licence Checks
If you have an Artifactory Pro license, you can set the Run License Checks checkbox so that Artifactory will scan all dependencies used by the build to check for any license violations.
This feature offers the following options:
Black Duck Code Center Integration
If you have an Artifactory Pro license, and a Black Duck Code Center account you can use the Artifactory Black Duck Code Center integration to automatically initiate an open source component approval process, and proactively monitor for security vulnerabilities.
This feature offers the following options:
Artifactory Generic Resolve Task
The Generic Resolve task can be used in any job with any combination of tasks.
The resolved files will be clustered as dependencies in the Build information.
Artifactory Generic Deploy Task
The Generic Deploy task can be used in any job with any combination of tasks, and is provided to offer minimal Build Info support for all types.
This task collects all available information regarding the build from Bamboo, and provides a deployment mechanism for the artifacts produced.
Adding the Generic Deploy task automatically deploys Build Info collected from the Published Artifacts declaration in addition to the artifacts themselves.
In addition to specifying the Artifactory Server URL, the Target Repository and the Deployer username and Password, you can specify the following parameters:
The 'Published Artifacts' declaration lets you specify which artifact files produced by the build are published to Artifactory. At build conclusion, the plugin locates artifacts in the build's checkout directory according to the specified artifact patterns and publishes them to Artifactory, optionally applying mapping for the target path of each deployed artifact.
Attaching Searchable Parameters
You can define parameters that should be attached to build info and artifacts that are deployed by the plugin.
To define a parameter, under Administrationת go to Build Resources | Global Variables, fill in a Key/Value pair and click Save.
The available parameter types are:
Using a Properties File
Instead of defining properties manually, you can point the plug-in to a properties file.
To do so, define a property named
You can also configure Bamboo to manage releases through Artifactory. If you set the Enable Release Management checkbox, you can configure the following fields:
Running a Build
Once you have completed setting up a project builder you can run it. The Artifactory plug-in commences at the end of the build and:
You can also link directly to the information in Artifactory from a build run view in Bamboo:
The Bamboo Artifactory plug-in is available under the Apache v2 License.
Click to see change log details
1.7.1 (26 MAY 2014)
1.7.0 (06 Apr 2014)
1.6.2 (24 Nov 2013)
1.6.1 (03 Oct 2013)
1.6.0 (16 Jul 2013)
1.5.6 (03 Sep 2013)
1.5.5 (03 Sep 2012)
1.5.4 (25 Jun 2012)
1.5.3 (02 Apr 2012)
1.5.2 (02 Apr 2012)
1.5.1 (05 Jan 2012)
1.5.0 (11 Dec 2011)
1.4.2 (19 Sep 2011)
1.4.1 (01 Aug 2011)
1.4.0 (14 Jul 2011)
1.3.2 (14 Jun 2011)
1.3.1 (13 Jun 2011)
1.3.0 (30 May 2011)
1.2.0 (2 Mar 2011)
1.0.3 (21 Nov 2010)
1.0.2 (7 Nov 2010)