Closed Bug 616470 Opened 15 years ago Closed 14 years ago

Pick up buildbot code for not needing to close the tree during tagging

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect, P2)

Product:
Mozilla Messaging Graveyard
Component:
Release Engineering
Type:
defect

Tracking

(blocking-thunderbird5.0 alpha3+)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
blocking-thunderbird5.0 --- alpha3+

People

(Reporter: standard8, Unassigned)

References

Details

(Whiteboard: [non-code])

Firefox has made some changes to their buildbot release mechanism so that they no-longer require the tree to be closed. This basically comes down to handling push conflicts.
Bug 508896 implemented this for Firefox. Apparently its basically all there in buildbot 0.8 (although probably not too hard to backport). So we could just make this depend on updating to 0.8 and pick up the other nice things they are doing as well (e.g. only building nightlies based on the last green changeset though we'd probably need more work for us with that).
Blocks: 540394
gozer, did we get this with the 0.8 upgrade?
Assignee: nobody → gozer
Nope. This depends on a lot of release automation stuff we need to catch up on (Bug 609337)
Depends on: 609337
blocking-thunderbird5.0: --- → alpha3+
Whiteboard: [non-code]
I'm going to want this for the next trunk release, probably within about 2 weeks.
Priority: -- → P2
Depends on: 626208
Depends on: 636208
No longer depends on: 626208
I don't recall us having to close the tree for tagging in ages. Is this no longer a problem?
I think we haven't yet got the code which means that we wouldn't be at risk of this. The bit that has mitigated us is having a dead quiet tree (i.e. comm-beta/comm-release) so there aren't lots of checkins. I think this would be fixed by migrating all our stuff to the Firefox infra and actually picking up the latest code which handles this properly.
Assignee: gozer → nobody
Yea TB side moving to Firefox infra will fix this, SeaMonkey Side I do plan to tackle this relatively soon. That said, the close-tree is near-not-needed since it is a dead-quiet-tree and SeaMonkey assures itself not to run while TB is doing tagging runs, so we don't have conflicts.
This is happening as part of bug 698843
Depends on: 698843
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.