Commit 2972352a authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'docs-clarify-auto-devops-pipelines' into 'master'

Clarify Auto DevOps pipelines

See merge request gitlab-org/gitlab-ce!16106
parents fe9bcd48 85403771
...@@ -122,11 +122,13 @@ Google Cloud. ...@@ -122,11 +122,13 @@ Google Cloud.
## Enabling Auto DevOps ## Enabling Auto DevOps
**Note:**
If you haven't done already, read the [prerequisites](#prerequisites) to make If you haven't done already, read the [prerequisites](#prerequisites) to make
full use of Auto DevOps. If this is your fist time, we recommend you follow the full use of Auto DevOps. If this is your fist time, we recommend you follow the
[quick start guide](#quick-start). [quick start guide](#quick-start).
To enable Auto DevOps to your project:
1. Check that your project doesn't have a `.gitlab-ci.yml`, and remove it otherwise
1. Go to your project's **Settings > CI/CD > General pipelines settings** and 1. Go to your project's **Settings > CI/CD > General pipelines settings** and
find the Auto DevOps section find the Auto DevOps section
1. Select "Enable Auto DevOps" 1. Select "Enable Auto DevOps"
...@@ -134,22 +136,13 @@ full use of Auto DevOps. If this is your fist time, we recommend you follow the ...@@ -134,22 +136,13 @@ full use of Auto DevOps. If this is your fist time, we recommend you follow the
that will be used by Kubernetes to deploy your application that will be used by Kubernetes to deploy your application
1. Hit **Save changes** for the changes to take effect 1. Hit **Save changes** for the changes to take effect
![Project AutoDevops settings section](img/auto_devops_settings.png) Once saved, an Auto DevOps pipeline will be triggered on the default branch.
Now that it's enabled, there are a few more steps depending on whether your project
has a `.gitlab-ci.yml` or not:
- **For projects with no `.gitlab-ci.yml` present:**
A pipeline needs to be triggered either by pushing a new commit to the
repository or manually visiting `https://example.gitlab.com/<username>/<project>/pipelines/new`
and creating a new pipeline for your default branch, generally `master`.
- **For projects with a `.gitlab-ci.yml` present:**
All you need to do is remove your existing `.gitlab-ci.yml`, and you can even
do that in a branch to test Auto DevOps before committing to `master`.
NOTE: **Note:** NOTE: **Note:**
Starting with GitLab 10.3, when enabling Auto DevOps, a pipeline is For GitLab versions 10.0 - 10.2, when enabling Auto DevOps, a pipeline needs to be
automatically run on the default branch. manually triggered either by pushing a new commit to the repository or by visiting
`https://example.gitlab.com/<username>/<project>/pipelines/new` and creating
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 enable Auto DevOps instance wide
......
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