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.
Thanks for visiting this category page on Environment Management in GitLab. This page belongs to the Release stage, and is maintained by Chris Balane who can be contacted directly via email. This vision is a work in progress and everyone can contribute. Sharing your feedback directly on issues and epics at GitLab.com is the best way to contribute to our vision. If you’re a GitLab user and have direct knowledge of your need for managing your environments and deployments in general, we’d especially love to hear from you.
Enable organizations to operate and manage multiple environments directly from GitLab. Environments are encapsulated in GitLab as a target system with associated configurations. By facilitating access control, visualizing deployments and deployment history across teams and projects, adding the ability to query environments, and ensuring that environment's configurations are traceable, platform engineers can enact stronger controls and avoid costly mistakes in deployments.
Through the use of Environments in GitLab, teams can easily understand and take critical action on the changes of their application. Environments provide the infrastructure needed for teams to test, deliver, and gain confidence software will work properly in production in any configuration and enable them to strive towards continuous deployment of their application.
| Job statements | Maturity | Confidence | Source |
|---|---|---|---|
| When managing my deployment platform, I want to monitor and have historical context about the different deployed versions of code across my application, so I can make effective decisions. |
|
Issue | |
| When I make changes to my applications, I can track the change from the repository, all the way through to the production environment, so that I can confirm that my changes have been deployed. |
|
Issue |
Garden.io allows developers to work against a live Kubernetes cluster that works alongside their CI. Through building and test caching it promises to allow for faster development cycles and better integration test creation.
ReleaseHub lets users launch ephemeral environments on-demand. Use cases they call out are Staging, Automated Preview, Dev, and QA environments.