Hey all, I am following up with the CI/credits situation. I have a proposal on getting the credits used much lower for now (until we get more credits/solve it differently).
I've already decreased the number of jobs needed and time needed to run for our tests even for Github Public runners and they should be much snappier than a couple of months ago. I would love to keep the burn rate quite a bit lower than it is now, so I have a proposal: I think it would be great if we move some of the builds (most of the PRs) back to the public runners and leave the Self--hosted only for "priority' builds. Current situation: Self-hosted 'fast' runners are used for: * all master PR builds (merges to master) * all "build-image" workflow * all committer's PR CI builds But I think that not every build by the committer needs to finish really quickly. I think it is mostly ok to wait even a couple of hours sometimes. I propose to change it to use it for: * all master PR builds * all committer's PR CI builds that will have a "priority-build' label set It would be up to the committer, to decide if the label should be set when the PR is created. It will set it then on a "fast-track", That could be useful for quick bug-fixes, release-related commits and the like. WDYT ? Especially committers ? BTW. I also think there is another - very promising approach which I wrote about in the previous mail - https://github.com/apache/spark/pull/32092 which can make everyone (including committer) to utilize their own fork's public runners which will make it even better - but this needs a bit more time to implement I am afraid. J. -- +48 660 796 129
