Closed Bug 375788 Opened 17 years ago Closed 16 years ago

Stitch Repack, Update Generation, and Verification Steps together in Buildbot


(Release Engineering :: General, defect, P2)



(Not tracked)



(Reporter: mtschrep, Assigned: joduinn)




(2 files)

As part of our Build automation run we need to develop BB steps to do Repacks, Update Generation and Verification.
OS: Mac OS X → All
Hardware: PC → All
The current milestone bumping logic will always cause the automation to die();

The relevant part is:

The code will search for $versionString . 'pre' in the milestone.txt file, which it will never find (milestone.txt contains the gecko version, not the product version), and thus it will always hit the assertion.

This needs to be fixed before we can get steps working for any of the steps (including Build).
Depends on: 372759
Depends on: 378226
needed for "release automation", hence marking as critical.
Severity: normal → critical
Priority: -- → P1
Priority: P1 → P2
Down to P3 for this triage round.
Priority: P2 → P3
Update summary and reassigning to joduinn; he's going to take a look at this.
Assignee: preed → joduinn
Summary: Implement Repack, Update Generation, and Verification Steps in Buildbot → Stitch Repack, Update Generation, and Verification Steps together in Buildbot
Priority: P3 → P2
Stitching these steps together only makes sense now in the context of stitching all the build&release steps together. 

In bug#355309, there are two master.cfg files, one used for production, one used for staging, which were used to successfully create the FF2.0.0.7rc1 build last week. Those master.cfg files use more general purpose slaves, rather then step-specific slaves presented in both attachments here. Therefore marking this bug as a dup of bug#355309.
Closed: 16 years ago
Resolution: --- → DUPLICATE
QA Contact: mozpreed → build
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.