StageFreight GitLab Integration

CI Pipeline

CI files are generated by StageFreight, not hand-maintained.

stagefreight ci render gitlab --write
git add .gitlab-ci.yml
git commit

Audition enforces freshness — stale CI files fail the pipeline.

Runner Infrastructure

Self-hosted GitLab Runner deployments live under docker/:

• runner/docker/docker-compose-gitlab_runner-minimal.yml — minimal reference: GitLab Runner with persistent DinD and StageFreight cache.
• runner/docker/docker-compose-gitlab_runner-minimal.yml — runner + DinD.
• runner/docker/docker-compose-gitlab_runner-buildkitd.yml — runner + persistent buildkitd (mTLS) + DinD, for fast builds. The Azure equivalent is ../azuredevops/k8s/.

How it works

All jobs call stagefreight ci run <phase>. StageFreight reads .stagefreight.yml and decides what each phase does at runtime. The generated CI file is transport — StageFreight owns all logic.