Use Case

As a... Node driver engineer
I want... to be able to easily pin (and unpin) to the last known working commit when a driver tools change breaks our CI
So that... our development work doesn't risk grinding to a halt on every potential push to driver evergreen tools

User Experience

• N/A

Dependencies

• None

Risks/Unknowns

• Can we also improve PR testing for driver CI compat in driver evergreen tools?

Acceptance Criteria

Implementation Requirements

• Try to integrate driver evergreen tools as a submodule into just the driver repo; set up dependabot for automatic updates (weekly)
  • Verify AWS ECS tests work after switching to submodule
  • Take no more than a day to get the submodule approach to work
• If that doesn't work, fall back to setting up an evergreen variable to control the version of driver evergreen tools used in CI and update our scripts to use it

Testing Requirements

• Make sure all CI tests are able to run and pass

Documentation Requirements

• N/A

Follow Up Requirements

• File DRIVERS ticket if we think we can improve integration testing of driver tools PRs