Using Artifactory 6.x ?
JFrog Artifactory 6.x User Guide

Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata



Artifactory provides tight integration with Bamboo through the Bamboo Artifactory Plug-in. Beyond managingefficientdeployment 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.

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.

Before you begin

Please refer to the general information about Artifactory's Build Integration before using the Bamboo Artifactory Plug-in.

Source Code Available!

The Bamboo Artifactory Plugin is an open-source project on GitHub which you can freely browse and fork.


Plugin Compatibility:

The Bamboo Artifactory Plugin is fully tested for compatibility with the version of Bamboo that is current when the plugin is released. When a new version of Bamboo is released, the Marketplace lists the Bamboo Artifactory Plugin as incompatible, however, since we regularly update the plugin it is likely to maintain compatibility with patch or minor version upgrades of Bamboo. We recommend testing new Bamboo and plugins releases on a staging environment before upgrading the production environment.


Download version 2.4.1 which is compatible with Bamboo 6.2.5 and above.

Upgrading to version 2.x from version 1.x of the plugin requires new installation steps. Please refer to Installing the Plugin for more details.


VersionDownload linkCompatibility
2.3.0DownloadBamboo 6.2.x
2.2.0DownloadBamboo 6.1.x
2.1.1DownloadBamboo 6.0.x
2.1.0DownloadBamboo 5.14.x
1.13.0DownloadBamboo 5.14.x
1.11.2Download Bamboo 5.13.x
1.11.1Download Bamboo 5.12.x
1.10.3Download Bamboo 5.11.x
1.10.1 Download Bamboo 5.10.x
1.9.2 DownloadBamboo 5.9.x
1.7.7 Download Bamboo 5.8.x


Installing the Plugin


  • Artifactory 2.2.5 or later. For best results and optimized communication, we recommend using the latest version of Artifactory.
  • Artifactory Pro is required for advanced features, such as License Control and enhanced Build Integration.
  • Maven 3.
  • Gradle 0.9 or later.
  • Ant and Ivy 2.1.0 or later.

Upgrading to Versions 2.x from Versions 1.x

If you are currently using a version of the plugin below 2.0.0 and would like to upgrade to version 2.0.0 or above, you need to migrate your Artifactory configuration data to the format expected by the type 2 plugin as described in the following steps:

1. If you are not already on version 1.13.0 of the plugin, upgrade to that version first.

2. From Bamboo Administration | Artifactory Plugin, click on the "Migrate data to v2" button.

3. Remove plugin version 1.13.0 and restart Bamboo.

4. You're now ready to install version 2.x according to the below instructions.

Installing Versions 2.x

From version 2.0.0, the Bamboo Artifactory Plugin is released as a type 2 plugin. You can read about installing type 2 plugins in the Bamboo documentation for Installing add-ons.

Installing Versions 1.x

Remove older versions

If you have an older version of the plug-in, be sure to remove it before upgrading to a newer one

For versions below 2.0.0, the plugin was released as a type 1 plugin and is deployed to Bamboo by placing the packaged plugin jar file into the $BAMBOO_INSTALLATION_HOME/atlassian-bamboo/WEB-INF/lib folder and restarting Bamboo.

For more details please refer to the Bamboo documentation for Installing Plugins type 1 add-ons.


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:

  1. Under the Administration menu, select Overview to view the Bamboo administration page. 
  2. Then, under Build Resources select Server Capabilities
  3. Select Executable as the Capability Type
  4. Select Artifactory Maven 3Artifactory Gradle or Artifactory Ivy as the type from the Types list.
  5. Make sure that Path points to an installation directory of the selected builder type.

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.

Username and Password

Username and password are optional and are 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).

Bamboo Artifactory Server Configuration

Configuring a Project Builder

To set up a project task to deploy build-info and artifacts to Artifactory:

  1. Go to the Tasks step of your jobs configuration.
  2. When adding a task type, select the Artifactory Maven 3, Gradle or Ivy builder
  3. The builder configuration fields appear and include Artifactory and build-info configuration options.

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.


Repository list empty?

If the Resolution Repository or Target Repository fields remain empty, check that you have entered valid credentials when defining the Artifactory servers.


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.

Configuring Repositories for Resolution and Deployment

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:

Send License Violation Notifications to
A list of email addresses of users who should receive license violation notifications.
Limit Checks to the Following Scopes
The Maven dependency scopes on which the license check should be run. If left empty, all scopes will be checked.
Include Published Artifacts
Indicates that any build artifacts that are dependencies for other build artifacts, should also be scanned for license violations
Disable Automatic License Discovery

Tells Artifactory not to try and automatically analyze and tag the build's dependencies with license information upon deployment.
You can still attach license information manually by running Auto-Find from the build's Licenses tab in Artifactory.

Running License Checks

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:

Code Center application name
The name of the Black Duck Code Center application that should be invoked.
Code Center application version
The Black Duck Code Center application version.
Send compliance report email to
A list of email addresses of users who should receive license violation notifications.
Limit checks to the following scopes
The Maven dependency scopes on which the compliance check should be run. If left empty, all scopes will be checked.
Include Published Artifacts
Indicates that any build artifacts that are dependencies for other build artifacts, should also be scanned for license violations
Auto create missing component requests
Automatically create missing components in Black Duck Code Center application after the build is completed and deployed in Artifactory.
Auto discard stale component requests
Automatically discard stale components in Black Duck Code Center application after the build is completed and deployed in Artifactory.


Black Duck Code Center Integration

The Artifactory Generic Resolve Task

The Generic Resolve task can be used in any job with any combination of tasks. 

It lets you specify dependency patterns that should be downloaded from Artifactory through the creation of File Specs. Read more about File Specs here.

Before version 2.2.0, specifying dependency patterns was possible through Legacy Patterns, which became deprecated in version 2.2.0

Generic Deploy Task

The 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. Specifying artifact patterns to be deployed to Artifactory is done through the creation of File Specs. Read more about File Specs here.

Before version 2.2.0, specifying artifact patterns was possible through Legacy Patterns, which became deprecated in version 2.2.0

Make sure to add the Generic Deploy task as a final step!

Generic Deploy Task


Using File Specs

File Spec are specified in JSON format. They are used in the Generic Resolve and Generic Deploy tasks, to specify the dependencies to be resolved from Artifactory or artifacts to be deployed to it.
You can use File Specs in one of the following ways:

  1. Manage them in your SCM, and then during the build, have them pulled to the workspace with the other sources. If you choose this option, you should select the "File" option in the "Upload spec source" or "Download spec source" field and specify the relative path to the File Spec in your workspace.
  2. Save the File Spec JSON as part of the job configuration. If you choose this option, you should select the "Job configuration" option in the "Upload spec source" or "Download spec source" field and specify the File Spec JSON content in your workspace in the "File path" field.

You can read the File Spec schema here.

Deployment Projects

The Bamboo Artifactory Plugin also supports Bamboo Deployment projects (read more about Deployment projects here).

  • The Artifactory Download task downloads artifacts from Artifactory. The artifacts to be downloaded are defined using File Specs.
  • The Artifactory Deployment task collects the build artifacts which are shared by the build plan associated with the deployment task, and uploads them to Artifactory. In addition, artifacts which were downloaded by Artifactory Download task are also available for deployment.

The "Artifacts Download" Task

The Artifacts Download task must be prior to the Artifactory Deployment task in the Deployment job flow.

The Artifacts Directory

We recommend configuring a subdirectory for the Artifacts Download task.

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:

  1. Deploys all artifacts to the selected target repository in one go (as opposed to the deploy at the end of each module build, used by Maven/Ivy).
  2. Deploys the Artifactory build-info to the selected server, which provides full traceability of the build in Artifactory, with links back to the build in Bamboo.

Running a Build

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.

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:

  •* - All properties starting with this prefix will be added to the root properties of the build-info.
  • artifactory.deploy.* - All properties starting with this prefix will be attached to any produced artifacts that are deployed.
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 buildInfoConfig.propertiesFile and set its value to the absolute path of the properties file.

Attaching Searchable Parameters

The given path and file should be present on the machine that is running the build agent, not the server.

Overriding Plan values using Bamboo Variables

The Artifactory Plugin supports overriding various in the plan configuration like Deployer credentials, Resolver credentials, repositories etc. 

If you wish to override any of the values specified in the table below, you need to configure them as Bamboo variables either through the UI or append then to the REST URL request as a query parameters.

When assigning any value to these Bamboo variables, it will override the job configuration.


Example with REST
curl -ubamboo-user:bamboo-password -XPOST 
"http://<BAMBOO HOST>:8085/rest/api/latest/queue/MVN-JOB?stage&executeAllStages&bamboo.variable.artifactory.override.deployer.username=new_username&bamboo.variable.artifactory.override.deployer.password=new_password"

In the example above, we use CURL to remotely invoke a Bamboo plan. We set the Deployer username and Deployer password for this specific request.

Note that we add the "bamboo.varaible" prefix to the query parameters.

Note that the sent values will be applied only if the specific task support them. For example: currently Artifactory Gradle tasks do not support Resolver credentials, hence those values will be ignored if sent.

Parameter nameDescriptionSupported jobs


Deployer usernameMaven, Gradle, Ivy, Generic deploy


Deployer passwordMaven, Gradle, Ivy, Generic deploy


Resolver usernameMaven, Generic resolve


Resolver passwordMaven, Generic resolve


Resolve repositoryMaven, Gradle


Deploy repositoryMaven, Gradle, Ivy, Generic deploy


If set to true, check the value of artifactory.task.override.jdk.env.var.

If that variable is populated with an environment variable,

use the value of that environment variable as the Build JDK path.

If artifactory.task.override.jdk.env.var is not defined, use the value of JAVA_HOME for the Build JDK.

Maven, Gradle, Ivy


Stores the name of another environment variable whose value should be used for the build JDK.Maven, Gradle, Ivy

Release Management

The Artifactory Plugin provides a powerful feature for release management and promotion. For details please refer to Bamboo Artifactory Plugin - Release Management.

Push to Bintray (Deprecated)

Bintray users can publish build artifacts to Bintray by using the Artifactory Bintray integration.
This can be done on the Push to Bintray tab of the Bamboo Artifactory Plugin in one of two ways:

  1. You can configure your Bintray details in a descriptor file which should be added to your list of build artifacts
  2. You can check the Override descriptor file checkbox and specify the details in the Push to Bintray tab UI.
Using a Descriptor File

1. Create a descriptor file named bintray-info.json.  

Here is an example:

-	"repo": {
+		"name": "test",
-		"type": "generic",
-		"private": false,
-		"premium": false,
-		"desc": "My test repo",
-		"labels": ["label1", "label2"],
-		"updateExisting": false
+	"package": {
+		"name": "auto-upload",
+		"repo": "test",
+		"subject": "myBintrayUser",
-		"desc": "I was pushed completely automatically",
-		"website_url": "",
-		"issue_tracker_url": "",
+ 		"vcs_url": "",
+ 		"licenses": ["MIT"],
- 		"labels": ["cool", "awesome", "gorilla"],
- 		"public_download_numbers": false,
- 		"public_stats": false,
- 		"attributes": [{"name": "att1", "values" : ["val1"], "type": "string"},
     				   {"name": "att2", "values" : [1, 2.2, 4], "type": "number"},
     				   {"name": "att5", "values" : ["2014-12-28T19:43:37+0100"], "type": "date"}]
+	"version": {
+		"name": "0.5",
-		"desc": "This is a version",
-		"released": "2015-01-04",
-		"vcs_tag": "0.5",
-	 	"attributes": [{"name": "VerAtt1", "values" : ["VerVal1"], "type": "string"},
  					   {"name": "VerAtt2", "values" : [1, 3.3, 5], "type": "number"},
					   {"name": "VerAtt3", "values" : ["2015-01-01T19:43:37+0100"], "type": "date"}],
-		"gpgSign": false
	"applyToFiles": ["repo1/org/jfrog/*.*", "repo2/org/jfrog/test/module*/*.jar", "repo3/org/jfrog/test/**/*.*", "repo2/org/jfrog/test/**/art.?ar"],
	"applyToRepoFiles": ["/org/jfrog/*.*,  jfrog/test/**/*.*"],
	"applyToProps": [{"upload.prop1": ["val1", "val2"]}, {"upload.prop2": ["*"]}, {"*":   ["valueRegardlessOfProperty"]}],
	"publish": true

The file's name itself must contain the string bintray-info (anywhere in the name) and have a .json extension


Most of the fields are self-explanatory, however below are descriptions for those fields whose purpose may be less obvious:

 Signifies Artifactory should update an existing repository with the same name with the values in the jsondescriptor (applies only to the 'labels' and 'desc' fields)
Can either be your Bintray user nameorthe organization you are pushing to. The credentials that are used in the operation are those you defined in your user profile (or in the default section). 

If you are pushing a complete build, this field should remain empty.

When pushing files, this field should contain a comma-separated list of files (in JSON format) that should be pushed. A file matching any of the file specifications will be pushed (i.e. an "OR" relationship).

You may use wildcards as follows:

  • *: match any 0 or more characters

  • **: recursively match any sub-folders (in the path section only)

  • ?: match any 0 or 1 character

Here are some examples of valid search paths:

repo1/org/jfrog/myTest.jarThe file myTest.jar under repo1/org/jfrog
repo1/org/jfrog/*.*All files under repo1/org/jfrog
repo2/org/jfrog/test/module*/*.jarAll .jar files under any subfolder of repo2/org/jfrog/test whose name starts with "module"
repo2/org/jfrog/test/**/*.jarAll .jar files under any subfolder of repo2/org/jfrog/test 
repo2/org/jfrog/test/**/art.?arAll files named "art" with a file extension that has 2 or 3 characters and ends with "ar" under any subfolder of repo2/org/jfrog/test 

If you are pushing a complete build, this field should remain empty.

When pushing files, this field should contain a comma-separated list of files(in JSON format) that should be pushed. A file matching any of the file specifications will be pushed (i.e. an "OR" relationship).

This field behaves similarly to applyToFiles, including wildcards as described above, only it refers to relative paths inside the repo that containsthejson descriptor file:

  • If the path starts with a leading ' / ' then the parent for this path is the repository's root, so the path /org/jfrog/*.* will actually point to containingRepo/org/jfrog/*.*
  • If the path doesn't start with a ' / ' then the parent for this path is the folder containing the descriptor. So if the descriptor resides in /org/jfrog/bintray-info.json, the path /test/myPackage/*.* will actually
    point to containingRepo/org/jfrog/test/myPackage/*.*

0 or more key:value pairs with which to filter the selected files by properties. The '*' and '?' wildcards are supported in this filter as well.

A file matching all of the property specifications will be pushed (i.e. an "AND relationship)

If set to true, the version will be automatically published once the push operation is complete.

If set to true and no passphrase was passed as a parameter to the REST API call, Artifactory will attempt to sign the version without any passphrase.  

If you provide the gpgPassphrase parameter in the REST API call, this will cause the call to ignore this flag and the version will be signed with the passphrase that was passed.

2. Commit the descriptor file to your source control along with your project sources.
3. Modify your build script to attach the file to your build artifacts.

Using the "Push to Bintray" Tab UI

1. Check the Override descriptor file checkbox in the Push to Bintray tab.
2. Fill in the fields that are displayed.


Bintray Required Fields

For Bintray OSS users, all fields are mandatory.
For Bintray Pro accounts, the Licenses and VCS URL fields are optional .

Maven Central sync with Bintray 

When checking the "Maven Central Sync" checkbox in Push to Bintray configuration page your build will be published to Maven Central after it is pushed to Bintray.

Only packages included to jcenter can be synced with Maven Central automatically.


In order to use Maven Central sync you need to configure your Bintray and Sonatype OSS credentials in Artifactory plugin page like shown in the image below.

Bintray credentials

"Push to Bintray" works with Bintray credentials configured in Artifactory. You only need to specify Bintray credentials if you are using the Maven Central sync option.

Release Notes

2.4.1 (21 Jan 2018)
  1. Bug fix (BAP-422)
2.4.0 (17 Jan 2018)
  1. Support Download from Artifactory in Deployment Plans (BAP-413)
  2. Compatibility with Bamboo 6.3.x (BAP-415, BAP-419, BAP-421)
  3. Bug fixes (BAP-399, BAP-401, BAP-403, BAP-404, BAP-408, BAP-409, BAP-410, BAP-411, BAP-412, BAP-413, BAP-414, BAP-417)
2.3.0 (10 Oct 2017)
  1. Support pattern exclusion in File Specs (BAP-391)
  2. File specs AQL optimizations (BAP-395)
  3. Dependencies repositories have been added to the plugin's maven descriptor (BAP-397)
  4. Bug fixes (BAP-385, BAP-390, BAP-396)
2.2.0 (6 Aug 2017)
  1. File Specs support for the Generic Resolve and Generic Deploy Tasks (BAP-377)
  2. Upgrade JGit (BAP-381)
  3. Bug fixes (BAP-378, BAP-379, BAP-380, BAP-382, BAP-383, BAP-384, BAP-387)
2.1.1 (22 Jun 2017)
  1. Compatibility with Bamboo 6.0.x (BAP-376)
2.1.0 (20 Apr 2017)
  1. Artifactory Release Management API changes (BAP-374)
  2. Bug fixes(BAP-372, BAP-373)
2.0.2 (16 Feb 2017)
  1. Compatibility with Bamboo 5.15.x (BAP-370)
2.0.1 (29 Jan 2017)
  1. Bug fix (BAP-369)
1.10.2 (22 Sep 2016)
  1. Bug fixes (BAP-360, BAP-359)
1.10.1 (7 Apr 2016)
  1. Bug fixes (BAP-345)
1.10.0 (25 Feb 2016)
  1. Compatibility with Bamboo 5.10.x (BAP-336)
  2. Coordinate the deployment order of artifacts according to module info in the Gradle task (BAP-294)
  3. Bug fix (BAP-303)
1.9.2 (22 Dec 2015)
  1. Bug fixes (BAP-330, BAP-331)
1.9.1 (13 Dec 2015)
  1. Bug fixe (BAP-312)
1.9.0 (26 Nov 2015)
  1. Support sending parameters when invoking Bamboo Artifactory tasks remotely. (BAP-281, BAP-232)
  2. New "Push to Maven Central" (BAP-284)
  3. Bug fixes (BAP-313, BAP-306, BAP-290, BAP-288)
1.8.2 (27 Oct 2015)
  1. Bug fixes (BAP-289, BAP-292, BAP-302)
1.8.1 (4 Aug 2015)
  1. Bug fix (BAP-282)
1.8.0 (15 Jun 2015)
  1. Add push to Bintray support (BAP-257)
  2. Make Artifactory Upload Task available for Deployment projects (BAP-264)
  3. Ability not to promote the version on Gradle Release Staging  (BAP-258)
  4. Bug fixes (BAP-270, BAP-269, BAP-267, BAP-266, BAP-261, BAP-260, BAP-254, BAP-246)
1.7.7 (30 Mar 2015)
  1. Support for Bamboo 5.8.x (BAP-249)
1.7.6 (14 Jan 2015)
  1. Support for Bamboo 5.7.x (BAP-230)
  2. Compatibility with Maven 3.2.5 (BAP-244)
  3. Enable overriding the Build JDK value using Bamboo variables (BAP-240)
  4. Bug fix (BAP-241)
1.7.5 (10 Nov 2014)
  1. Support Atlassian Stash source control management (BAP-206)
  2. Artifactory generic Resolve task (BAP-207)
  3. Maven 3 tasks - Record Implicit Project Dependencies and Build-Time Dependencies (BAP-225)
1.7.4 (12 Aug 2014)
  1. Support for Bamboo 5.6 (BAP-218)
  2. Bug fix (BAP-219)
1.7.3 (29 Jul 2014)
  1. Add support for Gradle 2.0 (GAP-153)
  2. Bug fix (BAP-212)
1.7.2 (25 Jun 2014)
  1. Bug fixes  (BAP-196BAP-208BAP-166)
1.7.1 (26 MAY 2014)
  1. A new check box that gives the ability to ignore artifacts that are not deployed according to include/exclude patterns. (BAP-180)
1.7.0 (06 Apr 2014)
  1. Fix Support for Bamboo 5.4+
  2. Supporting Git Shared Credentials in Release Management functionality (BAP-189
  3. Adding Version Control Url property to the Artifactory Build Info JSON. (BAP-200)
  4. Bug fixes ( BAP-197)
1.6.2 (24 Nov 2013)
  1. Fix Support for Bamboo 5.2
  2. Add Artifactory BlackDuck integration
  3. Bug fixes (BAP-182 BAP-184 BAP-186 BAP-184)
1.6.1 (03 Oct 2013)
  1. Support form Bamboo 5.1.1
  2. Bug fixes 1.6.1
1.6.0 (16 Jul 2013)
  1. Support form Bamboo 5.0
1.5.6 (03 Sep 2013)
  1. Support form Bamboo 4.2
1.5.5 (03 Sep 2012)
  1. Support for include/exclude captured environment variables (BAP-143)
  2. Bug fixes (MAP-41 MAP-40 GAP-129 BAP-148 IAP-32)
1.5.4 (25 Jun 2012)
  1. Support Bamboo 4.1.
  2. Bug fixes. (JIRA)
1.5.3 (02 Apr 2012)
  1. Support Bamboo 4.0.
1.5.2 (02 Apr 2012)
  1. Support Perforce for release management. (BAP-133)
  2. Bug fixes. (JIRA)
1.5.1 (05 Jan 2012)
  1. Compatible release plugin for version 3.4.2. (BAP-116)
  2. Support for Gradle properties deployment. (BAP-117)
  3. Unique icon for each Artifactory task type.
  4. Setting Bamboo job requirements correctly for all builder types. (BAP-125)
1.5.0 (11 Dec 2011)
  1. Compatible with bamboo version 3.3.x.
  2. Compatible with Gradle 1.0-milestone-6.
1.4.2 (19 Sep 2011)
  1. Bug fix (BAP-91)
1.4.1 (01 Aug 2011) 
  1. Support for Bamboo 3.2.x
  2. Bug fix (BAP-90)
1.4.0 (14 Jul 2011)
  1. Introducing Release Management capabilities.
  2. Generic Build Info support for all job types.
  3. Bug fixes.
1.3.2 (14 Jun 2011)
  1. Bug fix (BAP-65)
1.3.1 (13 Jun 2011)
  1. Bug fix (BAP-64)
1.3.0 (30 May 2011)
  1. Support for Bamboo 3.1.x
1.2.0 (2 Mar 2011)
  1. Support for Bamboo 3.x
1.1.0 (2 Jan 2011)
  1. Gradle Support - Gradle builds are now fully supported with the new Gradle builder
  2. Ivy builds now support custom Ivy patterns for artifacts and descriptors
  3. Support for Bamboo 2.7.x
1.0.3 (21 Nov 2010)
  1. Add Include/exclude pattern for artifacts deployment
  2. Bug fix (BAP-26)
1.0.2 (7 Nov 2010)
  1. Control for including published artifacts when running license checks
  2. Limiting license checks to scopes
  3. Control for turning off license discovery when running license checks
  • No labels