The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Continuous Delivery (CD) enables organizations to have the latest changes to their software ready for production at any time. GitLab's CD capabilities provide the deployment automation, approval workflows, and environment management teams need to deliver software reliably and frequently.
This page focuses specifically on GitLab's traditional CI/CD-based deployment capabilities. For our broader delivery vision including GitOps and modern deployment frameworks, see the main Delivery direction.
Continuous Delivery(CD) tools automate the process of delivering code changes to target environments (development, test, production) reliably and efficiently, typically after passing quality or compliance checks when the target is a production environment.
We follow the well-known definitions from Martin Fowler on the difference between continuous delivery and continuous deployment:
Source: https://martinfowler.com/bliki/ContinuousDelivery.html
Core Features:
What This Enables:
GitLab's Continuous Delivery capabilities serve as the foundation for software deployment across diverse infrastructure types. While we're investing heavily in Kubernetes-first approaches and the GitLab Delivery Framework for modern cloud-native applications, our CD features continue to serve teams with:
The continuous delivery product category is currently in maintenance mode. We do not have any new features on our roadmap. We are still encouraging community contributions, especially around connecting releases and environments, improving resource group management or improving environment access controls here and here.
This category is currently at the "Complete" maturity level, and our next maturity target is Lovable (see our definitions of maturity levels).
Current Focus: Stability and reliability
Why This Focus: As we build the next generation of delivery capabilities, we're ensuring our existing CD features remain stable and secure for the thousands of teams relying on them daily.