Summary

Now that you have a good grasp of the purpose and structure of GitLab CI/CD pipelines, let’s review the concepts we covered in this chapter.

Pipelines are a series of steps that are performed against code in your project’s Git repository. Each project has just one pipeline, although the various steps that make up a project’s pipeline can be run or suppressed, depending on which Git branch or Git tag the pipeline is running against. The term “pipeline” is sometimes used to mean the overall set of tasks that will be run on a project’s code, while other times, it’s used to mean a single instance or run of that pipeline against a particular version of the repository’s files.

The CI, or continuous integration, portion of a pipeline answers the question, is the code good? It typically consists of some combination of automated tests, security scans, license compliance checks, and code quality checks. The CI steps of a pipeline...