comm-central builds incorrectly uploading symbols to staging symbol server.

RESOLVED FIXED in Thunderbird 59.0

Status

enhancement
RESOLVED FIXED
Last year
Last year

People

(Reporter: tomprince, Assigned: tomprince)

Tracking

Trunk
Thunderbird 59.0

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Assignee

Description

Last year
Since buildbot wasn't setting MOZ_SCM_LEVEL, the symbol upload script was concluding that we must be on a try branch, so uploaded symbols to the staging server.
Assignee

Updated

Last year
Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Comment hidden (mozreview-request)

Comment 2

Last year
mozreview-review
Comment on attachment 8944578 [details]
Bug 1432336: Set MOZ_SCM_LEVEL for level 3 comm branches;

https://reviewboard.mozilla.org/r/214738/#review220438
Attachment #8944578 - Flags: review?(nthomas) → review+

Comment 3

Last year
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/comm-central/rev/68c02fba54d2
Temporarily set SOCORRO_SYMBOL_UPLOAD_URL explicitly in mozconfig; rs=bustage-fix
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED

Comment 4

Last year
Backout by mozilla@hocat.ca:
https://hg.mozilla.org/comm-central/rev/cc883ed7c0a1
Backed out changeset 68c02fba54d2 : Don't set SOCORRO_SYMBOL_UPLOAD_URL explicitly; rs=bustage-fix
Assignee

Comment 5

Last year
Posted patch socorro-backout.patch (obsolete) — Splinter Review
Attachment #8946372 - Flags: approval-comm-beta?

Updated

Last year
Attachment #8946372 - Flags: approval-comm-beta? → approval-comm-beta+

Updated

Last year
Target Milestone: --- → Thunderbird 59.0

Comment 6

Last year
Comment on attachment 8946372 [details] [diff] [review]
socorro-backout.patch

Since https://hg.mozilla.org/comm-central/rev/68c02fba54d2 was landed on  2018-01-23, one day after the branch day, it was never on the beta branch, so I can't back it out there.
Attachment #8946372 - Attachment is obsolete: true
Attachment #8946372 - Flags: approval-comm-beta+
You need to log in before you can comment on or make changes to this bug.