Closed
Bug 613229
Opened 15 years ago
Closed 15 years ago
release tagging scripts should use shared source
Categories
(Release Engineering :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(2 files, 1 obsolete file)
|
2.52 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
|
1.27 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Turns out that they use clone() instead of mercurial() currently, which bypasses potential share usage.
|
Assignee | |
Comment 2•15 years ago
|
||
|
|
Assignee | |
Comment 3•15 years ago
|
||
|
|
Assignee | |
Comment 4•15 years ago
|
||
Comment on attachment 502912 [details] [diff] [review]
use shared source in tagging
This patch worked fine in staging, but I did discover that we don't have rebase or mq enabled on the Linux build machines, which breaks our push race protection regardless of shared source usage or not :-(. I filed bug 625121 on that.
Attachment #502912 -
Flags: review?(catlee)
|
|
Assignee | |
Comment 5•15 years ago
|
||
Attachment #502916 -
Attachment is obsolete: true
Attachment #503219 -
Flags: review?(catlee)
|
|
Assignee | |
Updated•15 years ago
|
Attachment #502912 -
Attachment description: [untested] use shared source in tagging → use shared source in tagging
|
||
Updated•15 years ago
|
Attachment #502912 -
Flags: review?(catlee) → review+
|
|
||
Updated•15 years ago
|
Attachment #503219 -
Flags: review?(catlee) → review+
|
|
Assignee | |
Comment 6•15 years ago
|
||
Comment on attachment 502912 [details] [diff] [review]
use shared source in tagging
changeset: 1995:9d809129322d
Attachment #502912 -
Flags: checked-in+
|
|
Assignee | |
Comment 7•15 years ago
|
||
Comment on attachment 503219 [details] [diff] [review]
updated patch, tested and working
changeset: 1427:605dd9f0fdce
Attachment #503219 -
Flags: checked-in+
|
|
Assignee | |
Comment 8•15 years ago
|
||
This went to production today.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 9•15 years ago
|
||
I made a stupid typo in the posted patch (that I had fixed locally on the staging master), I had to push this bustage fix: http://hg.mozilla.org/build/buildbotcustom/rev/ba033184af1e
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•