Add a shipitscript task that updates the Nightly version in shipit if necessary once the builds are in the Mozilla archive
Categories
(Firefox Build System :: Task Configuration, enhancement, P3)
Tracking
(firefox129 fixed)
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: gabriel, Assigned: gabriel)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Once we have an API to manage the Nightly version in shipit, and scriptworker support for calling this API, we need to add a task to the Nightly graph to trigger the worker's behavior once the builds are in the archive.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Backed out for causing Gecko decision task bustages in gecko_taskgraph.loader.transform
- Backout link
- Push with failures
- Failure Log
- Failure line: ModuleNotFoundError: No module named 'gecko_taskgraph.loader.transform'
| Assignee | ||
Comment 3•1 year ago
|
||
Comment 5•1 year ago
|
||
| bugherder | ||
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 6•1 year ago
|
||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
| bugherder | ||
Comment 9•1 year ago
|
||
Backed out for causing cron job failures.
- Backout link
- Push with failures
- Failure Log
- Failure line: requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http://taskcluster/queue/v1/task/O4NH5MWIRgS5wgVDBo4imA
Comment 10•1 year ago
|
||
I'm not a fan of how scopes work here. Until now mozilla-central hasn't needed to talk to production shipit, but if we grant it that scope then that also means it can create new releases, or mark them as shipped, for any and all products. That may not need to block this bug, but can we look at making things more granular?
| Assignee | ||
Comment 11•1 year ago
•
|
||
Thanks Julien.
So, grating project:releng:ship-it:server:production to mozilla-central would enable it to call all the actions on all the products?
That kinda sucks :C
Is it because we grant the actions to the gecko trust domain?
I see some references to "products" in the worker's client scopes, but they apply to all the gecko-3 workers.
...
project/releng/scriptworker/v2/shipit/prod/firefoxci-gecko-3:
description: ''
scopes:
- project:releng:services/shipit_api/update_product_channel_version/firefox
- project:releng:services/shipit_api/add_release/devedition
- project:releng:services/shipit_api/add_release/fennec
- project:releng:services/shipit_api/add_release/firefox
...
| Assignee | ||
Comment 12•1 year ago
•
|
||
Could we make it more granular using the project alias?
| Assignee | ||
Comment 13•1 year ago
|
||
I already landed patches to shipit to use the non-hard-coded version so it would be nice if I could close this bug before merge day. But, if I need more time to refactor the scopes... I can grant releng access to update the version in shipit (right now only the workers can call the API) and bump it myself (if I need to.)
| Assignee | ||
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
Pushed by gbustamante@mozilla.com:
https://hg.mozilla.org/ci/ci-configuration/rev/9f31d79ce94b
Grant the Nightly cron jobs scopes to run actions on the production ship-it server r=jcristau,releng-reviewers
Comment 16•1 year ago
|
||
Updated•1 year ago
|
Comment 17•1 year ago
|
||
| bugherder | ||
Description
•