Pipeline Authoring runbooks

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

This issue is for our part of the https://gitlab.com/gitlab-org/gitlab/-/issues/552411+. See the description there for motivation and context, as well as a definition of runbook vs. playbook and an example.

Pipeline Authoring features:

Pipeline Composition

• Comprehensive pipeline graphs
• Automatic Retry for Failed CI Jobs
• Include external files in CI/CD pipeline definition
• Run jobs only when there are changes to a file or path
• More efficient job execution flow
• Run pipelines for merge requests
• Explicit support for monorepos
• Community powered workflows (configuration is code so are shareable)
• Pipeline defined in one file kept in the repository
• Auto suggest pipelines to start with based on code language
• Advanced CI/CD configuration linter
• Comes with many pre-defined pipelines
• Multiple pipelines per repo
• Reference actions/jobs in another repo
• Define Parent-child pipelines
• Create parallel jobs via a matrix of targets
• CI/CD Catalog
• CI/CD components
• Instance file templates
• Group file templates
• Downstream and Multi-project pipeline graphs
• Define cross-project jobs with artifact dependencies
• Multi project pipeline visualization
• Inputs
• Add anything that's missing!

Variables

• CI/CD variables
• Protected variables
• Nested variable expansion
• Group-level variables
• Add anything that's missing!

---

The feature list and categorization above is taken from the SSOT – some of the feature names and/or links don't make much sense, I know. I had mentioned before that I think this needs to be overhauled. But we can still use it as a starting point.