Auto DevOps runs pipelines automatically only if a Dockerfile or matching buildpack exists. You can enable or disable Auto DevOps for a project or an entire group.

If you only require a subset of the features offered by Auto DevOps, you can include individual Auto DevOps jobs in your own .gitlab-ci.yml. Be sure to also define the stage required by each …

Before enabling Auto DevOps, you should prepare it for deployment. If you don’t, you can use it to build and test your apps, and then configure the deployment later.

You can use CI/CD variables to automatically scale your pod replicas, and to apply custom arguments to the Auto DevOps helm upgrade commands. This is an easy way to customize …

This tutorial gets you started with Auto DevOps using an example of how to deploy an application to Amazon Elastic Kubernetes Service (EKS). The tutorial uses the GitLab native Kubernetes …

If you enable Auto DevOps without setting the base domain and deployment strategy, GitLab can’t deploy your application directly. Therefore, you should prepare the strategies before enabling …

Auto DevOps development guidelines This document provides a development guide for contributors to Auto DevOps. An Auto DevOps technical walk-through is also available on …

Auto DevOps typically uses continuous deployment, and pushes automatically to the production environment whenever a new pipeline runs on the default branch. To deploy to production …

You can use this output to diagnose Auto DevOps deployment problems. You can resolve some problems with Auto DevOps deployment by changing advanced Auto DevOps configuration …

Continuous Integration and Deployment: Configure settings for Auto DevOps, jobs, artifacts, instance runners, and pipeline features. Package registry: Configure package forwarding and …