Open
Bug 1452163
Opened 7 years ago
Updated 3 months ago
[scriptworker] Move scope handling to scriptworker
Categories
(Release Engineering :: Release Automation, enhancement)
Release Engineering
Release Automation
Tracking
(Not tracked)
NEW
People
(Reporter: tomprince, Unassigned)
References
Details
In Bug 1421062, I added support for using different taskcluster scope prefixes to all the scriptworkers to support having different scopes for thunderbird
Each of the scriptworkers has almost identical functions `get_task_{server,action,bucket}`. There is no reason for these functions to be duplicated in each script.
Additionally, the configuration for the scope prefix includes the worker type. The in-tree code hard-codes the script-type in the scope, so the workers should do the same. (i.e. the specified scope prefix is `project:releng:` instead of `project:releng:<script-type>:`.
Updated•2 years ago
|
Severity: normal → S3
Updated•3 months ago
|
QA Contact: catlee
You need to log in
before you can comment on or make changes to this bug.
Description
•