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
e15016ed
Commit
e15016ed
authored
Sep 14, 2018
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move the Auto DevOps note to the top
parent
df0b8b94
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
10 deletions
+12
-10
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+12
-10
No files found.
doc/topics/autodevops/index.md
View file @
e15016ed
...
...
@@ -7,6 +7,14 @@ applications.
## Overview
NOTE:
**Enabled by default:**
Starting with GitLab 11.3, the Auto DevOps pipeline will be enabled by default for all
projects. If it's not explicitly enabled for the project, Auto DevOps will be automatically
disabled on the first pipeline failure. Your project will continue to use an alternative
[
CI/CD configuration file
](
../../ci/yaml/README.md
)
if one is found. A GitLab
administrator can
[
change this setting
](
../../user/admin_area/settings/continuous_integration.html#auto-devops
)
in the admin area.
With Auto DevOps, the software development process becomes easier to set up
as every project can have a complete workflow from verification to monitoring
without needing to configure anything. Just push your code and GitLab takes
...
...
@@ -214,22 +222,16 @@ manually triggered either by pushing a new commit to the repository or by visiti
a new pipeline for your default branch, generally
`master`
.
NOTE:
**Note:**
If you are a GitLab Administrator, you can
enable Auto DevOps instance wide
in
**Admin Area > Settings > Continuous Integration and Deployment**
. Doing that
,
a
ll the
projects that haven't explicitly set an option will have Auto DevOps
enabled by default.
If you are a GitLab Administrator, you can
[
enable/disable Auto DevOps instance-wide
](
../../user/admin_area/settings/continuous_integration.md#auto-devops
)
,
a
nd all
projects that haven't explicitly set an option will have Auto DevOps
enabled
/disabled
by default.
NOTE:
**Note:**
There is also a feature flag to enable Auto DevOps to a percentage of projects
which can be enabled from the console with
`Feature.get(:force_autodevops_on_by_default).enable_percentage_of_actors(10)`
.
NOTE:
**Enabled by default:**
Starting with GitLab 11.3, the Auto DevOps pipeline will be enabled by default for all
projects. If it's not explicitly enabled for the project, Auto DevOps will be automatically
disabled on the first pipeline failure. Your project will continue to use an alternative
[
CI/CD configuration file
](
../../ci/yaml/README.md
)
if one is found.
### Deployment strategy
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/38542) in GitLab 11.0.
...
...
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