Asking for help with Windows CI resources

When this was discussed on Discord we saw two problems with the current pre-commit CI configuration right now:

  1. We don’t have enough runners, leading to very long wait times.
  2. The community doesn’t have full access to the buildkite configuration and it’s not clear how we can add more resources even if we had them.

Everyone I have talked to is of course very grateful that you managed to get this configuration working before and have maintained it. But our idea to migrate to GitHub was just to make sure that we don’t have a buss-factor of 1 and to increase the ability for us to help out.

Maybe this can be solved with Buildkite, more resources added to the pool, and access shared (and explained, I haven’t worked with BK before).

I think some of this has been raised in the other thread here [RFC] LLVM Precommit CI through Github Actions.

I am open to here suggestions on how we can reduce the wait for windows runners and how to improve access to the pre-commit ci. I think this can be handled differently from the discussion about moving to GitHub for now.

3 Likes