Closed Bug 1316340 Opened 4 years ago Closed 3 years ago

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

Categories

(Release Engineering :: Release Automation: Other, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Unassigned)

References

Details

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".
Assignee: nobody → rail
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....
Depends on: 1316593
Depends on: 1318253
Assignee: rail → nobody
Priority: -- → P3
I think Rail fixed this in releasetasks, and we use the standard graph logic in Fx59+ via in-tree decision tasks.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.