482252 - move Firefox 3.1/3.5 builds to Firefox3.5 tinderbox

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[[e-mail] (:bhearsum)]

I'm going to see if we can simply "rename" it, to keep history and such. If not, we'll have to create a new one and delete Firefox3.1

Comment 1

[[e-mail] (:bhearsum)]

Attachment: move mozilla-1.9.1 builds to Firefox3.5 tinderbox

Alice, I think this is all that needs to be done for Talos, is that right?

Comment 2

[[e-mail] (:bhearsum)]

I talked to justdave about this and he told me we can just move the Firefox3.1 tinderbox. I'll coordinate with someone from IT during the downtime to get this done.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 366589 [details] [diff] [review]
move mozilla-1.9.1 builds to Firefox3.5 tinderbox

r+ for the mozilla2/config.py
 part

Comment 4

[alice nodelman [:alice] [:anode]]

Comment on attachment 366589 [details] [diff] [review]
move mozilla-1.9.1 builds to Firefox3.5 tinderbox

This covers the talos changes, but graph server will also have to be updated to reflect the new tree name - that will require a sql patch that should be applied at the same time as the talos changes are pushed.  There may be some interim red during the changeover if any straggling talos boxes attempt to report under the old name.

Comment 5

[[e-mail] (:bhearsum)]

Can you point me to what to patch for that, Alice? And how does rollout happen? IT ticket?

Comment 6

[alice nodelman [:alice] [:anode]]

You'll need to run:

update branches set name = "Firefox3.5" where name = "Firefox3.1";

On the db for graphs-new.m.o, it should go through justdave.

Comment 7

[[e-mail] (:bhearsum)]

Comment on attachment 366589 [details] [diff] [review]
move mozilla-1.9.1 builds to Firefox3.5 tinderbox

changeset:   1016:47161a4de858

Comment 8

[[e-mail] (:bhearsum)]

buildbot master has been reconfig'ed for this.