Skip to content
Getting Started

Getting Started

Welcome! Follow the steps below to use the BuildJet for GitHub Actions runners.

Install BuildJet

Install BuildJet onto your repository here. It's an GitHub OAuth application allows us to listen to your GitHub Actions runs and give you access to the BuildJet hardware.

If you don't have admin rights in the repository, please contact your repository owner and ask them to install BuildJet for GitHub Actions. Simply send them the link above.

Add BuildJet to your workflow.yml

In order for BuildJet for GitHub Actions to be used by your workflow job, you need to specify a runner tag in the jobs.[job-name].runs-on property.

We recommend starting with the 4 vCPU runner, as this has the same cost as the GitHub runner and is a good baseline for comparison. For a complete list of runners, click here.

name: Test Suite
on: push
    runs-on: buildjet-4vcpu-ubuntu-2204
    name: Test
      - uses: actions/[email protected]

Next steps

Congratulations! That is all you need to do to get up and running with BuildJet for GitHub Actions. Now you can try to out different BuildJet hardware configurations and see how much they improve the job.

Some jobs don't need an 32vCPU machine, but a 4vCPU would be enough. You should play around and see what works best for your setup. Read more about how pick to right runner.

Please keep in mind that every account starts with only being able to run 64 AMD64 vCPU's at the same time/concurrently. If you would like to increase the number of concurrent runs you can make, please contact our customer support team at [email protected].