# Production Change Lock CR for the Soft PCL - https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#soft-pcl This CR will prevent deployments during the PCL period. For a full description of restrictions please see https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#production-change-lock-pcl ### Lock Summary Soft PCL during the [GitLab Transcend event](https://about.gitlab.com/events/transcend/india/) on 2026-10-06 in Bengaluru, India. Current schedule as per the event webpage: `2026-10-06T11:30Z (5 pm IST) to 2026-10-06T16:00Z (9:30 pm IST)` {width=653 height=600} The Soft PCL will be set from a few hours before the event begins to a few hours after the event ends. This provides us enough time to respond to any issues created by the last deployment to GitLab.com before the PCL. The goal of this PCL is to avoid deployments to GitLab.com and ensure that the system is stable. We were talking about coordination on a different issue as well: https://gitlab.com/gitlab-com/gl-infra/delivery/-/work_items/22370+. ### Details 1. **Lock type** - {+ Soft +} 1. **Lock DRI** - {+ @dawsmith +} 1. **Start Date** - {+ 2026-10-06 03:00 UTC +} 1. **End Date** - {+ 2026-10-06 20:00 UTC +} ## Detailed steps for the change ### Change Steps - steps to take to execute the change _Estimated Time to Complete (mins)_ - {+ 900 +} - [x] On 2026-10-06 at 03:00 UTC, Set label production-engineering~54266819 `/label ~change::in-progress` - [ ] On 2026-10-06 at 20:00 UTC, Set label production-engineering~54266823 `/label ~change::complete` ## Rollback ### Rollback steps - steps to be taken in the event of a need to rollback this change _Estimated Time to Complete (mins)_ - {+ 5 +} - [ ] Set label ~"change::aborted" `/label ~change::aborted` ## Change Reviewer checklist production-engineering~8276990 ~C3 ~C2 ~C1: - [x] Check if the following applies: - The **scheduled day and time** of execution of the change is appropriate. - The [change plan](#detailed-steps-for-the-change) is technically accurate. - The change plan includes **estimated timing values** based on previous testing. - The change plan includes a viable [rollback plan](#rollback). - The specified [metrics/monitoring dashboards](#key-metrics-to-observe) provide sufficient visibility for the change. production-engineering~8276978 ~C1: - [x] Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details). - The change plan includes success measures for all steps/milestones during the execution. - The change adequately minimizes risk within the environment/service. - The performance implications of executing the change are well-understood and documented. - The specified metrics/monitoring dashboards provide sufficient visibility for the change. - If not, is it possible (or necessary) to make changes to observability platforms for added visibility? - The change has a primary and secondary SRE with knowledge of the details available during the change window. - The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval. - The labels production-engineering~24972270 and/or ~"blocks feature-flags" are applied as necessary. ## Change Technician checklist - [x] Check if all items below are complete: - The [change plan](#detailed-steps-for-the-change) is technically accurate. - This Change Issue is linked to the appropriate Issue and/or Epic - Change has been tested in staging and results noted in a comment on this issue. - A dry-run has been conducted and results noted in a comment on this issue. - The change execution window respects the [Production Change Lock periods](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#production-change-lock-pcl). - For production-engineering~8276976 and ~C2 change issues, the change event is added to the [GitLab Production](https://calendar.google.com/calendar/embed?src=gitlab.com_si2ach70eb1j65cnu040m3alq0%40group.calendar.google.com) calendar. - For production-engineering~8276976 and ~C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention `@sre-oncall` and this issue and await their acknowledgement.) - For production-engineering~8276976 and ~C2 change issues, the SRE on-call provided approval with the ~eoc_approved label on the issue. - For production-engineering~8276976 and ~C2 change issues, the Infrastructure Manager provided approval with the ~manager_approved label on the issue. - Release managers have been informed prior to any C1, C2, or production-engineering~24972270 change being rolled out. (In #production channel, mention `@release-managers` and this issue and await their acknowledgment.) - There are currently no [active incidents](https://gitlab.com/gitlab-com/gl-infra/production/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=Incident%3A%3AActive) that are production-engineering~3760139 or ~severity::2 - If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.