Mawreen Dela Cruz - Release Management Onboarding
On-Boarding
Trainee: @madelacruz
Release Manager: TBD
. See https://about.gitlab.com/release-managers/ for details
-
Trainee: Assign yourself and the Release Manager to this issue. -
Trainee: Set up a sync or have an async chat with the Release Manager you are shadowing to go over any initial questions and your learning style and align on your expectations for your shadowing experience.
Usernames
Trainee: Make a note of your GitLab.com
and dev.gitlab.org
usernames and add them to this issue.
Instance | Username |
---|---|
gitlab.com | madelacruz |
dev.gitlab.org | madelacruz |
ops.gitlab.net | madelacruz |
release.gitlab.net | madelacruz |
Access request
-
Trainee: Add your information to the config/release_managers.yml
file in release-tools and open a merge request, linking to this issue. -
Trainee: Open a merge request, linking to this issue, that adds your information to the data/release.yml
file undermanager_apac_emea
ormanager_americas
for the appropriate version when you plan to shadow the Release Manager, example MR. -
Trainee: Reflect Rotation on PagerDuty Schedule:-
Reflect Rotation on PagerDuty Schedule in Terraform: config-mgmt/environments/pagerduty-
Once merged and applied, verify it is present in PD: release-managers
-
-
-
Trainee: make sure you can log in to ops.gitlab.net
. After log in, please change your username to be the same as it is on gitlab.com -
Trainee: make sure you can log in to release.gitlab.net
. After log in, please change your username to be the same as it is on gitlab.com -
Trainer: Add user as a Maintainer
in the delivery group
Tool setup
Trainee: Ensure you have completed all the steps on Access Request
before doing this section.
-
Trainee: Make sure you have release-tools cloned locally, and set it up -
Trainee: Make sure you have chatops access by running /chatops run auto_deploy status
in#chat-ops-test
Slack channel. If not, ask somebody who does to run the following command in Slack:/chatops run member add USER gitlab-com/chatops --ops
, replacing USER with your username on ops.gitlab.net.
First Tasks
-
Trainee: Join the following Slack Channels: - #announcements - Shows deployments moving through the various environments.
- #f_upcoming_release - Channel used by release managers to perform daily activities.
- #g_delivery - Delivery group channel. A good place to ask any questions.
- #incident-management - Any declared incidents will display in this channel. You will find links to the associated incident slack channel and issue.
- #production - Contains a lot of production discussions, but also a place to see all feature flags being toggled on production.
- #releases - Contains messages about monthly releases, patch releases, stable branch failures, and merge train.
-
Trainee: Read through the release guides -
Trainee: Read through the deployment and releases documentation -
Trainee: Read through the release documentation -
Trainee: Read through the deployment documentation -
Trainee: Read the deploy docs
Dashboards and issues to familiarize with and watch
These are reviewed weekly during the Delivery group weekly meeting.
-
Auto-deploy packages dashboard -
Deployment frequency and lead time -
Familiarize with the deployment blockers epic -
Release management dashboard
Tasks to shadow
Not every task will happen during your shadowing shift (for example a critical patch release). This is a non-exhaustive list of some major tasks to shadow when they occur.
-
Patch release -
Rollback practice -
Promoting a package -
Patch release -
Monthly release -
Deployment blocking incident -
Pick into autodeploy / manually push an MR through to production -
Declaring an incident -
Opening a release/tasks issue for a failure -
Execute the PDM pipeline -
Critical patch release (if happening)
Edited by Mawreen Dela Cruz