Code · DevSecOps platform
GitLab
GitLab hosts repositories and runs pipelines defined in .gitlab-ci.yml on shared or self-managed runners. Its SAST, Secret Detection and Dependency Scanning templates bring baseline DevSecOps checks to every project.
On this page
What it does
Git hosting, merge requests with approvals, protected branches, CI/CD with environments and deployments, package and container registries, and security scanning integrated in merge requests.
Where it fits
Code and Build stages; this site’s source lives on GitLab, from which Cloudflare Workers Builds deploys it.
Quick start
include:
- template: Jobs/SAST.gitlab-ci.yml
- template: Jobs/Secret-Detection.gitlab-ci.yml
stages: [test, build, deploy]
Common pitfalls
- Unprotected CI variables are exposed to pipelines from any branch — mark deployment secrets protected and masked.
- Shared runners with Docker-in-Docker need privileged mode; prefer Kaniko or the Kubernetes executor.
latestDocker images in jobs make pipelines non-reproducible; pin versions.
On this site
- Reusable GitLab CI Templates and Components: a platform-owned template with
spec:inputs, consumed by project and tag, extended without editing, and what a consumer can still override.