1198430 - Prototype a way to push to try which schedules all buildbot jobs through TaskCluster

Status: RESOLVED WONTFIX

(Testing :: General, defect)

Description

[Armen [:armenzg]]

This would help us fix issues that cannot be easily fixed without touching buildbot-configs (bug 1116275).

For now, we could add --schedule-buildbot as a way for the Gecko decision task to include Buildbot jobs.

This is a step to make Buildbot scheduling more self-serve.

This bug would not include switching over to this model OR to disable the buildbot scheduling for Try. For now, it would look like twice the number of jobs.

Making this model be the default would also have further beefits:
* This moves the try syntax parsing to the tree which allow us to:
** easily expand on the try syntax
** add unit tests to the try syntax
* It helps us do the leg work to transition to TaskCluster

Comment 1

[Armen [:armenzg]]

Some of this work is still landed on alder.

This depends on bug 1197204.

Switching to this model would require fixing bug 1197239 or move "make check" from the builds (bug 992323).

Comment 2

[u429623]

(In reply to Armen Zambrano Gasparnian [:armenzg] from comment #0)
> For now, it would look like twice the number of
> jobs.

Twice the number of jobs is fine, but twice the load on git.mozilla.org is not. Please don't deploy this without signoff from the vcs folks.

There are several efforts underway to address the capacity issue, and improve the scalability of both BB & TC slaves. So, with luck, the problem will be solved by the time this is ready for testing.

But please double check.

Comment 3

[Armen [:armenzg]]

Thanks Hal.
The only work for this bug is to simply show that we can do it and land some code to make it easy to push it to try to test the system still works.
There are various blockers and we will talk more about it in Q4 and won't switch to this approach unless vcs signs off.

Comment 4

[Armen [:armenzg]]

We won't be spending time on this.