1197239 - Support to trigger dependent tasks once a mid point is reached

Status: RESOLVED WONTFIX

(Taskcluster :: Services, defect)

Description

[Armen [:armenzg]]

The way that buildbot works is that once the artifacts of a build are uploaded, we do a sendchange step which triggers the dependent tasks.
This is because all that the test jobs need is ready.
The build job continues past the sendchange step because it runs that make check step which can take 10-20 minutes depending on the task.
As-is, this would delay the starting of all of our tests.

This is probably not super urgent to fix since there are initiatives to get rid of the "make check" step after and upload, however, I wanted to file it just in case.

Adding ted since he might be aware of the "make check" removal work.

Comment 1

[(not currently active) Ted Mielczarek]

Getting rid of "make check" is bug 992323. We're getting pretty close, once chmanchester gets gtest running as a separate job we can probably mop up the rest easily.

Comment 2

[Jonas Finnemann Jensen (:jonasfj)]

Well, we could make the build task manually schedule the dependent task.
It's the sort of hack that can be justified if this a corner case and gains are huge.

But building a feature specifically for triggering dependents based on some artifact sounds dangerous.
There is something very simple and super powerful about having strict boundaries for when a task
triggers another task. Giving up simplicity of architecture can only be justified for HUGE gains.

Comment 3

[Armen [:armenzg]]

Fair enough. I'm OK if we ended up making the build task schedule the dependent task. 
I think getting the "make check" work done will help us here

Comment 4

[Pete Moore [:pmoore][:pete]]

Moving closed bugs across to new Bugzilla product "TaskCluster".