Chris Meyers cc7c2957cf always chain failures
* When inv and proj updates trigger from a JT run, if either update
fails then the job template should get marked failed. Before this
commit, the job template would get marked failed ONLY if there was
enough capacity to run all the associated updates within the same
schedule() call. If, instead, the associated updates were ran in another
schedule() call, the failure chain was lost. This changeset fixes that
by saving the necessary data in the dependent_jobs relationship so that
the failure is always chained.
2016-12-09 14:09:54 -05:00
2016-12-09 14:09:54 -05:00
2016-10-27 22:26:39 +05:30
2016-02-01 18:37:56 -05:00
2016-10-18 18:10:39 +05:30
2015-02-06 09:47:41 -05:00
2016-07-22 13:19:57 -04:00
2015-06-12 11:54:22 -04:00
2016-03-04 16:19:00 -05:00
2015-06-11 16:10:23 -04:00
2016-11-02 14:16:27 -04:00
2016-10-25 16:12:41 +05:30
2016-11-11 16:01:45 -05:00
2016-11-15 17:31:21 -05:00
2016-11-15 20:59:39 -05:00
2016-07-22 13:19:57 -04:00

Build Status Requirements Status

Ansible Tower

Tower provides a web-based user interface, REST API and task engine built on top of Ansible.

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.

Refer to http://docs.ansible.com/ansible-tower/index.html for information on installing/upgrading, setup, troubleshooting, and much more.

Description
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
Readme 428 MiB
Languages
Python 97.8%
Jinja 0.9%
Makefile 0.5%
Shell 0.3%
HTML 0.2%
Other 0.2%