Onboarding Release Manager Mark Fletcher
On-Boarding
-
Make a note of your dev
andgithub
usernames and add them to this issue. -
Use the release manager infrastructure permissions template to request chef and SSH access: [https://gitlab.com/gitlab-com/infrastructure/issues/3552] -
Make sure you have takeoff cloned locally, and set it up -
Make sure you have release-tools cloned locally, and set it up -
If your ssh key has a passphrase, you will want to do ssh-add
in your local takeoff repo -
Read through the release guides -
Join #releases on Slack, and introduce yourself -
Master access on gitlab-ce (dev and com) -
Master access on gitlab-ee (dev and com) -
Master access on gitlab-omnibus (dev and com) -
Get added to the Release Managers team on GitHub. -
Make sure you have VPN access (follow instructions from creating client certificate up to and including google authenticator setup), and test by bringing VPN up and sshing into staging sidekiq node ( sidekiq-asap-01.sv.stg.gitlab.com
)
First Tasks
-
Read the deploy docs: https://gitlab.com/gitlab-org/takeoff#deploying-gitlab -
Be involved in the merge/pick to stable for at least one RC/Patch -
Perform the ce-to-ee merge at least once for a RC/Patch -
Tag the release for at least one RC/patch -
Join a staging deploy call -
Join a gitlab.com deploy call -
Deploy to staging at least once -
Deploy to gitlab.com at least once
Last task (after the release)
-
Ensure the next RM trainee has an onboarding issue like this one, using the onboarding template.
Usernames
Username | |
---|---|
Gitlab.com | markglenfletcher |
dev | mark |
github | markglenfletcher |
Edited by Mark Fletcher