Closed
Bug 537461
Opened 15 years ago
Closed 15 years ago
switch CC* release automation to chatzilla-from-hg
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
References
Details
Attachments
(1 file)
16.22 KB,
patch
|
gozer
:
review+
|
Details | Diff | Splinter Review |
Now that bug 524682 is fixed on comm-central and 1.9.1, we can remove the ugly hacks in buildbotcustom that deal with pulling chatzilla from cvs and switch to the same hg stuff we have for the rest.
I'll look into that but possibly need to do SM 2.0.2 from the old model and relbranch first.
![]() |
Assignee | |
Comment 1•15 years ago
|
||
This patch should do everything needed and still results in a good checkconfig for SeaMonkey together with the config update in http://hg.mozilla.org/build/buildbot-configs/rev/dede06bd8ee9 (ignore the bogus and buggy l10n-changesets change in there) - I don't have a staging setup or a post-cz-on-hg release to cut atm, so I didn't actually do a test run with this, but usually that's less of a problem than getting all the var definitions right which a checkconfig does actually check for.
Attachment #421635 -
Flags: review?(gozer)
Updated•15 years ago
|
Attachment #421635 -
Flags: review?(gozer) → review+
![]() |
Assignee | |
Comment 2•15 years ago
|
||
Thanks, pushed as http://hg.mozilla.org/build/buildbotcustom/rev/b616aa1ece20
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•