External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-02-01 09:38:10 -03:30
Code Issues Packages Projects Releases Wiki Activity

Doc updates and add release_process.md

Browse Source
This commit is contained in:
James Laska
2014-02-26 10:48:34 -05:00
parent d9d8fbd432
commit e8d6d69fff
3 changed files with 48 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/release_process.md Normal file
View File

@@ -0,0 +1,34 @@
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](http://50.116.42.103/view/Tower/) will take care of the
following steps. The jenkins job
[Release_Tower](http://50.116.42.103/view/Tower/job/Release_Tower/) will detect
the recent tag, and initiate the `OFFICIAL=yes` build process.
The following jobs will be triggered:
* [Build_Tower_TAR](http://50.116.42.103/view/Tower/)
* [Build_Tower_DEB](http://50.116.42.103/view/Tower/)
* [Build_Tower_AMI](http://50.116.42.103/view/Tower/)
* [Build_Tower_RPM](http://50.116.42.103/view/Tower/)
* [Build_Tower_Docs](http://50.116.42.103/view/Tower/)
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:
* http://releases.ansible.com/ansible-tower/rpm
* http://releases.ansible.com/ansible-tower/deb
* http://releases.ansible.com/ansible-tower/setup