Closed
Bug 512303
Opened 15 years ago
Closed 15 years ago
need to ensure that only one production buildbot instance is polling a candidates dir at a time
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bhearsum, Unassigned)
References
Details
While doing Firefox 3.5.3 I realized that it was possible for both production-master and production-master02 to be polling the 3.5.3 candidates dir at the same time. If they were, they both would've kicked off l10nverify, updates, and verify steps, which would've been bad. Luckily, I only reconfig'ed one instance for this release so the other was still polling 3.6a1-candidates. We need to ensure this doesn't happen in the future. Possibly through one of these means: * Always using different release-* configs for each master * Turning off polling except when it's needed
Reporter | ||
Updated•15 years ago
|
Assignee: nobody → bhearsum
Reporter | ||
Comment 1•15 years ago
|
||
Not going to get to this for awhile
Assignee: bhearsum → nobody
Component: Release Engineering → Release Engineering: Future
Reporter | ||
Comment 2•15 years ago
|
||
Now that we point different masters to different release configs this isn't such an issue.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Comment 3•14 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•