release_sanity.py should check both source and target repos in staging

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [automation])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

8 years ago
Created attachment 494389 [details] [diff] [review]
Check revision in 2 repos

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

8 years ago
Created attachment 499847 [details] [diff] [review]
Check revision in 2 sourceRepoPath
Attachment #494389 - Attachment is obsolete: true
Attachment #499847 - Flags: review?(bhearsum)
Attachment #494389 - Flags: review?(salbiz)
Attachment #499847 - Flags: review?(bhearsum) → review+
(Assignee)

Comment 2

8 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

8 years ago
Status: NEW → RESOLVED
Last Resolved: 8 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.