diff options
| author | Fabio Busatto <fabio@gitlab.com> | 2017-12-22 08:30:34 +0000 |
|---|---|---|
| committer | Fabio Busatto <fabio@gitlab.com> | 2017-12-22 08:30:34 +0000 |
| commit | 16f4585076af696a1a1d915e1c8e7576b49813cb (patch) | |
| tree | b186bbf525699f1723a6c41d92fc4d75a4896014 | |
| parent | 36f4710301926bb853b35d9b14a60e03b42def34 (diff) | |
| download | gitlab-ce-docs-clarify-auto-devops-pipelines.tar.gz | |
Clarify Auto DevOps pipelinesdocs-clarify-auto-devops-pipelines
| -rw-r--r-- | doc/topics/autodevops/index.md | 22 |
1 files changed, 8 insertions, 14 deletions
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md index 0b48596006d..b4d2910d862 100644 --- a/doc/topics/autodevops/index.md +++ b/doc/topics/autodevops/index.md @@ -127,6 +127,7 @@ 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 [quick start guide](#quick-start). +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 find the Auto DevOps section 1. Select "Enable Auto DevOps" @@ -134,22 +135,15 @@ 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 1. Hit **Save changes** for the changes to take effect - - -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`. +Once saved, an Auto DevOps pipeline will be triggered on the default branch. NOTE: **Note:** -Starting with GitLab 10.3, when enabling Auto DevOps, a pipeline is -automatically run on the default branch. +Before with GitLab 10.3, when enabling Auto DevOps, a pipeline needs to be +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:** If you are a GitLab Administrator, you can enable Auto DevOps instance wide |