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

Status: RESOLVED DUPLICATE of bug 355309

(Release Engineering :: General, defect, P2)

Description

[Mike Schroepfer]

As part of our Build automation run we need to develop BB steps to do Repacks, Update Generation and Verification.

Comment 1

[J. Paul Reed [:preed]]

The current milestone bumping logic will always cause the automation to die();

The relevant part is:

http://lxr.mozilla.org/mozilla/source/tools/release/Bootstrap/Step/Tag/Bump.pm#76

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).

Comment 2

[J. Paul Reed [:preed]]

Attachment: rhelmer's development master.cfg

Comment 3

[J. Paul Reed [:preed]]

Attachment: preed's development master.cfg

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

needed for "release automation", hence marking as critical.

Comment 5

[J. Paul Reed [:preed]]

Down to P3 for this triage round.

Comment 6

[J. Paul Reed [:preed]]

Update summary and reassigning to joduinn; he's going to take a look at this.

Comment 7

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

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.