Refactor.io VS BuildJet for GitHub Actions

Refactor.io mentions (0)

BuildJet for GitHub Actions mentions (5)

• Experiment: The costs of slow build times

  Disclaimer: Co-founder of https://buildjet.com/for-github-actions While more cores can certainly help with certain types of projects, such as those that can be easily parallelized, this is not always the case. For example, web app projects won't benefit as much from additional cores. Another important factor to consider is the single-core performance of each vCPU. Many server-class CPUs, such as those used by... - Source: Hacker News / over 1 year ago

• Blazing fast CI with MicroVMs

  Congratulations on the launch. It looks pretty much like a self-hosted version of https://buildjet.com/for-github-actions. - Source: Hacker News / over 1 year ago

• CircleCI Announces Support for Gitlab

  I'm a bit biased as one of the founders of BuildJet, but we solve this exact issue. BuildJet for GitHub Actions, plugs elegantly into GitHub Actions. With 1-line change in your config, you get 2x speed for half of GitHub's price. Check it out @ https://buildjet.com/for-github-actions. - Source: Hacker News / over 1 year ago

• We use GitHub Actions to build GitHub

  With BuildJet for GitHub Actions, you can get up to 64 vCPU as a GitHub Actions runner. We plug right into your existing setup and have a significantly higher per core performance compared to the native runner. Check us out here: https://buildjet.com/for-github-actions. - Source: Hacker News / about 2 years ago

• GitHub Actions by Example

  Incoming shameless plug; if you don’t have to handle the hosting runners, but still to reap the benefits of having proper hardware (close to the metal). Check out BuildJet for GitHub actions[1] - 2x the speed for half the price. Easy to install and easy to revert. [1] https://buildjet.com/for-github-actions. - Source: Hacker News / about 2 years ago