Closed Bug 482252 Opened 12 years ago Closed 12 years ago
move Firefox 3
.1/3 .5 builds to Firefox3 .5 tinderbox
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
Assignee: nobody → bhearsum
Priority: -- → P3
Alice, I think this is all that needs to be done for Talos, is that right?
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 on attachment 366589 [details] [diff] [review] move mozilla-1.9.1 builds to Firefox3.5 tinderbox r+ for the mozilla2/config.py part
Attachment #366589 - Flags: review?(nthomas) → review+
Attachment #366589 - Flags: review?(anodelman) → review+
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.
Can you point me to what to patch for that, Alice? And how does rollout happen? IT ticket?
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 on attachment 366589 [details] [diff] [review] move mozilla-1.9.1 builds to Firefox3.5 tinderbox changeset: 1016:47161a4de858
Attachment #366589 - Flags: checkedâ€‘in+ checked‑in+
buildbot master has been reconfig'ed for this.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.