Product Vision - Release

Release Automation & Orchestration

The Release stage comes after your build has completed in your CI pipeline, and ensures that your software makes it through your review apps, pre-production environments, and ultimately to your users with zero touch needed.

Pipeline Infographic

The stage aligns to two main industry categories: Continuous Delivery and Release Automation and Application Release Automation/Orchestration.

You can also check out this video for a walkthrough of the stage, north stars, and categories that make up Release.

Reach out to PM Jason Lenny (E-Mail / Twitter) if you'd like to provide feedback or ask questions about what's coming.

North Stars

There are a few important ideas we are keeping as northern stars to guide us forward in this space. With each of these, we're focusing on more complete (truly minimally lovable) features. Iterations are how we build software, but at the same time we want to continue to curate those features that have proven their value, allowing them to grow into more complete, lovable features that exceed expectations.

You can see an calendar view of the epics below at this link.

Zero-Touch Delivery

Technologies like Heroku/PAS Buildpacks are leading the way in allowing for developers to focus on building code and letting the automation handle figuring out how to manage the deployment. Our vision is for CD to take over from your build system and predictably manage your delivery for you while remaining completely customizable to support any unique cases.

Related Epics:

On-Demand Environments

Delivering software to your environments automatically is the first step, but new technologies like Kubernetes are now allowing on-demand environments to be created in parallel with code deployments like never before. By enabling this on-demand infrastructure to understand the intentions of developers, you can enable a true one-click "deliver to my users" workflow.

Related Epics:

Secure, Compliant, and Well-Orchestrated Deployments

Releasing in GitLab takes advantage of our deeply connected ecosystem to provide auditability all the way from planning through monitoring changes. Compliance and security evidence is gathered and validated at each step of the way, giving you confidence in what you're delivering in your release. Deployments are run from outside the build pipeline, ensuring a clear boundary between your developers and changes to your environments inside of a well-orchestrated and automated delivery process.

Related Epics:


There are a few categories that are critical for success in this stage; each one is intended to represent what you might find as an entire product out in the market. If you have thoughts or questions on any of these, feel free to jump into the conversation in the vision epic.

Continuous Delivery (CD)

Deliver your changes to production with zero-touch software delivery; focus on building great software and allow GitLab CD to bring your release through your path to production for you.
Learn moreDocumentationVision

Release Orchestration

Management and orchestration of releases-as-code that supports intelligent notifications, scheduling of delivery and shared resources, blackout periods, relationships, parallelization, and sequencing, as well as support for integrating manual processes and interventions.


Use any static site generator to create websites that are easily managed and deployed by GitLab.
Learn moreDocumentationVision

Review apps

Get a full production like environment for every merge request that updates on each commit. See code running and enable user acceptance testing before you merge.
Learn moreDocumentationVision

Incremental Rollout

Mitigate the risk of production deploys by deploying new production code to small subset of your fleet and then incrementally adding more.

Feature Flags

Feature flags enable teams to achieve CD by letting them deploy dark features to production as smaller batches for controlled testing, separating feature delivery from customer launch, and removing risk from delivery.

Release Governance

Release Governance includes features such as deploy-time security controls to ensure only trusted container images are deployed on Kubernetes Engine, and more broadly includes all the assurances and evidence collection that are necessary for you to trust the changes you're delivering.


At GitLab, one of our values is that everyone can contribute. If you're looking to get involved with features in the Release area, there are a couple queries you can use to find issues to work on:

You can read more about our general contribution guidelines here.

What's Next

It's important to call out that the below plan can change any moment and should not be taken as a hard commitment, though we do try to keep things generally stable. In general, we follow the same prioritization guidelines as the product team at large. Issues will tend to flow from having no milestone, to being added to the backlog, to being added to this page and/or a specific milestone for delivery.

Take a look at the video below for a walkthrough of what's coming next.

11.8 (2019-02-22)

11.9 (2019-03-22)

11.10 (2019-04-22)

11.11 (2019-05-22)

12.0 (2019-06-22)

12.1 (2019-07-22)

12.2 (2019-08-22)

12.3 (2019-09-22)

FY20 Q4

Other Interesting Items

There are a number of other issues that we've identified as being interesting that we are potentially thinking about, but do not currently have planned by setting a milestone for delivery. Some are good ideas we want to do, but don't yet know when; some we may never get around to, some may be replaced by another idea, and some are just waiting for that right spark of inspiration to turn them into something special.

Remember that at GitLab, everyone can contribute! This is one of our fundamental values and something we truly believe in, so if you have feedback on any of these items you're more than welcome to jump into the discussion. Our vision and product are truly something we build together!