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
a748eaf0
Commit
a748eaf0
authored
4 years ago
by
Simon Mansfield
Committed by
Amy Qualls
4 years ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update Auto DevOps STAGING and CANARY documentation for clarity
parent
8cdba719
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
4 deletions
+2
-4
doc/topics/autodevops/customize.md
doc/topics/autodevops/customize.md
+2
-4
No files found.
doc/topics/autodevops/customize.md
View file @
a748eaf0
...
...
@@ -520,8 +520,7 @@ on the default branch. However, there are cases where you might want to use a
staging environment, and deploy to production manually. For this scenario, the
`STAGING_ENABLED`
environment variable was introduced.
If you define
`STAGING_ENABLED`
, such as setting
`STAGING_ENABLED`
to
`1`
as a CI/CD variable, then GitLab automatically deploys the application
If you define
`STAGING_ENABLED`
with a non-empty value, then GitLab automatically deploys the application
to a
`staging`
environment, and creates a
`production_manual`
job for
you when you're ready to manually deploy to production.
...
...
@@ -532,8 +531,7 @@ you when you're ready to manually deploy to production.
You can use a
[
canary environment
](
../../user/project/canary_deployments.md
)
before
deploying any changes to production.
If you define
`CANARY_ENABLED`
in your project, such as setting
`CANARY_ENABLED`
to
`1`
as a CI/CD variable, then two manual jobs are created:
If you define
`CANARY_ENABLED`
with a non-empty value, then two manual jobs are created:
-
`canary`
- Deploys the application to the canary environment.
-
`production_manual`
- Manually deploys the application to production.
...
...
This diff is collapsed.
Click to expand it.
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