We're currently on 0.8.2. Upgrading to 0.8.3 includes a fix for how a master maintains it claim over active jobs. This is used to detect, reclaim & retrigger jobs whenever another master dies. This came up over the weekend after the colo outage, when we saw jobs being run, and then being run again an hour later.
We could also just backport the fix. I only vaguely remember which fix you're talking about, so I'll need to look at the buildbot revision history to see what it was.
Ah, not the change I was thinking of, but a good change to merge all the same. Catlee, what do you think about using 0.8.3 vs. continuing to backport into 0.8.2?
(In reply to comment #3) > Ah, not the change I was thinking of, but a good change to merge all the same. > > Catlee, what do you think about using 0.8.3 vs. continuing to backport into > 0.8.2? 0.8.3 is a relatively minor update from 0.8.2 I think? If so, we should plan on upgrading to 0.8.3, since 0.8.4 is going to be a bigger jump, and will take longer to validate.
Should we upgrade to buildbot0.8.5 (which was released on 18sep2011)?
Product: mozilla.org → Release Engineering
Found in triage. I think this belongs in PlatformSupport, but please bounce if I guessed incorrectly. (In reply to John O'Duinn [:joduinn] from comment #5) > Should we upgrade to buildbot0.8.5 (which was released on 18sep2011)? Tweaking summary, as latest release of buildbot is now v0.8.7 (as of 21aug2013), with 0.8.8rc1 available for upcoming 0.8.8 release.
Component: Other → Platform Support
Summary: Upgrade buildbot masters to buildbot-0.8.3 → Upgrade buildbot masters to more recent version of buildbot
Definitely not doing this, we're moving to Taskcluster!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
QA Contact: coop
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.