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
82f3fa14
Commit
82f3fa14
authored
Oct 16, 2019
by
Evan Read
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'patch-34' into 'master'
Update index.md See merge request gitlab-org/gitlab!18623
parents
bb7c2882
60196f55
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+3
-3
No files found.
doc/topics/autodevops/index.md
View file @
82f3fa14
...
...
@@ -98,7 +98,7 @@ To make full use of Auto DevOps, you will need:
-
**GitLab Runner**
(for all stages)
Your Runner needs to be configured to be able to run Docker. Generally this
means using
the
either the
[
Docker
](
https://docs.gitlab.com/runner/executors/docker.html
)
means using either the
[
Docker
](
https://docs.gitlab.com/runner/executors/docker.html
)
or
[
Kubernetes
](
https://docs.gitlab.com/runner/executors/kubernetes.html
)
executors, with
[
privileged mode enabled
](
https://docs.gitlab.com/runner/executors/docker.html#use-docker-in-docker-with-privileged-mode
)
.
...
...
@@ -1169,13 +1169,13 @@ This configuration is deprecated and will be removed in the future.
TIP:
**Tip:**
You can also set this inside your
[
project's settings
](
#deployment-strategy
)
.
This configuration based on
This configuration
is
based on
[
incremental rollout to production
](
#incremental-rollout-to-production-premium
)
.
Everything behaves the same way, except:
-
It's enabled by setting the
`INCREMENTAL_ROLLOUT_MODE`
variable to
`timed`
.
-
Instead of the standard
`production`
job, the following jobs
with a 5 minute delay between each are created
:
-
Instead of the standard
`production`
job, the following jobs
are created with a 5 minute delay between each
:
1.
`timed rollout 10%`
1.
`timed rollout 25%`
1.
`timed rollout 50%`
...
...
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