mirror of
https://github.com/ansible/awx.git
synced 2026-03-22 19:35:02 -02:30
Update release history and process docs
This commit is contained in:
@@ -4,7 +4,7 @@ Ansible Tower
|
|||||||
Tower provides a web-based user interface, REST API and task engine built on top of
|
Tower provides a web-based user interface, REST API and task engine built on top of
|
||||||
Ansible.
|
Ansible.
|
||||||
|
|
||||||
The current version under development is 2.0.0.
|
The current version under development is 2.1.0.
|
||||||
|
|
||||||
Development releases always use the 'master' branch.
|
Development releases always use the 'master' branch.
|
||||||
|
|
||||||
@@ -21,6 +21,10 @@ Release schedule
|
|||||||
* 1.4.10, April 28, 2014.
|
* 1.4.10, April 28, 2014.
|
||||||
* 1.4.11, May 30, 2014.
|
* 1.4.11, May 30, 2014.
|
||||||
* 2.0.0, August 19, 2014
|
* 2.0.0, August 19, 2014
|
||||||
|
* 2.0.1, September 4, 2014
|
||||||
|
* 2.0.2, October 6, 2014
|
||||||
|
* 2.0.3, November 14, 2014
|
||||||
|
* 2.0.4, November 21, 2014
|
||||||
|
|
||||||
Any fixes should be applied on the appropriate release branch and be cherry-picked to
|
Any fixes should be applied on the appropriate release branch and be cherry-picked to
|
||||||
master.
|
master.
|
||||||
|
|||||||
@@ -1,21 +1,38 @@
|
|||||||
Release Process
|
Release Process
|
||||||
===============
|
===============
|
||||||
|
|
||||||
This document describes the process of created and publishing an Ansible Tower release.
|
This document describes the process of creating and publishing an Ansible Tower release.
|
||||||
|
|
||||||
Time for a release
|
Time for a release
|
||||||
------------------
|
------------------
|
||||||
|
|
||||||
When the time comes for a release, the first step is to tag the release in git.
|
When the time comes for a release, the following steps will ensure a smooth and
|
||||||
|
successful release.
|
||||||
|
|
||||||
|
1. Verify that the `__version__` variable has been updated in `awx/__init__.py`.
|
||||||
|
|
||||||
|
__version__ = 'X.Y.Z'
|
||||||
|
|
||||||
|
2. Update the rpm package changelog by adding a new entry to the file `packaging/rpm/ansible-tower.spec`.
|
||||||
|
|
||||||
|
3. Update the debian package changelog by adding a new entry to the file `packaging/debian/changelog`.
|
||||||
|
|
||||||
|
4. Tag and push the release to git.
|
||||||
|
|
||||||
# git tag <X.Y.Z>
|
# git tag <X.Y.Z>
|
||||||
|
# git push --tags
|
||||||
|
|
||||||
|
5. Create and push a release branch to git.
|
||||||
|
|
||||||
|
# git branch release_<X.Y.Z>
|
||||||
|
# git checkout release_<X.Y.Z>
|
||||||
|
# git push origin release_<X.Y.Z>
|
||||||
|
|
||||||
Monitor Jenkins
|
Monitor Jenkins
|
||||||
---------------
|
---------------
|
||||||
Once tagged, [Jenkins](http://50.116.42.103/view/Tower/) will take care of the
|
Once tagged, one must launch the [Release_Tower](http://50.116.42.103/view/Tower/job/Release_Tower/) with the following parameters:
|
||||||
following steps. The jenkins job
|
* `GIT_BRANCH=origin/tags/<X.Y.Z>`
|
||||||
[Release_Tower](http://50.116.42.103/view/Tower/job/Release_Tower/) will detect
|
* `OFFICIAL=yes`
|
||||||
the recent tag, and initiate the `OFFICIAL=yes` build process.
|
|
||||||
|
|
||||||
The following jobs will be triggered:
|
The following jobs will be triggered:
|
||||||
* [Build_Tower_TAR](http://50.116.42.103/view/Tower/)
|
* [Build_Tower_TAR](http://50.116.42.103/view/Tower/)
|
||||||
|
|||||||
Reference in New Issue
Block a user