kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

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

Browse source 
Clarify Auto DevOps pipelines

See merge request gitlab-org/gitlab-ce!16106
This commit is contained in:
Achilleas Pipinellis 2017-12-22 11:31:04 +00:00
commit 2972352a9c
2 changed files with 8 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
doc/topics/autodevops/img/auto_devops_settings.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 93 KiB

23
doc/topics/autodevops/index.md
View file

@ -122,11 +122,13 @@ Google Cloud.
## Enabling Auto DevOps
**Note:**
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).
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
find the Auto DevOps section
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
that will be used by Kubernetes to deploy your application
1. Hit **Save changes** for the changes to take effect
![Project AutoDevops settings section](img/auto_devops_settings.png)
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.
For GitLab versions 10.0 - 10.2, 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