Use Case

As a Node engineer,
I want CI fixes and tooling updates to be easily backported or cross-ported to other repos,
So that CI is up-to-date wherever we need to work.

Our active list of active branches / repos that need green CI and are impacted by CI tooling changes:

• 5.x, 6.0 and 6.x
• 5.x and 6.x
• kerberos
• libmongocrypt
• legacy driver
• zstd

Changes to CI configuration and to CI tooling constantly cause friction when we work on branches other than main in the driver and bson. Especially in the driver, we spend time backporting fixes that accommodate changes in drivers-evergreen-tools, changes to our own CI tooling, or just environment changes. A simplified process for managing our tooling across all supported branches and repos would enable us to make changes confidently and without friction when we need to on infrequently modified branches.

Acceptance Criteria

• Investigate solutions to streamlining CI setup across our supported repos. Some potential solutions:
  • consolidate all CI tooling and utilities into a separate repo, possibly an npm package, and add it as a dependency wherever needed. consider using dependabot to automatically pull in updates when necessary
  • consider tooling that can automatically sync changes across our supported repos and branches whenever changes are made
• Document approaches considered and outline the pros/cons of each.
• Have the team review, and determine if we will consider fixing this issue and if so, determine the solution we will implement.