Jarek Potiuk <[email protected]> writes: Hi,
> Hi everyone, > > I hope you're all doing well! I've been looking at how Arrow uses > GitHub Actions. All ASF projects share the same pool of GitHub > runners, so every minute we save also shortens the queue for > everyone else. The good news: Arrow's CI is already in good shape > (path filters, concurrency cancelling, the "CI: Extra" labels, > RunsOn for CUDA). Even so, I found some easy wins, and I'd love to > hear what you think. > > I was a listener at yesterday's board meeting and i understand > that Arrow has some CI "difficulties" and is looking for ways to > deal with and JBO was generally offering his overlook of that > (hence the CC:) but then there was a lot of buzz about the > #project-workflows-optimisations channel of ASF - and I just added > new "workflow-optimization" skill in Magpie that is > producing very good advice, and you can use it to implement changes. > those optimizations quickly. > > Last week we used roughly 110-125k GitHub-hosted runner minutes. > Package Linux alone is about 40% of that. Fedora does offer CI builds for packaging: https://packit.dev/ Probably CentOS and other RPM builds could be moved to that.
