Release Process

This document describes the process of created and publishing an Ansible Tower release.

Time for a release

When the time comes for a release, the first step is to tag the release in git.

# git tag <X.Y.Z>

Monitor Jenkins

Once tagged, Jenkins will take care of the following steps. The jenkins job Release_Tower will detect the recent tag, and initiate the OFFICIAL=yes build process.

The following jobs will be triggered:

Should any build step fail, Jenkins will emit a message in IRC and set the build status to failed.

Publishing Builds

Upon successful completion, jenkins will publish build artifacts to the following locations:

Publishing AMI's

While OFFICIAL Tower AMI's are created by jenkins, the process for blessing AMI's is manual. Please contact dave@ansible.com to initiate the process.

Publishing Documentation

Tower documentation is available in the product-docs repository. The Build_Tower_Docs job builds and publishes PDF, and HTML, documentation.

1.7 KiB Raw Blame History