Confirmed users
142
edits
ReleaseEngineering/Maintenance: Difference between revisions
→Puppet deployments
| Line 23: | Line 23: | ||
Merges to the <em>production</em> branch of [http://hg.mozilla.org/build/puppet/graph the puppet repository] are automatically deployed by Puppet within a 1/2 hour. Please see that repo for push history. | Merges to the <em>production</em> branch of [http://hg.mozilla.org/build/puppet/graph the puppet repository] are automatically deployed by Puppet within a 1/2 hour. Please see that repo for push history. | ||
Please note if you are applying a puppet change, '''unless you have good reason not to do so''' please merge it to production branch immediately. The reason for this is that we do not want puppet changes to "back up" on default, and then land ''en masse'' in production. It can be very difficult to untangle multiple puppet changes that arrive together. | |||
The reason we have a production branch at all, is to allow contributions on default branch from a larger group of people, than those responsible for maintaining the infrastructure controlled by the puppet repo - in other words, a smaller group of people can merge to production, than the group of people that can land on default. | |||
= Reconfigs / Deployments = | = Reconfigs / Deployments = | ||