1059461c6c
When proposing requirement update changes ensure that the proper branch can be checked out if the branch isn't master. To do this checkout origin/$BRANCH instead of just branch. Additonally, don't git review -d an existing change as it may have merge conflicts with the target branch. Instead make changes against the target branch, push them to the existing change as a new patchset, and ignore failures of git review when there are no new changes. This allows changes to the requirements files to happen out of band from these automated change proposals. Closes-Bug: 1274251 Change-Id: I7b81b87a90639a66dce5502cded5e37d96abd1f7
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.