Closed
Bug 1473428
Opened 6 years ago
Closed 6 years ago
release-update-verify-config fails on Try
Categories
(Release Engineering :: Release Automation: Updates, enhancement)
Release Engineering
Release Automation: Updates
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Unassigned)
References
Details
I think this may be a number of factors: - I specified 61.0b15 build 4 as the partial version. I think this works on maple, so that's probably not it - aha, we have `maple` in various `by-project` blocks, but not `try` [1] - the Try version is 63.0a1; we may hardcode version assumptions into it. I think that's smart for prod, but a little restrictive on Try; we may want to allow for relaxing those restrictions on Try. - something else Updating the by-project blocks to allow for some testing on Try seems easy enough. We'll probably be hardcoded to always assume beta or rc behavior unless someone edits the kind; ideally we could add a way to easily override that on Try. [1] https://hg.mozilla.org/mozilla-central/file/default/taskcluster/ci/release-update-verify-config/kind.yml#l32
Reporter | ||
Comment 1•6 years ago
|
||
Example failed task, which won't stick around forever: https://tools.taskcluster.net/groups/JzDg_-vqQDei9xN7fg_wLQ/tasks/Q0gXJl6aSLSUpjtR1hOTfw/details
Comment 2•6 years ago
|
||
This was fixed as part of the try-staging work.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•