Release 11.4.9
Preparation
-
Create preparation MRs for this version and add the links below: # In the release-tools project: bundle exec rake "patch_merge_request[11.4.9]"
-
Add changes into preparation MRs following their instructions -
Ensure the CE preparation MR has been fully merged into the EE counterpart -
Merge the preparation branches -
For omnibus-gitlab
add the changes to the stable branches:- Before the 7th: merge master into the CE stable branch, then merge the CE stable branch into EE.
- After the 7th: cherry-pick remaining merge requests directly into CE stable branch. Then, merge the CE Omnibus stable branch into EE.
-
Check the following list of critical issues/MRs which are to be included in
11.4.9
. Ensure each has made both CE and EE:-
REFERENCE_TO_MR_TO_PICK
-
-
Ensure builds are green on Omnibus CE stable branch and Omnibus EE stable branch
Packaging
-
Sync stable branches for CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE, and paste the diff in a comment: git diff -M v<PREVIOUS_TAG>-ee..11-4-stable-ee -- db/migrate db/post_migrate ee/db/migrate ee/db/post_migrate
-
Tag the 11.4.9
version using therelease
command:# In Slack: /chatops run tag 11.4.9
-
While waiting for packages to build, now is a good time to prepare the blog post. Look at previous MRs for examples. => gitlab-com/www-gitlab-com!16986 (merged) -
Check progress of EE packages build and CE packages build. - This might take a while (around 80 min).
- We only need the EE packages to finish to continue with next steps.
Deploy
Deploys to production require confirmation from a production team member before
proceeding. Use !oncall prod
in the #production
channel to find who's on
call and ping someone. Deploys to staging or canary can be done at will, just
mention it in the #production
channel.
-
Warm up the packages in the /takeoff by running: # In Slack: /chatops run deploy 11.4.9-ee.0 --warmup
staging.gitlab.com
-
Inform the oncall in the #production channel about staging deploy -
Check if there are any post-deployment patches that need to be re-applied. If there are, the deployment must be halted and assessed as to the impact of undoing the patches because of the release. To proceed, approval must be given by the manager oncall. -
On video call, deploy 11.4.9
to staging.gitlab.com# In Slack: /chatops run deploy 11.4.9-ee.0
-
Comment with the output of the migrations from the takeoff script in this issue -
Link to deployment job (even failed attempts) =>
QA
-
Create a "QA Task" issue using the ChatOps command: # In Slack, replacing LAST_DEPLOYED_VERSION with the appropriate value: /chatops run qa_issue vLAST_DEPLOYED_VERSION..v11.4.9
-
Wait for the QA Task deadline to pass
gitlab.com canary VMs
-
Inform the oncall in the #production channel about canary deploy -
On video call, deploy 11.4.9
to canary vms in production# In Slack: /chatops run deploy 11.4.9-ee.0 --production --canary
-
Link to deployment job (even failed attempts) => -
Confirm that there are no errors on canary
gitlab.com (production)
-
Confirm there are no critical alerts on gitlab.com on the alerting dashboard -
Get confirmation from a production team member to deploy to production In #production
, use!oncall prod
to find who's on call, and@mention
them asking to deploy to production -
If someone besides the oncall confirms, @mention
the oncall so they are aware. -
On video call, deploy 11.4.9
to GitLab.com# In Slack: /chatops run deploy 11.4.9-ee.0 --production
-
Link to deployment job (even failed attempts) => -
Check if there are any post-deployment patches that need to be re-applied. If there are, the deployment must be halted and assessed as to the impact of undoing the patches because of the release. To proceed, approval must be given by the manager oncall.
Release
-
Publish the packages via ChatOps: # In Slack: /chatops run publish 11.4.9
-
Create the 11.4.9
version on version.gitlab.com -
Deploy the blog post -
Post a tweet about the 11.4.9
release in the#releases
channel:!tweet "GitLab 11.4.9 is now available: [BLOG_POST_URL] [DESCRIPTION_OF_CHANGES]"
References
gitlab.com
- https://gitlab.com/gitlab-org/gitlab-ce/commits/11-4-stable
- https://gitlab.com/gitlab-org/gitlab-ee/commits/11-4-stable-ee
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/11-4-stable
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/11-4-stable-ee