> Maybe if you have burstable CI loads it's worth doing and re-rolling on failure. We have extremely bursty CI loads. One push can kick off up to 60 different

> Maybe if you have burstable CI loads it's worth doing and re-rolling on failure. We have extremely bursty CI loads. One push can kick off up to 60 different CI jobs. If a few people push at the same time, we easily have 300 jobs running in parallel. This happens the whole day long. It absolutely makes sense to self host this, since the cost to run this on Github runners would be prohibitive (Github runners are 8x the cost of the equivalent AWS instance I think). All our runners are ephemeral, so we only pay for them when they are actually running jobs. After all the jobs are over, the runners are immediately scaled to zero. I build this whole thing myself, so it's a bit sad to find someone had already built the whole thing before.