I think we can treat build tasks with no associated tests just like test tasks: we don't need those builds ready for backfilling purposes. The same smart scheduler we use to schedule tests could easily be modified to schedule build tasks as well. The main benefit of this is that these optimizations will be handled automatically without us having to 1) notice build tasks that can be moved to backstop pushes/m-c only; 2) figure out if they can actually be moved and what the drawbacks are; 3) figure out what the cost savings are to see if the benefits outweigh the drawbacks; 4) convince people it's the right thing. See for example bug 1636902 or bug 1603255. So, it'd clearly save us time.
Bug 1637810 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think we can treat build tasks with no associated tests just like test tasks: we don't need those builds ready for backfilling purposes. The same smart scheduler we use to schedule tests could easily be modified to schedule build tasks as well. The main benefit of this is that these optimizations will be handled automatically without us having to 1) notice build tasks that can be moved to backstop pushes/m-c only; 2) figure out if they can actually be moved and what the drawbacks are; 3) figure out what the cost savings are to see if the benefits outweigh the drawbacks; 4) convince people it's the right thing. See for example bug 1636902 or bug 1637542. So, it'd clearly save us time.