News for hackers. Stuff that matters.

A comment on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds. Parent comment

Re:Show HN: WarpBuild – x86-64 and arm GitHub Action runners... by clintonb on Friday December 08, 2023 @12:22PM (#38571518)
I migrated from BuildJet this week because BuildJet’s caching is broken. Installing cached pnpm dependencies takes about 12s on GitHub and WarpBuild runners. It takes 2m on BuildJet, which is about half the runtime, effectively negating the cost savings of BuildJet over GitHub.

I reported this issue to BuildJet over a week ago and haven’t received any response.

[ Parent | on HN ]
Re:Show HN: WarpBuild – x86-64 and arm GitHub Action runners... by suryao on Friday December 08, 2023 @02:21PM (#38573000)
Thanks for your trust! I'm here to ensure you have a good experience with WarpBuild and for feedback/requests.
[ Parent | on HN ]
Re:Show HN: WarpBuild – x86-64 and arm GitHub Action runners... by jeanregisser on Saturday December 09, 2023 @02:46AM (#38579652)
I’m currently evaluating Buildjet. I’m curious about this caching issue. Were you using actions/cache or buildjet/cache?

https://buildjet.com/for-github-actions/docs/guides/migratin...

[ Parent | on HN ]
Re:Show HN: WarpBuild – x86-64 and arm GitHub Action runners... by suryao on Saturday December 09, 2023 @05:46AM (#38580687)
You can continue to use actions/cache if using WarpBuild :)
[ Parent | on HN ]
Re:Show HN: WarpBuild – x86-64 and arm GitHub Action runners... by clintonb on Saturday December 09, 2023 @11:25AM (#38583180)
We used BuildJet cache for months. It’s possible it was always broken and I only noticed a few days ago. I tried both and neither actually cached data. I even tried forking, and upgrading, the BuildJet variant to no avail.

I spent a solid couple hours trying to fix this before moving to WarpBuild.

[ Parent | on HN ]
Re:Show HN: WarpBuild – x86-64 and arm GitHub Action runners... by crohr on Saturday December 09, 2023 @04:53PM (#38586449)
Exactly my experience as well: https://x.com/crohr/status/1732442731715113374

In the tests with my GitHub Action [1] that spawns ephemeral runners for any workflow, I found BuildJet bandwidth speed 10 to 20 times slower than machines at AWS.

[1]: https://github.com/runs-on/action

[ Parent | on HN ]