Adopt Tools · New
GitLab CI/CD
Pipelines for deployments and network changes.
GitLab brings code, merge requests, pipelines and a container registry together in one system. With a self-hosted GitLab instance and your own runners, this also works in isolated networks. We use it for infrastructure and network changes: automated checks, approval via merge request and rollout with a log.
Enforced approvals through approval rules require a paid edition. If another CI system is the company standard, we implement the same workflows there.
A good fit if …
- GitLab is already in-house or can be self-hosted
- changes need to be traceable and go through approval
- pipelines must also run without internet access
Not a good fit if …
- another CI system is already the standard
- nobody looks after runners and updates
Related entries
- Adopt 10Ansible Configuration and changes as code.
- Adopt 13Terraform Infrastructure as code for cloud and data centre.
- Trial 07CI/CD in air-gapped environments Pipelines in networks without internet access.
- Hold 21Jenkins Proven CI server; for new initiatives we recommend integrated platforms.
History Adopt (New)
Which tools suit your operations?
In an initial call we review your tool landscape and show where a change pays off and where it does not.