Skip to content

Disable gitlab-org/gitlab CI pre-clone script

Production Change

Change Summary

Because of the work done in &463 (closed) we should no longer need the CI pre-clone script on gitlab-org/gitlab. This change issue is here to create a record of the change.

Change Details

  1. Services Impacted - ServiceGitaly ServiceGit
  2. Change Technician - @jacobvosmaer-gitlab
  3. Change Reviewer - @qmnguyen0711
  4. Time tracking - 30m
  5. Downtime Component - No

Detailed steps for the change

Pre-Change Steps - steps to be completed before execution of the change

Estimated Time to Complete (mins) - 5

  • Set label changein-progress on this issue
  • Announce change in #g_engineering_productivity

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 5

  • Go to gitlab-org/gitlab CI settings, open "General pipelines", set "Git strategy" to "git clone" and save changes

Post-Change Steps - steps to take to verify the change

Estimated Time to Complete (mins) - 20

  • monitor server metrics for file-cny-01 (see below)

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 5

  • Go to gitlab-org/gitlab CI settings, open "General pipelines", set "Git strategy" to "git fetch" and save changes

Monitoring

Key metrics to observe

  • Metric: file-cny-01 apdex and saturation
    • Location: file-cny-01 dashboard
    • What changes to this metric should prompt a rollback: apdex SLI violations
  • Metric: PostUploadPackWithSidechannel error rate

Summary of infrastructure changes

  • Does this change introduce new compute instances? No
  • Does this change re-size any existing compute instances? No
  • Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc? No

Changes checklist

  • This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
  • This issue has the change technician as the assignee.
  • Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Necessary approvals have been completed based on the Change Management Workflow.
  • 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.
  • 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.)
  • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
  • There are currently no active incidents.
Edited by Jacob Vosmaer