Closed Bug 496491 Opened 12 years ago Closed 11 years ago
[Bootstrap] Move update verify bumping to Updates step
This is the Bootstrap (Tb2 & Fx3) equivalent of bug 486454. Basically, doing the config bump for update verify on each platform doesn't work so well when the config lives in a hg repository.
Assignee: nobody → nthomas
Status: NEW → ASSIGNED
Priority: -- → P2
Only passes perl -c at this point. Will test in staging.
tripped over this during TB220.127.116.11 release.
(In reply to comment #2) > tripped over this during TB18.104.22.168 release. Yes, this is a problem in RELEASE_AUTOMATION_M13 and M14.
Comment on attachment 382438 [details] [diff] [review] WIP, tested I tested this on staging-1.9, to make sure that it could reproduce the bump from 3.0.11 build1 to build2 bump. It did that, modulo the hostname changes that come with staging. Had to jump through a bunch of hoops to setup staging but I'm pretty confident this will work fine in production. Patch also fixes pulling shipped-locales from the relbranch rather than the release tag, when updating the patcher config.
(In reply to comment #4) > (From update of attachment 382438 [details] [diff] [review]) > I tested this on staging-1.9, to make sure that it could reproduce the bump > from 3.0.11 build1 to build2 ... for both the patcher and update verify configs.
Do we want to have this for Fx3.0.12 ?
Comment on attachment 382438 [details] [diff] [review] WIP, tested Sorry this sat for so long, looks good though.
Attachment #382438 - Flags: review?(bhearsum) → review+
Comment on attachment 382438 [details] [diff] [review] WIP, tested Checking in Bootstrap/Step/PatcherConfig.pm; /cvsroot/mozilla/tools/release/Bootstrap/Step/PatcherConfig.pm,v <-- PatcherConfig.pm new revision: 1.24; previous revision: 1.23 done Checking in Bootstrap/Step/Updates.pm; /cvsroot/mozilla/tools/release/Bootstrap/Step/Updates.pm,v <-- Updates.pm new revision: 1.49; previous revision: 1.48 done And tagged as RELEASE_AUTOMATION_M15.
Attachment #382438 - Flags: checked‑in+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.