CI Decomposition - Staging Testing (all Engineering Managers to approve)
As we are very close to finalising our CI decomposition rollout &7791 (closed) . As of last week at 2022-06-17 05:00 UTC we deployed the final phase of CI decomposition to staging (staging.gitlab.com). We have run all QA tests so far and not noticed any issues but out of an abundance of caution we'd like all teams to do a small amount of manual testing in staging to be sure nothing is newly broken.
Ask
Please go to staging.gitlab.com and do a small amount of manual testing of your most critical features that you know should be working on staging.gitlab.com . Leave a comment on this issue if you notice anything surprising or concerning and we'll investigate it further as best we can. Ideally you'd leave some notes on timing/logs to look for if something goes wrong.
You may also choose to check the box without testing if you feel comfortable you've already done some manual testing since 2022-06-17 05:00 UTC or you are confident your automated tests in gitlab-qa would provide you good coverage.
This should take you (or a team member) less than 20 minutes. Reach us in #g_sharding if you need additional clarification.
Please leave a comment with information what was tested.
Please finish this before 2022-06-27. I will follow up with you or your manager if we don't get a response in the next few days so we can close this out quickly.
Some detail
To execute the CI decomposition we are going to take all services that interact with our Main Postgres database offline for 2 hours while we finish replicating data to CI and switchover and do some QA. After the decomposition the CI database will be totally independent from the main database and any CI tables remaining in the Main database will be stale, writes will be blocked and reads will be reading out of date rows.
You can read more about how this was rolled out in stages &6160 (closed) if you want.
Teams
-
Authentication & Authorization: @jarka -
Workspace: @mksionek -
Compliance: @dennis -
Project Management: @donaldcook -
Product Planning: @johnhope -
Certify: @johnhope -
Source Code: @sean_carroll -
Code Review: @andr3 (covering for @mnohr) -
Editor: @oregand -
Gitaly: @john.mcdonnell -
Integrations: @arturoherrero -
Foundations: @leipert -
Pipeline Execution: @marknuzzo -
Pipeline Authoring: @marknuzzo -
Runner: @erushton -
Pipeline Insights: @shampton -
Package: @michelletorres -
Release: @nicolewilliams -
Configure: @anna_vovchenko / @nmezzopera -
Respond: @crystalpoole -
Static Analysis: @twoodham -
Dynamic Analysis: @sethgitlab -
Composition Analysis: @gonzoyumo -
Threat Insights: @thiagocsf -
Vulnerability Research: @mark.art -
Container Security: @thiagocsf -
Product Intelligence: @alinamihaila -
Purchase: @rhardarson -
Utilization: @csouthard -
Fulfillment Platform: @jameslopez -
Distribution:Build: @twk3 -
Distribution:Deploy: @mendeni -
Geo: @juan-silva -
Memory: @mkaeppler -
Global Search: @dgruzd -
Database: @alexives -
Sharding: @DylanGriffith -
Import: @wortschi -
Optimize: @blabuschagne -
Observability: @nicholasklick -
Anti-Abuse: @jayswain -
Applied Machine Learning: @mray2020 -
MLOps: @mray2020 -
DataOps: @mray2020 -
Conversion: @kniechajewicz -
Expansion: kniechajewicz -
Adoption: @jayswain -
Provision: @jameslopez