Our Blog

Welcome to the BuildJet for GitHub Actions Blog. We're building a faster and cheaper way to run your Github Actions builds. You can read about our journey and what we've learnt along the way on this blog.

11/9/2020

· Adam from BuildJet

What hardware powers GitHub Actions?

It is common practice for CI's to simply state the amount of vCPUs at the user's disposal. We do the same and find it generally to be a good abstraction. Cross-service comparison gets easier and the users don't need to dabble with the details.

10/23/2020

· Adam from BuildJet

A Performance Review of GitHub Actions - the cost of slow hardware

In this performance review, we will take a close look at the cost of slow hardware. Firstly, we will compare CI runs with different codebases, on different hardware. We will then explain the different CI runs, by drilling into characteristics of the respective codebase, programming language, and the available CI hardware.

10/11/2020

· Adam from BuildJet

Why we want to fix GitHub Actions

As most developers know, regardless of how much you try to multitask, waiting for the CI to finish always feels like an unnecessary bottleneck. As a consequence of project complexity and developers waiting for simple PR's, we always ended up migrating to a self-hosted CI despite it always being extra effort to set it up and maintain.

Make Github Actions FasterManaged high-performance runners for Github Actions

Get StartedFree trial minutes · No CC required