Closed Bug 610045 Opened 15 years ago Closed 15 years ago

Deploy buildbot-0.8.2

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

Having been tested in bug 607531, it's time to get buildbot-0.8.2 on the masters. From IRC, it looks like the way to do this is * land the upgrade (see https://bitbucket.org/djmitche/moz-buildbot/changesets) * deploy to the staging systems, restart * soak 24 hours * deploy to production masters * close tree * restart masters one by one * test some builds * open tree of course, I'm happy to be told to do it a different way!
Flags: needs-treeclosure?
cc'ing armen, since he's on build duty next week
long life to 0.8.2!
Let's block this for the moment on http://buildbot.net/trac/ticket/1043
Assignee: nobody → dustin
I'm staging 0.8.2 with this patch now, to see if build statuses come out right when a build contains a skipped step. I've added another patch to include VERSION in the 'default' branch: http://hg.mozilla.org/users/dmitchell_mozilla.com/buildbot/rev/e5b0d9774f2a as described here: https://wiki.mozilla.org/ReleaseEngineering/Upgrading_Buildbot This is running on sm02, and I'll leave it installed for the time being. Other than that, I think it's ready to land.
possibly blocked on http://buildbot.net/trac/ticket/1050 I'll be investigating shortly, when sm02 is free.
Status: NEW → ASSIGNED
deployment complete
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Flags: needs-treeclosure?
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.