CI/CD

Continuous Integration (CI) means every change is built and tested automatically as soon as it is pushed, so problems surface while they are still small. Continuous Deployment (CD) carries a change that passed its tests through to deployment without a manual hand-off.

If this is new to you, this introduction is a good place to start:

Pipelines, jobs and runners

GitLab has CI/CD built in, in the same place as your code. This site uses three terms for it:

Term Meaning
Pipeline The set of jobs that GitLab runs for a change. You declare it in a .gitlab-ci.yml file at the root of your repository
Job One step of a pipeline, such as build, test or package. Each job runs on one runner
Runner The machine that runs a job. On this platform, runners belong to your organization and are chosen by tag. See Runners

Status, logs and job artifacts are visible in GitLab, on the branch and the merge request they belong to.

The GitLab CI/CD documentation is the reference for the syntax.

What the platform adds

Working on a shared platform rather than on individually maintained build servers means:

  • Shared pipelines: common pipeline definitions are reused and improved rather than reimplemented per project.
  • No contention: several contributors build, test and deploy in parallel instead of queueing for one build server.
  • Scalability: the same setup carries one team or many.
  • Expert coaching: Vector engineers work alongside your teams on practice, troubleshooting and pipeline improvements.