* Add reprepro target
* Use debuild for building deb packages
* Use the same setuptools target for RPM and DEB
* Update rpm and deb changelogs for existing releases
Moves the iterator-based id to the top-level <div>. The pagination
links and labels are now children of this <div>. Also, renamed id on
the buttons and labels regions.
Adds the following aliases to assist with packaging-specific sdist.
* dev_deb and release_deb - includes only .pyc files
* dev_rpm and release_rpm - includes only .py files (later removed by
install_lib)
The rpm sdist tarball is a traditional source distribution. During the build
process, RPM will byte-compile and remove the .py source files. The deb sdist
includes only byte-compiled awx python.
Debian doesn't byte-compile .py files during the build process. Packagers are
expected to byte-compile in the postinst [1]. The following change adds
byte-compiled .pyc files into the sdist tarball. During RPM packaging, the rpm
macros will regenerate/replace these files against the appropriate python
version.
[1] https://wiki.debian.org/Python/Packaging
Simplifing the RPM build process by moving the jenkins build workflow into the
Makefile. This starts with mock. Additional buildrequires changes likely to
follow.
Several AMI packaging changes, including:
* Set a default value for OFFICIAL=no
* Include tower version in ami_description and tag:Name
* Packer will tag the AMI to help with visually identifying AMIs (tags used
include Name, aws_instance_count, product_name, product_version)
* Removed license/* files. The license instance count is supplied via an
environment variable AWS_INSTANCE_COUNT
* Update reset/install_aws.sh to require an instance count parameter (-c)
The grunt command is still configurable via the GRUNT environment variable. By
default, we disable colored output when we detect the shell is non-interactive.
This improves reviewing output when run from automation.
Automation can now set GRUNT to provide a path to a specific grunt binary, or
to add grunt parameters. For example, to disable color output during a Jenkins
build:
GRUNT="grunt --no-color" make lintjs
Rather than hard-code the name and version in package.json, generate the file
during the build process. The strings %NAME% and %VERSION% will be replaced
with appropriate values during a new build target 'package.json'.
Update Makefile syntax to no longer generate the license as a build step. In
addition, updated ansible-tower.json to provide a more descriptive ami_name and
ami_description.
James Laska