|
|
|
|
|
by thinkafterbef
1876 days ago
|
|
We had the same kind of problem, where we saw our tests and builds take 20-30 minutes.
We also noticed that our own machine could run the tests significantly faster, mainly due to that desktop CPU can easily boost the clock speed for intense work load. Comparably most CIs use Cloud VMs which hardly go beyond 3 GHz. We found this quite strange. After some talk we decided to build a CI service based on this premise, i.e desktop CPU outform Cloud CPUs for the CI use case. After some months we managed to create BuildJet. I would say it at minimum cuts the the build time in half and the best part is that it plugs right into Github Actions, just need to change one line in your Github Actions configuration. If it sounds useful for you, check it out: https://buildjet.com |
|