Closed
Bug 1257245
Opened 9 years ago
Closed 7 years ago
releaserunner: update taskcluster-client.py
Categories
(Release Engineering :: Release Automation: Other, defect, P3)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rail, Unassigned)
References
Details
(Whiteboard: [releaseduty])
we use 0.0.24, which is old-ish. It has some issues (doesn't accept dashes and underscores in client IDs) and doesn't use nice slugIds. Watch out new deps: https://github.com/taskcluster/taskcluster-client.py/blob/master/setup.py#L29-L34
Reporter | ||
Comment 1•8 years ago
|
||
Just tried to use 0.3.3 and got this:
Traceback (most recent call last):
File "release-runner.py", line 443, in main
validate_graph_kwargs(queue, gpg_key_path, **kwargs)
File "release-runner.py", line 264, in validate_graph_kwargs
sanitize_en_US_binary(queue, task_id, gpg_key_path)
File "release-runner.py", line 205, in sanitize_en_US_binary
artifact
TypeError: buildSignedUrl() takes at most 3 arguments (4 given)
Looks like it may require some extra work.
Reporter | ||
Updated•8 years ago
|
Priority: -- → P3
Summary: releaserunner: update taskcluster.py → releaserunner: update taskcluster-client.py
Updated•7 years ago
|
Whiteboard: [releaseduty]
Reporter | ||
Comment 2•7 years ago
|
||
Let's wontfix this. release-runner3 uses the latest version of taskcluster-client and the original release-runner will die very soon.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•