Skip to content

Defining Business Outcomes and DRIs for CI build speed working group

Gabriel Engel requested to merge gabrielengel_gl-main-patch-da42 into main

Why is this change being made?

@allison.browne @grzesiek @ajwalker @ofalk @dnsmichi @mbobin @cheryl.li

I've created this MR to discuss the business outcomes of the working group and to define DRIs. It would be great to get volunteers for each of them.

If you want we can split down bigger business outcomes such as 1. CI benchmark framework or 3. Technical improvements in a/b/c for different directions to explore, but I'll leave that up to the group to discuss.

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
Edited by Gabriel Engel

Merge request reports