Skip to content

Updates the workaround label process for Environment Automation

Oriol Lluch requested to merge updates-workaround-label-process into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

In order to keep the lights on for GitLab Dedicated, there are situations where we need to apply temporary workarounds for bugs on upstream libraries that are outside of our control. Some of these temporary workarounds may imply some manual operations to be performed by the team at periodic times, which is toil that adds up in the team's cognitive load.

We propose in this MR an improvements in the temporary workaround process with the aim to simplify how we apply the labels and the queries required to get a picture of all the active workarounds.

Relates to: https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/2576#note_1506479759

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Merge request reports