This article describes how and where censhare releases are uploaded to Artifactory and through which phases they are going through.

Audience

  • Developers
  • IT
  • Support

Artifact Repositories

Artifactory supports various types of repositories. For censhare releases a generic repository is used to store the releases in subdirectories:

censhare-dev and rpm-dev

For every build triggered at TeamCity build server, the resulting build is uploaded to these repositories, if it is a Master Release or a Developer Build.

censhare-qa and rpm-qa

In case of a Master Release, when the "Master Release"-Step has successfully finished with all its dependencies, the Artifacts are promoted from censhare-dev and rpm-dev to censhare-qa and rpm-qa where they are available for testing by the QA Team. This also means that if a dependency failed in the Master-Release Build, the other builds are still available for inspection in the -dev repositories.

censhare-release and rpm-release

When the QA team successfully tested and gave their go for the final release, then "Master Release Deploy" step is triggered in TeamCity. This step also promotes all builds in Artifactory to move from censhare-qa and rpm-qa to censhare-release and rpm-release.

censhare-EoS and rpm-EoS

All releases that have reached their End-of-Service are moved to these repositories.

Build Info

Whenever a build-server deploys artifacts to Artifactory it also stores the following build information:

* by which build server the build was created;
* when it was created together with all system and environment variables used at the build agent;
* when a build and its artifacts were promoted to a new stage.

All the build information are available at https://artifactory.censhare.com/artifactory/webapp/#/builds/ From the Build ID widget, you can browse through all the build numbers for a build.

  1. The "Agent" widget links back to the build-server. Clicking this link will take you back to TeamCity and the log for this specific build.
  2. When clicking on the "Published Module" tab, you can see more Artifacts and their path in the repository. You can directly download the artifacts or open the "Artifacts Browser" to show the artifacts in the directory tree.
  3. In the "Environment" tab, you can see all the environment and system variables that were present on the actual build agent during the build. So you can always inspect under which circumstances a build was created.
  4. It is also possible to see the difference between two builds. Here you can choose a different build number to compare and see, which files have changed/removed in the build, as well as see the difference in build environment variables.
  5. The "Release History" shows if a build was promoted during the build process. In case of Master Releases, if the Master Release build was successful, we can see that it was staged and when "Master Release Deploy" was executed, we can see that it has been released and when. For the future, it is planned to add an End-of-Life and End-of-Service stage.
  6. All the mentioned information are also available in JSON format directly in the browser. Please mind that the Artifactory also offers a REST-API

Last Updated: 3 September 2019