Oh neat, I came across BuildJet the other day. I was trying to cross-compile a side project ( https://github.com/marcus-crane/october ) for Linux arm64 but trying to do so would throw up some instruction set errors. I had parted the idea of supporting Linux arm since Github has no runners but I threw in BuildJet and it spat out a working build with no problems! Given it only needs to run on release, for a small open…
Check us out! We put some effort into the onboarding to make it super easy to use WarpBuild runners.
Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
61–70 of 89 posts
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#62Hi, quick question: > Runners are assigned to hardware that is ideal for build workloads with [...] high single-core performance In my kind of projects (C++, Rust, C) the builds are highly parallelizable, so single core performance is generally not what you want, if you can instead get a lot of cores. The main bottleneck to my own build pipelines on github was how painful it is to use containers, and how "helpful to…
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#63Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#64I'm not officially affiliated with them at all. But I'm a big fan of their product.
It appears that one difference though is that Depot is more focused on just docker builds and y'all are more generalized runners Is that right?
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#65Congrats on the launch! There do seem to be a number of other entrants in this space: https://github.com/neysofu/awesome-github-actions-runners#li... What makes you stand out from the pack? The VM approach seems very cool - is this unique in the space? Do you have different approaches that provide speedups or security benefits not possible with other third party runner systems? Any benchmarks against competitors? Sep…
We are essentially competing in the same space with https://dime.run/ We also use VMs. But they are persistent. So you always see your runners as Online in GitHub UI. We achieve this by investing in virtualization technology so that idle runner VMs do not consume too many resources. Disclaimer: I used to work for Google Cloud.
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#66Earlier quoted context omitted.
Awesome. Do docker image layers persist across build runs? Github, BuildJet, etc. use ephemeral runners, so subsequent runs have to re-pull everything from scratch, which is where most of my actions' time is spent now. If you're able to persist these across runs, that'd be a reason to switch alone.
Not yet, but coming soon (~2 weeks)
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#67Earlier quoted context omitted.
Not yet, but coming soon (~2 weeks)
This will, by itself, immediately sell me. I’ve spent countless hours and lots of deep deep reading trying to get satisfactory results on GitHub Actions, with no success. From what I’ve seen, plenty of other people are in the same boat.
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#68Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#69It seems half-baked to me. I logged in, and it says only org accounts are supported. I'm interesting because I can not use Win32 and mac M1 instance on github actions, but I failed to find any docs mentioning supported instance types.
The docs are wip - it'll be updated in the next couple of days.
Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
#70Can I expect complex caching actions like https://github.com/DeterminateSystems/magic-nix-cache to work as quickly as they do on GitHub?