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
d102b50c
Commit
d102b50c
authored
Sep 18, 2020
by
Jason Goodman
Committed by
Marcel Amirault
Sep 18, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document That Deploy Boards Assumes Stable Track When None is Present
parent
e659365a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/user/project/canary_deployments.md
doc/user/project/canary_deployments.md
+3
-3
No files found.
doc/user/project/canary_deployments.md
View file @
d102b50c
...
@@ -48,9 +48,9 @@ Canary deployments require that you properly configure Deploy Boards:
...
@@ -48,9 +48,9 @@ Canary deployments require that you properly configure Deploy Boards:
template for canary deployments that GitLab provides.
template for canary deployments that GitLab provides.
Depending on the deploy, the label should be either
`stable`
or
`canary`
.
Depending on the deploy, the label should be either
`stable`
or
`canary`
.
Usually,
`stable`
and blank or missing label means the same thing, and
`canary`
GitLab assumes the track label is
`stable`
if the label is blank or missing.
or any other track means canary/temporary
.
Any other track label is considered
`canary`
(temporary)
.
This allows GitLab to discover whether deployment is stable or canary (temporary).
This allows GitLab to discover whether
a
deployment is stable or canary (temporary).
Once all of the above are set up and the pipeline has run at least once,
Once all of the above are set up and the pipeline has run at least once,
navigate to the environments page under
**Pipelines > Environments**
.
navigate to the environments page under
**Pipelines > Environments**
.
...
...
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