Assimilating Artifactory into a continuous integration build process is very straightforward.
Treat the CI server as a regular build client and, as such, the CI server resolves dependencies from Artifactory and deploys artifacts into a dedicated repository wihtin Artifactory.
The Build Integration feature of Artifactory takes this integration one step further, by closely integrating your Artifactory and your CI server to provide fully-reproducible builds and full visibility of deployed artifacts, used dependencies and information regarding the build environment.
By using the Build Integration Add-on you are able to:
Jenkins/Hudson, Team City and Bamboo Integrations
The Build Integration currently supports Jenkins/Hudson, TeamCity and Bamboo. Similar integration with other build technologies stacks, are currently being worked-on - stay tuned.
The build technologies supported are: Maven 3 and 2, Gradle, Ivy/Ant, .Net and Generic builds (look under each CI server to see the technologies supported by the plugin for this server).
To learn more about installation and usage instructions specific to your CI server, follow these links:
Inspecting and Managing Builds
Builds and Per-Build History
Once you have run a build in your your CI server that deployed to Artifactory, you can immediately see the corresponding build results inside Artifactory. A new '
Each build corresponds to its CI server project (job) counterpart and contains a build history of all runs, that reflect the build history in the CI server:
For each build item in the history you can drill down and obtain more fine details about it, as explained in the next section.
You can also view the build in the CI server by selecting 'Show in CI Server'. In addition, you can also navigate back to Artifactory from the CI server UI.
Drilling-down into the single build level, each build contains three sections of information:
General Build Information
This section contains general information about the build.
From here, you can save the build's artifacts and/or dependencies as a Smart Search Result to further manipulate the search, as explained below.
Each build publishes module(s) into Artifactory, displayed in this view, together with the number of artifacts and dependencies which they contain.
Module Artifacts and Dependencies
If you drill down even further, you can inspect each module's published artifacts and dependencies.
NOTE! the deployed artifacts are collected with their types and dependencies contain the scope(s) that the dependencies used in during the build.
You can also go from each item to its tree view in Artifactory and view other details about it.
In the Environment tab, you can view build properties and other environmental details that are otherwise lost if you want to replay the build at a later point in time (e.g. JDK used, system architecture etc.).
In the Licenses tab, you receive a centralized view of all the artifacts and dependencies involved and their license analysis.
The Governance tab displays the integration status of this build with a Black Duck Code Center application. In this tab you can also find the components approval statuses, licenses and security vulnerabilities.
In the Diff tab, you can compare the current build artifacts/dependencies/environment with an older build to see what has changed (new artifacts added, old dependencies deleted etc).
The Release History tab displays a timeline of the selected build's release landmarks.