This page is to track upcoming changes to any part of RelEng infrastructure; buildbot masters, slaves, ESX hosts, etc. This should allow us keep track of what we're doing in a downtime, and also what changes can be rolled out to production without needing a downtime. This should be helpful if we need to track what changes were made when troubleshooting problems.
ReleaseEngineering:BuildbotBestPractices describes how we manage changes to our master buildbots.
Non-releng repositories involved in the CI
- Chief self-deploy recent history (needs VPN; more readable than raw logs, but is cleared if the Chief service is restarted)
- [treeherderadm.private.scl3.mozilla.com/chief/treeherder.prod/logs/ Chief self-deploy logs archive] (needs VPN; use if the history page is empty)
Merges to the production branch of the mozharness repository are live immediately. Please see that repo for push history.
Merges to the production branch of 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
This page is updated by the person who does a reconfig on production systems. Please give accurate times, as we use this page to track down if reconfigs caused debug intermittent problems. (This includes config changes not requiring a "reconfig", such as mozharness changes.)
Outcome should be 'backed out' or 'In production' or some such. Reverse date order pretty please.
|Outcome||When||Bug #(s) - Description(s)|
|in production||2015-05-21 09:46 PT||
|in production||2015-05-14 16:55 PT||
|in production||2015-05-14 07:26 PT||
|in production||2015-05-11 11:32 PT||
|in production||2015-05-08 07:31 PT||
|in production||2015-05-07 14:44 PT|
|in production||2015-05-07 09:41 PT||
|in production||2015-05-06 11:02 PT||
|in production||2015-05-04 09:40 PT||