Closed
Bug 1732929
Opened 4 years ago
Closed 3 years ago
release-bouncer-aliases doesn't run on try
Categories
(Release Engineering :: Release Automation, defect, P3)
Release Engineering
Release Automation
Tracking
(firefox113 fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox113 | --- | fixed |
People
(Reporter: bhearsum, Assigned: jcristau)
References
Details
Attachments
(1 file)
The by-project on https://searchfox.org/mozilla-central/source/taskcluster/ci/release-bouncer-aliases/kind.yml#46 means it always ends up empty on try.
|
Assignee | |
Updated•4 years ago
|
Severity: -- → S4
Priority: -- → P3
|
|
Assignee | |
Comment 1•3 years ago
|
||
Can you think of a reason why these shouldn't be by-release-type instead?
Flags: needinfo?(bhearsum)
|
Reporter | |
Comment 2•3 years ago
|
||
(In reply to Julien Cristau [:jcristau] from comment #1)
Can you think of a reason why these shouldn't be by-release-type instead?
I cannot! I'm guessing that the historical reason is that we didn't have a useful staging bouncer instance...but I can't prove that, and it's certainly not true at this point.
Flags: needinfo?(bhearsum)
|
|
Assignee | |
Comment 3•3 years ago
|
||
|
||
Updated•3 years ago
|
Assignee: nobody → jcristau
Status: NEW → ASSIGNED
Pushed by jcristau@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b26c49cd856b
use release_type parameter in release-bouncer-aliases task config r=bhearsum DONTBUILD
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
|
||
Updated•1 year ago
|
Component: Release Automation: Bouncer → Release Automation
You need to log in
before you can comment on or make changes to this bug.
Description
•