Before You Begin
The TeamCity Artifactory plugin brings CI Build Integration to TeamCity users. This allows you to capture information about deployed artifacts, resolved dependencies and environment data associated with TeamCity build runs. There is also full traceability for your builds.
Build Integration also takes care of deploying your artifacts to Artifactory efficiently.
You can read more about the concept of Build Integration, BuildInfo and how it is used in Artifactory here.
Installing the Plugin
Some features of the plugin only run on the recent versions of Artifactory and TeamCity.
To make the most of the plugin, the recommended requirements are:
Download the version of the plugin according to the compatibility matrix below:
Plugins are deployed to TeamCity by placing the packaged plugin into the
NOTE! that if you have an older version of the plugin, make sure to remove it.
To use the TeamCity Artifactory plugin you must first configure your Artifactory server(s) in TeamCity's server configuration. You can then set up a project build runner to deploy artifacts and Build Info to a repository on one of the configured Artifactory servers.
Configuring System-wide Artifactory Server(s)
To make Artifactory servers globally available to project-runner configurations, they must be defined in
Click on "
Deployer credentials can be set at the global level for all builds. Deploy credentials can be set or overridden at a project build level.
Resolving repository username and password is 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 Project-specific Runners
Editing Project-specific Configuration
To set up a project runner to deploy build info and artifacts to Artifactory go to
When selecting an Artifactory server URL, the server is queried for a list of configured repositories (using the credentials in the server configuration, if configured). This populates the "Target Repository" combobox with a list of target repositories to deploy to.
If the repository list remains empty, ensure the specified Artifactory server URL, credentials and proxy information (if provided) are valid.
Any information about communication errors that might occur can be found in the TeamCity server logs.
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 email addresses in the notification recipients text box.
In addition, you have more advanced options:
Attaching Searchable Parameters to Build-Info and to Published Artifacts
To define a parameter click on the "Add new property" or "Add new variable" buttons (both system properties and environment variables are supported).
Available parameter types:
It is also possible to point the plugin to a properties file containing the aforementioned properties.
To point to such a file, define a property by the name
Viewing Project-specific Configuration
Existing project configuration can be viewed from
Running a Build with the Artifactory Plugin
Once you have completed setting up a project runner you can run a project build. The Artifactory plugin takes effect at the end of the build and:
You can also link directly to the information in Artifactory from a build run view:
Triggering Builds in Reaction to Changes in Artifactory
The plugin allows you to set a new type of trigger that periodically polls a path in Artifactory, a folder or an individual file. Whenever a change is detected to this path, for example new artifacts have been deployed, the TeamCity build is triggered.
This feature can only be used with the Artifactory Pro Power Pack.
To configure a new build trigger, first select the Artifactory Build Trigger from
Select the server, repository and paths in the repository for which you would like to automatically trigger a build following a change in the item content.
Complete the username and a password fields of a valid deployer.
NOTE! that the user must have deploy rights on any local repository).
Currently, TeamCity does not provide a global point of proxy configuration; so where the target Artifactory server must be accessed via a proxy, proxy configuration can be achieved by setting the following properties inside the
The TeamCity Artifactory plugin is available under the Apache v2 License.
Watch the Screencast
To see the Teamcity plugin in action you can watch the short demo screencast below.
2.0.0 (5 Dec 2010)
1.1.3 (21 Nov 2010)
1.1.2 (7 Nov 2010)