Closed Bug 594435 Opened 14 years ago Closed 13 years ago

[Tracking] Almost all steps of release automation should be run by buildbot

Categories

(Release Engineering :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 478420

People

(Reporter: rail, Assigned: rail)

References

Details

(Whiteboard: [tracking])

At the moment we have a lot of repetitive task we run by hand: virus scan, push to mirrors, backupsnip, pushsnip, etc.

We should script these steps and partition release process into 3 phases:

1. everything up to mirror push (already automated, except signing)
2. push to mirrors (virus scan, rsync, backup snippets, send some announces to r-d ML)
3. release (push snippets, update symlinks for stable releases)

Every phase should run unattended from the beginning to the end.
I agree 101% and I am hoping I will be allowed to take a lot of this work in the next two quarters since we can make this happen and improve the quality of our releases.
rail: is this a DUP (or subset?) of bug#478420?
(In reply to comment #2)
> rail: is this a DUP (or subset?) of bug#478420?

I'd prefer to have this bug as a subset, because I'm going to work on these specific pieces, but bug 478420 is too generic.
Depends on: 594930
Depends on: 540598
Priority: P4 → P5
Summary: Almost all steps of release automation should be run by buildbot → [Tracking] Almost all steps of release automation should be run by buildbot
Whiteboard: [tracking]
(In reply to comment #2)
> rail: is this a DUP (or subset?) of bug#478420?

You are right. No need to duplicate.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.