Before You Begin
The Bamboo Artifactory plug-in brings CI Build Integration to Bamboo users, allowing the capture of information about deployed artifacts, resolved dependencies and environment data associated with Bamboo build runs. In addition, you have full traceability for your builds.
The plug-in also efficiently deploys your artifacts to Artifactory.
Installing the Plug-in
Download the latest version of the plugin:
To use the Bamboo Artifactory plug-in you must configure 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.
To define build capabilities as standard:
Configuring System-wide Artifactory Server(s)
To make Artifactory servers available to project configurations, they must be defined under
NOTE! that username and password are optional and only used when querying Artifactory's REST API for a list of configured repositories (credentials are only required if the target instance does not allow anonymous access).
Configuring a Project Builder
To set up a project task to deploy build-info and artifacts to Artifactory:
Selecting an Artifactory Server URL
The 'Target Repository' list 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 License Checks
Use the Artifactory Pro License Control feature to discover and handle third party dependency licensing issues as part of the build.
Check the 'Run License Checks' checkbox if you want Artifactory to scan and check the licenses of all dependencies used by this build.
If you want to inform selected users about any license violations detected while scanning, enter a list of e-mail addresses to the notification recipients text box.
Use the Artifactory Black Duck Code Center integration to automated, non-invasive approach to the open source component approval process, in addition to proactively monitoring for security vulnerabilities.
Generic (Freestyle) Deploy Tasks
The Generic Deploy task can be used in any job with any combination of tasks; made to provide minimal Build Info support for all types, the task collects all available information from Bamboo regarding the build and provides a deployment mechanism for produced artifacts.
Adding the Generic Deploy task automatically deploys Build Info including artifacts collected from the Published Artifacts declaration.
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 to Build-Info and Artifacts Deployed by the Plug-in
To define a parameter complete the blank parameter row and click "Save".
The available parameter types are:
It is also possible to point the plug-in to a properties file containing the aforementioned properties.
To point to such a file, define a property named
Running a Build with the Artifactory Plug-in
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.
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.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)