774425 - Tracking bug for August 27, 2012 migration work

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

+++ This bug was initially created as a clone of Bug #764909 +++

This bug is to track the changes releng need to make for the next migration day. This includes things like mozconfig changes, moving new slaves up to the next trains, etc.

Comment 1

[Justin Wood (:Callek)]

Attachment: [buildbot-configs] v1 - MERGE DAY stuff for -release/Firefox 15

Comment 2

[Chris Cooper [:coop] (he/him)]

Comment on attachment 654918 [details] [diff] [review]
[buildbot-configs] v1 - MERGE DAY stuff for -release/Firefox 15

Review of attachment 654918 [details] [diff] [review]:
-----------------------------------------------------------------

A good start, but there's still more work to do. 

Check (thunderbird_)config.py under both mozilla/ and mozilla-test/...there *should be* sections in both marked with changes for Fx17 that are riding the trains. We can remove aurora from those special case blocks on merge day too.

Comment 3

[Chris Cooper [:coop] (he/him)]

Comment on attachment 654918 [details] [diff] [review]
[buildbot-configs] v1 - MERGE DAY stuff for -release/Firefox 15

Landed, modulo the armv6 changes that are now targeted for Firefox 16 (based on bug 775232):
https://hg.mozilla.org/build/buildbot-configs/rev/ad33d528a3bd

Comment 4

[Chris Cooper [:coop] (he/him)]

In production.

Comment 5

[Aki Sasaki (not active)]

Attachment: missed merge day items from buildbot-configs

Comment 6

[Aki Sasaki (not active)]

Comment on attachment 655845 [details] [diff] [review]
missed merge day items from buildbot-configs

http://hg.mozilla.org/build/buildbot-configs/rev/ba4287240484

Comment 8

[Mark Banner (:standard8)]

Just a small reminder: this still needs to be done for the Thunderbird configs (specifically the disabling of 10.5 on aurora) as can be found from:

http://mxr.mozilla.org/build/search?string=MERGE+DAY&find=&findi=&filter=^[^\0]*%24&hitlimit=&tree=build

Comment 9

[[e-mail] (:bhearsum)]

Attachment: disable lion on comm-aurora

Comment 10

[Alex Keybl [:akeybl]]

Does the merge need to complete for these changes to be made? Or can they be done in parallel with future merges? We closed the trees at around 12PM PT yesterday, so my feeling is we could have done much of this at that time.

Comment 11

[Alex Keybl [:akeybl]]

(that last comment is in reference to bug 786134 fyi)

Comment 12

[Aki Sasaki (not active)]

Hm, I thought I responded to that, but I don't see my reply.

We can do these changes in parallel to the merge, and had them marked as merge day items in code (e.g. http://hg.mozilla.org/build/buildbot-configs/rev/ba4287240484#l1.121 ).

We didn't have tracking bugs for them specifically, and no one specifically responsible for tracking those merge day items down (no assignee for this bug).  I think one of those two, or a combination of the two, would help us avoid missing things next merge day.

Comment 13

[[e-mail] (:bhearsum)]

Comment on attachment 655972 [details] [diff] [review]
disable lion on comm-aurora

This got accidentally committed yesterday anyways =\. Already in production.

Comment 14

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum [:bhearsum] from comment #13)
> Comment on attachment 655972 [details] [diff] [review]
> disable lion on comm-aurora
> 
> This got accidentally committed yesterday anyways =\. Already in production.

https://hg.mozilla.org/build/buildbot-configs/rev/1f11adf95f57