Shane McDonald d600706150 Use jinja template for populating version and release in spec file
These macros were intended to pull the version and release from a python file if they werent passed in with --define, but /usr/bin/python is not available at this point in the build process. I'm not sure when or if this ever worked. Perhaps before we were using mock.

This approach also works for our Brew builds, as we cannot specify a macro value at build time.
2017-04-03 10:32:46 -04:00
2017-03-31 12:11:37 -04:00
2017-02-28 14:03:52 -05:00
2017-03-29 14:30:58 -04:00
2016-02-01 18:37:56 -05:00
2015-02-06 09:47:41 -05:00
2016-07-22 13:19:57 -04:00
2016-12-20 15:34:29 -05: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-18 14:19:18 -04:00
2016-11-11 16:01:45 -05:00
2016-11-15 17:31:21 -05:00
2017-03-23 16:46:25 -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 429 MiB
Languages
Python 97.8%
Jinja 0.9%
Makefile 0.5%
Shell 0.3%
HTML 0.2%
Other 0.2%