Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
2972352a
Commit
2972352a
authored
Dec 22, 2017
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'docs-clarify-auto-devops-pipelines' into 'master'
Clarify Auto DevOps pipelines See merge request gitlab-org/gitlab-ce!16106
parents
fe9bcd48
85403771
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
8 additions
and
15 deletions
+8
-15
doc/topics/autodevops/img/auto_devops_settings.png
doc/topics/autodevops/img/auto_devops_settings.png
+0
-0
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+8
-15
No files found.
doc/topics/autodevops/img/auto_devops_settings.png
deleted
100644 → 0
View file @
fe9bcd48
93 KB
doc/topics/autodevops/index.md
View file @
2972352a
...
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment