Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
G
GitLab Release Docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
release
GitLab Release Docs
Commits
645fd52f
Commit
645fd52f
authored
2 years ago
by
Graeme Gillies
Committed by
Mayra Cabrera
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Add initial draft of runbook to deploy to a specific environment
Part of
gitlab-com/gl-infra/delivery#2143
parent
7f28f385
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
runbooks/deploy-to-a-single-environment.md
+37
-0
37 additions, 0 deletions
runbooks/deploy-to-a-single-environment.md
with
37 additions
and
0 deletions
runbooks/deploy-to-a-single-environment.md
0 → 100644
+
37
−
0
View file @
645fd52f
# Deploying to a single environment
This runbook aims to cover the use cases where our auto-deploy pipelines are
not functioning correctly, or there is a need to deploy to environments out of
order, and thus you need to manually deploy a specific release to an environment.
## Pre-deploy considerations
*
When deploying to a canary environment, make sure canary is unddrained so
that QA tests are accurately using the canary stage
*
Identify the full package version you wish to deploy using XXX
## Deploying to a single environment
*
Use chatops to deploy to a single environment
```
# Staging deploy
/chatops run deploy 14.X.XXX
# Staging canary deploy
/chatops run deploy --canary 14.X.XXX
# Production deploy
/chatops run deploy --production 14.X.XXX
# Production canary deploy
/chatops run deploy --production --canary 14.X.XXX
```
## Post-deploy considerations
*
If you are deploying to
`gstg`
or
`gprd`
, consider the fact that the pipeline
order expects that these environments are kept very close in sync. If you manually
deploy to a single environment, you should highly consider manually deploying
to the other one as well
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment