We'd like to get to the point where we can schedule all jobs in-tree, with many of them still executed via the buildbot bridge. At this point, the future is hazy as to how possible that is and what prevents it. Possible prerequisites include: * More / better access control for BBB (e.g., bug 1226018) * Credentials handling in BBB (pass temp creds from a task to BBB, rather than using on-slave permacreds) * Overhaul the in-tree graph generation system from the current yaml inheritance * Connect jobs to hooks for nightly, periodic runs * Some kind of stable storage for state that's kept from one graph to the next (e.g., jobs that run every 4 pushes, or SETA)

> * Overhaul the in-tree graph generation system from the current yaml > inheritance This work will be tracked in bug 1243844

> * Some kind of stable storage for state that's kept from one graph to the > next (e.g., jobs that run every 4 pushes, or SETA) Bug 1252568 is to give TC the ability to determine what Buildbot jobs to schedule. We're pretty far from working on it. We can determine the proper way to proceed depending on where we are with bug 1247703.

It's not clear we still want to do this -- Joel?

I've noted your comments in the BBB scope document https://docs.google.com/document/d/1TVfvL3DVuki8o4tcUbKxZa7v3gbr1uDZ9aXBfcoirxI/edit If any of these items need to move ahead we'll need to add a section into the project task schedule.

I don't think this is a useful tracker anymore -- it doesn't align with any of our OKRs or milestones.