50d8020efe
With pbr tag-based versioning, not having the latest release tag in the master branch makes the output a little nasty. Add a job that makes a merge commit containing the tag on a release from milestone-proposed branch. The merge strategy it uses is 'ours' because we're not attempting to use this to keep code lines up to date - the expectation is that content added in milestone-proposed should already be in master. The main thing we want to do is re-connect the revision and tag history with master, so that things like 'git tag --contains' work. Closes-Bug: 1192039 Change-Id: I06c06bd7542ae493e74fdcaa3c4419f84843cd03
These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.
The main entry point is in manifests/site.pp.
In general, most of the modules here are designed to be able to be run either in agent or apply mode.
These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.
See http://ci.openstack.org for more information.