ReleaseEngineering/Maintenance: Difference between revisions
ChrisCooper (talk | contribs) (reconfig) |
ChrisCooper (talk | contribs) (reconfig) |
||
Line 38: | Line 38: | ||
| style="background:#cccccc" | '''When''' | | style="background:#cccccc" | '''When''' | ||
| style="background:#cccccc" | '''Bug #(s)''' - '''Description(s)''' | | style="background:#cccccc" | '''Bug #(s)''' - '''Description(s)''' | ||
|- | |||
| in production | |||
| 2015-07-30 12:54 PT | |||
| | |||
<div style="border: thin grey solid; background-color: lightgrey; float: right; text-align: right; text-size: 80%; padding-left: 5px; padding-right: 5px;"> | |||
[https://bugzilla.mozilla.org/buglist.cgi?bug_id=1184117,1184594,1187966,1188648,1188698,1189273&query_format=advanced&order=bug_status%2Cbug_id&tweak=1 View list in Bugzilla] | |||
</div> | |||
[https://hg.mozilla.org/build/buildbot-configs buildbot-configs] | |||
* {{bug|1184117}} - Make Android 4.0 opt-in by default on Try - r=Callek ([https://hg.mozilla.org/build/buildbot-configs/rev/e7176ef993ef e7176ef993ef]) | |||
* {{bug|1189273}} - Drop twice-daily nightlies for v2.2/v2.2r and stop running emulator nightly builds on the B2G release branches - r=catlee ([https://hg.mozilla.org/build/buildbot-configs/rev/fbd3abad6d6b fbd3abad6d6b]) | |||
[https://hg.mozilla.org/build/buildbotcustom buildbotcustom] | |||
* {{bug|1187966}} - Set the env for periodic file update jobs so we can use TOOLTOOL_CACHE = - r=nthomas ([https://hg.mozilla.org/build/buildbotcustom/rev/dc0535892866 dc0535892866]) | |||
[https://hg.mozilla.org/build/mozharness mozharness] | |||
* {{bug|1184594}} - git 'repo' is not deployed correctly on build machines managed by buildbot - r=hwine ([https://hg.mozilla.org/build/mozharness/rev/57dde819edcb 57dde819edcb]) | |||
* {{bug|1188648}} - Use HOST_LOG env var to log gecko output when running Gij on _all_ gecko builds - r=jgriffin ([https://hg.mozilla.org/build/mozharness/rev/79fffa3a18ae 79fffa3a18ae]) | |||
* {{bug|1188648}} - Always log gecko output during Gaia JS Integration Tests - r=jgriffin ([https://hg.mozilla.org/build/mozharness/rev/d72df953784c d72df953784c]) | |||
* {{bug|1188698}} - Do not fail when succeed count is 0 ([https://hg.mozilla.org/build/mozharness/rev/672af8a8da3e 672af8a8da3e]) | |||
* No bug - Backed out changeset 79fffa3a18ae -- Unfortunately try run reveals this isn't working as expected ([https://hg.mozilla.org/build/mozharness/rev/faf4013a7fc6 faf4013a7fc6]) | |||
* No bug - Backed out changeset 57dde819edcb ([https://hg.mozilla.org/build/mozharness/rev/3ae81f4458ef 3ae81f4458ef]) | |||
|- | |- | ||
| in production | | in production |
Revision as of 19:54, 30 July 2015
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.
Relevant repositories
Non-releng repositories involved in the CI
Treeherder
- 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)
Mozharness deployments
Merges to the production branch of the mozharness repository are live immediately. Please see that repo for push history.
Puppet deployments
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.
Older changes are archived in: 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009
Outcome | When | Bug #(s) - Description(s) |
in production | 2015-07-30 12:54 PT |
|
in production | 2015-07-24 12:15 PT |
|
in production | 2015-07-23 11:11 PT |
|
in production | 2015-07-22 13:13 PT |
|
in production | 2015-07-22 13:03 PT |
|
in production | 2015-07-22 07:58 PT |
|
in production | 2015-07-21 07:06 PT |
|
in production | 2015-07-17 10:43 PT |
|
in production | 2015-07-10 13:36 PT |
|
in production | 2015-07-09 18:06 PT |
|
in production | 2015-07-06 13:12 PT |
|
in production | 2015-07-01 15:25 PT |
|
in production | 2015-06-29 11:35 PT |
|
in production | 2015-06-16 08:00 PT |
|
in production | 2015-06-16 08:26 PT |
|
in production | 2015-06-05 14:55 PT |
|
in production | 2015-06-02 16:00 PT |
|
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 |
|