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.
Our direction for “Auto DevOps” is to leverage our single application to assist users in every phase of the development and delivery process, implementing automatic tasks that can be customized and refined to get the best fit for their needs.
With the dramatic increase in the number of projects being managed by software teams (especially with the rise of micro-services), it's no longer enough to just craft your code. In addition, you must consider all of the other aspects that will make your project successful, such as tests, quality, security, deployment, logging, monitoring, etc. It's no longer acceptable to add these things only when they are needed, or when the project becomes popular, or when there's a problem to address; on the contrary, all of these things should be available at inception.
Watch this video of our CEO Sid explaining the importance of Auto DevOps and follow along with this issue where we are organizing to increase Auto DevOps adoption.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
DevOps Adoption is a known pain point that GitLab, as a complete DevOps platform delivered as a single application, can help alleviate. That adoption isn't just hard technically, it's also a challenge organizationally. The vision for Auto DevOps is to ease that adoption pain. We will serve as a central mechanism for enabling users to continue to further their DevOps adoption journey by automatically implementing best practices, and recommending iterative improvements where appropriate.
There is no current tool in the market that does what Auto DevOps is capable of doing. The best analogy we've found is this - consider that you are trying to navigate from New York to California by car in the year 1992. To get there it would be painful, even with a map because it is a multi-variate problem - one that requires lots of inputs and more than just instruction manuals and best practices. Now imagine you are doing that today with Google Maps on your phone! Google Maps removes all of the pain of those best practices, employs data to intelligently move beyond them and recommends pit stops if you ask.
Auto DevOps will be something similar for DevOps practices. Today it can provide encoded best practices. In the future, Auto DevOps will become the navigation assistant for your DevOps journey - a guide for the journey of continuous improvement.
This vision offers enormous benefit to users confronted with the pain of adopting DevOps, and it serves our business. As our business is built around the whole DevOps cycle, if we can present DevOps practices in a unified and automated way to our users, we believe that they are open to adopt all our stages.
The target persona for Auto DevOps is the platform engineer who wants to simplify, possibly automate the ops-work that falls on software developers. The pipeline authoring category deals with the question on simplifying DevOps practices for single engineers.
Platform engineers require a platform. They either have to build it themselves or can use GitLab for it. These platforms have to support complex processes for CI, security, compliance and deployments alike.
We learned that the current Auto DevOps offering has many shortcomings:
We are discussing two initiatives actively that would require sizeable investment from GitLab and could push this category forward:
At the same time, this discussion had a big effect on the deployment direction of GitLab. Thus we are building out the foundations in order to deliver on this vision.
Auto Devops ties together several feature from across GitLab product categories. Each individual feature will have its own maturity classification.
|Feature||Responsible GitLab Group|
|Auto Code Quality||Testing|
|Auto SAST||Static Analysis|
|Auto Secret Detection||Static Analysis|
|Auto Dependency Scanning||Composition|
|Auto License Compliance||Composition|
|Auto Container Scanning||Container Security|
|Auto Review Apps||Progressive Delivery|
|Auto DAST||Dynamic Analysis|
|Auto Browser Performance Testing||Testing|
|Auto Load Performance testing||Testing|
|Auto Deploy||Progressive Delivery|
While there are "piece-meal" solutions that offer to automate a particular stage, there are no comprehensive tools that offer to address the entire devops lifecycle.
DeployHQ offers to "Automatically build and deploy code from your repositories", however, its UX is complex that its deployment targets limited.
Keptn provides a simplified setup for Kubernetes deployments, but requires other pipelines for non-delivery related tasks.
Crossplane provide a control plane for infrastructure operations, but does not address the overall pipeline question.
Backstage.io provide an umbrella app for other applications. Thus platform engineers can put together full pipelines and project templates that are easily re-used by software engineers.
Humanites provides a SaaS for internal development platforms.
There is currently no analyst category that aligns with Auto DevOps.