Use task-level dependencies in release promotion tasks instead of graph's "requires"

RESOLVED FIXED

Status

Release Engineering
Release Automation: Other
P3
normal
RESOLVED FIXED
2 years ago
4 months ago

People

(Reporter: rail, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
It would be great to migrate existing release tasks to use inter task dependencies (see https://docs.taskcluster.net/reference/platform/queue/task, "dependencies") instead of graph API's "requires".
(Reporter)

Updated

2 years ago
Assignee: nobody → rail
(Reporter)

Comment 1

2 years ago
Just tried to submit a graph and hit another issue. Maximum amount of dependencies that you can have is 100 according to http://schemas.taskcluster.net/queue/v1/create-task-request.json#. D'oh.

Probably we should also test our tasks against the schemas....
(Reporter)

Updated

2 years ago
Depends on: 1316593
(Reporter)

Updated

2 years ago
Depends on: 1318253
(Reporter)

Updated

2 years ago
Assignee: rail → nobody
(Reporter)

Updated

a year ago
Priority: -- → P3

Comment 3

4 months ago
I think Rail fixed this in releasetasks, and we use the standard graph logic in Fx59+ via in-tree decision tasks.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.