Use Case

As a Node.js engineer
I want to be able to easily test my add-on changes for driver compatibility
So that I can be confident about the compat between the driver and its add-on packages

User Impact

• None

Dependencies

• None

Unknowns

• Evergreen triggers work by listening to another project but the new repo does not have a project.

Acceptance Criteria

Implementation Requirements

• For each of our supported driver add-on packages (bson, mongodb-client-encryption, zstd, kerberos, mongodb-legacy):
  • Create tooling to make it easy to test a dev branch of the add-on library against a driver branch (main by default)
  • If possible, integrate tooling into the add-on CI as an optional configurable task so that the results are accessible from GH on the PR
  • If possible, on merge to main, kick off a build in the driver main evergreen project
  • Timebox the effort of trying to get the "if possible" parts to work to a day or two

Testing Requirements

• Manually test to ensure this works as expected for each library with driver-main and an arbitrary driver commit
• If the driver evergreen integration is implemented, verify that the integration works

Documentation Requirements

• None

Follow Up Requirements

• None