Closed Bug 1294065 Opened 9 years ago Closed 9 years ago

Describe "transitive closure" in taskgraph docs

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla51

People

(Reporter: dustin, Assigned: dustin)

Details

Attachments

(1 file)

From bug 1287018: Transitive closure is a fancy name for this sort of operation: * start with a set of nodes (without edges) * add all edges pointing away from any of those nodes, and any nodes attached to those edges * repeat until nothing changes The effect is this: imagine you start with a linux32 test job and a linux64 test job. So start with those two nodes. Each one depends on a docker image building task, so add the edge pointing to that docker task and the docker task itself. And each test task depends on a build task, so add the edges pointing to those build tasks, and the build tasks themselves. Then repeat: we already have everything that the test tasks point to. The docker tasks don't point to anything. But the build tasks point to different docker image build tasks (they run in a different image), so we add those edges and nodes. And repeat again. This time, there are no new edges or nodes to add, so we are done. And as you can see, the graph we've built now includes everything we wanted (the test jobs) plus everything required to do that (docker images, builds).
Assignee: nobody → dustin
Attachment #8779756 - Flags: review?(garndt) → review+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
Component: Documentation → Services
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: