GitHub user parshimers added a comment to the discussion: Adopt a UCI-sponsored self-hosted GitHub Actions runner
I maintain an older but analogous system for AsterixDB's build (Jenkins instead of GHA). I will say that it is a bit of a task to manage, and often one that is kind of a chore. Often I think folks really only notice it when it breaks, not when something is done to improve or maintain it. That's just a perennial problem in any infrastructure, however. My views on this might be biased by being tasked with Jenkins which is really a troublesome system; GHA should be less annoying. For benchmarks it makes a lot of sense.. It's also easier to just be able to alter or look at something directly if you manage it. It's come in handy many times, particularly in the earlier days of AsterixDB when there were more odd bugs lurking about that required special setups to pin down. I think a machine of that spec should be sufficient. I actually migrated all of the previous builders for AsterixDB onto a machine of similar spec a few years ago (Threadripper 5975WX with 256GB, using VMs to parallelize) and it has been just fine. Before that it was an assortment of discrete machines (NUCs and others) but this lead to a lot of maintenance overhead, because they weren't uniform and ephemeral (e.g. PXE booted, or something similar). GitHub link: https://github.com/apache/texera/discussions/6973#discussioncomment-17817902 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
