Commit a01a1340 authored by Marcia Ramos's avatar Marcia Ramos

Merge branch 'docs/autodevops-enable-auto' into 'master'

Move the Auto DevOps note to the top

See merge request gitlab-org/gitlab-ce!21745
parents 687fa664 e15016ed
...@@ -7,6 +7,14 @@ applications. ...@@ -7,6 +7,14 @@ applications.
## Overview ## Overview
NOTE: **Enabled by default:**
Starting with GitLab 11.3, the Auto DevOps pipeline will be enabled by default for all
projects. If it's not explicitly enabled for the project, Auto DevOps will be automatically
disabled on the first pipeline failure. Your project will continue to use an alternative
[CI/CD configuration file](../../ci/yaml/README.md) if one is found. A GitLab
administrator can [change this setting](../../user/admin_area/settings/continuous_integration.html#auto-devops)
in the admin area.
With Auto DevOps, the software development process becomes easier to set up With Auto DevOps, the software development process becomes easier to set up
as every project can have a complete workflow from verification to monitoring as every project can have a complete workflow from verification to monitoring
without needing to configure anything. Just push your code and GitLab takes without needing to configure anything. Just push your code and GitLab takes
...@@ -214,22 +222,16 @@ manually triggered either by pushing a new commit to the repository or by visiti ...@@ -214,22 +222,16 @@ manually triggered either by pushing a new commit to the repository or by visiti
a new pipeline for your default branch, generally `master`. a new pipeline for your default branch, generally `master`.
NOTE: **Note:** NOTE: **Note:**
If you are a GitLab Administrator, you can enable Auto DevOps instance wide If you are a GitLab Administrator, you can
in **Admin Area > Settings > Continuous Integration and Deployment**. Doing that, [enable/disable Auto DevOps instance-wide](../../user/admin_area/settings/continuous_integration.md#auto-devops),
all the projects that haven't explicitly set an option will have Auto DevOps and all projects that haven't explicitly set an option will have Auto DevOps
enabled by default. enabled/disabled by default.
NOTE: **Note:** NOTE: **Note:**
There is also a feature flag to enable Auto DevOps to a percentage of projects There is also a feature flag to enable Auto DevOps to a percentage of projects
which can be enabled from the console with which can be enabled from the console with
`Feature.get(:force_autodevops_on_by_default).enable_percentage_of_actors(10)`. `Feature.get(:force_autodevops_on_by_default).enable_percentage_of_actors(10)`.
NOTE: **Enabled by default:**
Starting with GitLab 11.3, the Auto DevOps pipeline will be enabled by default for all
projects. If it's not explicitly enabled for the project, Auto DevOps will be automatically
disabled on the first pipeline failure. Your project will continue to use an alternative
[CI/CD configuration file](../../ci/yaml/README.md) if one is found.
### Deployment strategy ### Deployment strategy
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/38542) in GitLab 11.0. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/38542) in GitLab 11.0.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment