Closed
Bug 615880
Opened 14 years ago
Closed 14 years ago
release_sanity.py should check both source and target repos in staging
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: rail)
Details
(Whiteboard: [automation])
Attachments
(1 file, 1 obsolete file)
|
1.13 KB,
patch
|
bhearsum
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
While running release_sanity.py for a staging release, I hit a condition when mozilla-central repo wasn't refreshed yet and had no needed revision to check. In this case we should check if the revision exists in the source repo. The attached patch should fix the problem.
Attachment #494389 -
Flags: review?(salbiz)
|
Assignee | |
Comment 1•14 years ago
|
||
Attachment #494389 -
Attachment is obsolete: true
Attachment #499847 -
Flags: review?(bhearsum)
Attachment #494389 -
Flags: review?(salbiz)
|
||
Updated•14 years ago
|
Attachment #499847 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Comment 2•14 years ago
|
||
Comment on attachment 499847 [details] [diff] [review] Check revision in 2 sourceRepoPath http://hg.mozilla.org/build/tools/rev/aff57c1ffe42
Attachment #499847 -
Flags: checked-in+
|
|
Assignee | |
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 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
•