Skip to content

Blog post for CI decomposition

Dylan Griffith requested to merge ci-decomposition-technical-blog-post into master

Why is this change being made?

Review app:

  1. Part 1: https://ci-decomposition-technical-blog-post.about.gitlab-review.app/blog/2022/07/15/path-to-decomposing-gitlab-database-part1/
  2. Part 2: https://ci-decomposition-technical-blog-post.about.gitlab-review.app/blog/2022/07/15/path-to-decomposing-gitlab-database-part2/
  3. Part 3: https://ci-decomposition-technical-blog-post.about.gitlab-review.app/blog/2022/07/15/path-to-decomposing-gitlab-database-part3/

This is a technical overview of the entire CI decomposition project which we just finished with https://about.gitlab.com/blog/2022/06/02/splitting-database-into-main-and-ci/ . This was a year long project with a lot of people involved and lots of insights gained along the way.

I think this is useful content to help with engineering recruiting efforts and general industry visibility as it represents one of the largest and most technically complex projects we’ve worked on at GItLab ever and in general represents a scale of complexity that few other companies get to work at. Also this gives a unique oppportunity to highlight and contrast with other companies the level of transparency at GitLab. Much of this work took place in public and we have lots of links for people to dive even deeper if they’re interested.

Author Checklist

  • 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.
  • 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
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Dylan Griffith

Merge request reports