GitLab (beta)
- Getting started
- One-line setup (size labels)
- Which jobs can move
- Fallback & rollback
- Build cache (Nx / Turborepo)
- OIDC with AWS
- OIDC with Google Cloud
- Get started with your box
- GitLab (beta)
- Connect Claude (MCP)
- Billing
- Usage analytics & your data
- Data processors for Code review and Insights
- Help
Run your GitLab CI jobs on compiler.dev machines by adding a tag to the job. It works for projects and groups on gitlab.com. Self-managed GitLab: ask us at contact@compiler.dev. This is a closed beta: the GitLab (beta) page appears in the CI part of the app's menu once we switch it on for your organization.
1. Connect. Open GitLab (beta) in the app and press Connect GitLab. You sign in on GitLab and approve. compiler.dev asks for the api scope (GitLab has no narrower scope that can create runners and webhooks) and read_user. The token is stored encrypted and never shown again. To switch something on you need the Owner role on a group or the Maintainer role on a project.
2. Switch on a group or project. The page lists the groups you own and the projects you maintain, each with a switch. Switching one on creates four runners in GitLab, one per size, and adds a Job events webhook (on every project of a group, because group webhooks need a paid GitLab tier). Switching it off deletes them again, and so does Disconnect for everything. Nothing else in your GitLab is touched.
3. Add a tag to the job. In .gitlab-ci.yml:
test:
tags: [compiler-8cpu]
script:
- npm test
- Sizes:
compiler-2cpu(2 vCPU, 4 GB, $0.002 per minute),compiler-4cpu(4 vCPU, 16 GB, $0.004),compiler-8cpu(8 vCPU, 16 GB, $0.008) andcompiler-16cpu(16 vCPU, 32 GB, $0.016). These are the same machines and prices as the size labels on GitHub Actions; the page shows the price for your organization. Jobs without one of these tags are never touched. - One fresh machine per job. Each job runs on a new machine that is deleted when the job ends. It runs the job with GitLab Runner's Docker executor, using the
image:from your file (Ubuntu 24.04 when there is none); Docker-in-Docker works. The machine downloads a pinned, checksum-verified GitLab Runner when it starts. - No warm caches. Every job starts on a cold machine, so the first seconds go on starting it and pulling your image. Use GitLab's own
cache:and artifacts as you do today. - Billing. Per started minute, at least one, from the moment the runner receives the job until it finishes, the same way as GitHub jobs. Starting the machine is not billed. Usage comes out of your prepaid credit or free trial. A job that never started costs nothing.
- If your credit or trial has run out, jobs with a compiler tag wait; they do not move to GitLab's shared runners. The page says why, and they start by themselves, within a couple of minutes, once you add credit.
- How a job is noticed. GitLab calls our webhook when a job becomes pending, and we also look for pending jobs every two minutes, so a missed webhook, or a project created after you switched on its group, only delays the start.
- Where it runs. On single-use cloud machines. Linux only; no macOS, Windows or GPU runners. gitlab.com only for now.