Introduction
CI+CD Tools Components Catalog for GitLab
The CI+CD Tools Components Catalog for GitLab brings components to enterprises to build flexible pipelines for continuous delivery to GitLab. Those pipelines can be used for applications and infrastructure. This model be applicable to teams of developers and operators that ship together.
Design principles
The catalog was designed under the following principles:
- Prioritize continuous delivery over continuous deployment. Read
- Infrastructure is delivered with continuous delivery the same way as applications.
- Every web application is running on Kubernetes which should be the current choice for enterprises.
- Every web application's software lifecycle management is handled by GitLab.
- Web applications in a container shall use technology abstraction like S2I from Red Hat as a stable base.
- Containers shipped via HELM packages to Kubernetes.
- The underlying automation stack is compatible to other automation platforms such as GitHub, Azure DevOps, … .
- Support and consult any enterprises following this pattern.
- Stay opinionated and open for feedback.
Documentation
Start here and follow the path that matches your task:
- New to CI Tools? Run the first YAML check. Add builds, releases, and deployments only when you need them.
- Choosing components? Use the task-based component overview to find what is available and open each component's inputs and examples.
- Using self-managed GitLab? Follow catalog setup before copying pipeline examples.
- Configuring access? Read GitLab tokens and registry authentication for the jobs you add.
- Controlling when jobs run? Read pipeline rules.
- Need help? Use the support guide.
Example application pipeline
CI Tools pipeline
