Closed Bug 1252568 Opened 9 years ago Closed 8 years ago

Prorotype in-tree Buildbot SETA scheduling via re-written SETA

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: armenzg, Unassigned)

References

Details

I was filing a bug to schedule jobs through TC/BBB instead of through Buildbot scheduling, however, I determined that we can't do it until we can do SETA analysys for Buildbot in the gecko decision task. Bug 1243123 will add SETA support to the gecko decision task. This bug would be the next step towards moving Buildbot scheduleing to TC. This might get picked up in the tail end of the GsoC project. CCing a bunch of people in case you have something you would like to add.
Blocks: 1252574
We could experiment on alder for this. Once we have the prototype working we can start switch over to scheduling most Buildbot jobs in-tree (bug 1252574).
I'm confused -- is this bug just announcing the existence of bug 1243123? Note that we already have bug 1243759 for in-tree scheduling of all jobs.
(In reply to Dustin J. Mitchell [:dustin] from comment #2) > I'm confused -- is this bug just announcing the existence of bug 1243123? > Note that we already have bug 1243759 for in-tree scheduling of all jobs. I want this bug to be specific to Buildbot (where we have SETA through Buildbot scheduling) rather than the work specific to TaskCluster. I could not find bug 1243759. Thanks!
Blocks: 1243759
Can you update the summary, then?
Summary: Once we have SETA support in the decision task we can look into switching to BBB for builds/tests → Prorotype in-tree Buildbot SETA scheduling via re-written SETA
Moving to TaskCluster component...
Component: TaskCluster → Integration
Product: Testing → Taskcluster
(In reply to Armen Zambrano [:armenzg] - Engineering productivity from comment #3) > I want this bug to be specific to Buildbot (where we have SETA through > Buildbot scheduling) rather than the work specific to TaskCluster. So, not a TC bug..
Component: Integration → General Automation
Product: Taskcluster → Release Engineering
QA Contact: catlee
No longer depends on: 1243123
No longer blocks: 1243759
(In reply to Armen Zambrano [:armenzg] (EDT/UTC-4) from comment #0) > I was filing a bug to schedule jobs through TC/BBB instead of through > Buildbot scheduling, however, I determined that we can't do it until we can > do SETA analysys for Buildbot in the gecko decision task. > > Bug 1243123 will add SETA support to the gecko decision task. This bug would > be the next step towards moving Buildbot scheduleing to TC. > > This might get picked up in the tail end of the GsoC project. > > CCing a bunch of people in case you have something you would like to add. Hey Armen, do you want me to work on this issue?
Hi MikeLing, Thanks for offering, however, I don't think the idea of switching scheduling of Buildbot jobs via TaskCluster (using the BBB) is something we want to push. One of the reasons is that the BBB has been known to have some race conditions and we could hit that probably very easily if we also start using it for per-push scheduling. Right now it is only being used for FF releases and it has produced quite some headaches to the releng team. Thanks though for your offer!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.