mirror of
https://github.com/ZwareBear/awx.git
synced 2026-03-20 07:43:35 -05:00
0f5beca9ae
* Add logic to ansible callback plugin to prevent it from waiting forever to submit events to Tower * Lower process recycle threshold for tower callback receiver * Make recycle threshold configurable * Properly exit the main callback receiver management process if the event receiver process is dead so we don't leave dead worker processes * Set a configurable maximum number of messages that can be waiting in a worker process queue before it is skipped instead of filling up memory on a dead worker process * Skip over a dead worker process if it's queue is full * Force restart callback receiver if all queues are dead * Roll back transaction.atomic with the thought that it is causing deadlocks in the worker process. Use the old commit_on_success mechanism with retry logic * Seperate queue nonblocking expected exception from any other type of exception that could be encountered on the queue fetch operation
Ansible Tower
Tower provides a web-based user interface, REST API and task engine built on top of Ansible.
The current version under development is 2.1.0.
Development releases always use the 'master' branch.
Release schedule
- 1.2.2, July 31, 2013.
- 1.3.0, September 15, 2013.
- 1.3.1, September 17, 2013.
- 1.4.0, November 25, 2013.
- 1.4.5, February 10, 2014.
- 1.4.8, April 7, 2014.
- 1.4.9, April 17, 2014.
- 1.4.10, April 28, 2014.
- 1.4.11, May 30, 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
- 2.0.5, ...
- 2.1.0, January 7, 2014
Any fixes should be applied on the appropriate release branch and be cherry-picked to master.
Resources
Refer to CONTRIBUTING.md to get started developing, testing and building Tower.
Refer to setup/README.md to get started deploying Tower.
Refer to docs/build_system.md for more about Jenkins and installing nightly builds (as opposed to running from source).
Refer to docs/release_process.md for information on the steps involved in creating a release.