Closed
Bug 504791
Opened 15 years ago
Closed 15 years ago
version-bump.pl doesn't know how to bump comm-central branch version files
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
References
Details
Attachments
(1 file)
1.81 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
As comm-central allows both builds with a branch repository and mozilla-central, we have multiple $(app)/config/version*.txt files to state different versions based on the platform we are building with. I just wanted to start the SeaMonkey 2.0b1 builds and the tag factory failed with version-bump.pl not knowing what the version-191.txt file is that we need to bump there. The solution is to match any $(app)/config/version*.txt file in the part of version-bump.pl that determines in what way to bump that file. I have tested that this patch works correctly with both version.txt and version-191.txt files and I need it ASAP to be able to build SeaMonkey 2.0 Beta 1.
Attachment #389108 -
Flags: review?(bhearsum)
Assignee | ||
Comment 1•15 years ago
|
||
Degrading to major as it's still a blocker for using release automation with the main build/tools repo but I ran SM2.0b1 build1 successfully with the patch on a cloned repo in seabld's private space and re-importing the verify-config changesets into build/tools.
Severity: critical → major
Updated•15 years ago
|
Attachment #389108 -
Flags: review?(bhearsum) → review+
Comment 2•15 years ago
|
||
Comment on attachment 389108 [details] [diff] [review] match any $(app)/config/version*.txt file Looks fine to me. Feel free to land this anytime, and please add it to the Maintenance wiki page.
Assignee | ||
Comment 3•15 years ago
|
||
Pushed as http://hg.mozilla.org/build/tools/rev/0da82dfb9dc5 - adding to the wiki now. Thanks.
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
•