Update BSON compatibility tests to use a hard-coded server version

    • Type: Build Failure
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: CI
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a... Node Driver developer
      I want... BSON compat tests to run a stable application against latest BSON library
      So that... we'll be notified about BSON library incompatibilities with a 7.0 app, instead of being notified about server incompatibilities with 7.0 driver+tests.

      User Experience

      • When BSON compat tests run, they will run against a steady version (eg. 8.0.26), instead of running against a floating version
      • Current version is "8.0", so we picked up "8.0.26" for a while, but then broke when "8.0.28" came out, because the behavior of 8.0.28 was different than what our 7.0 driver+tests expected
      • Updated BSON compat tests will now run against "v8.0-perf", a pinned version in the drivers-evergreen-tools repo that corresponds to "8.0.1" release.
      • Use pinned version "v8.0-perf" so we don't have a lot of arbitrary "pinned" versions specified

      Dependencies

      • None

      Risks/Unknowns

      • This stabilizes the version, instead of allowing a floating 8.0.X version, so this is reducing risks

      Acceptance Criteria

      Implementation Requirements

      • server version is set to hard coded to a specific version like "8.0.26" or "v8.0-perf" (or another version that we choose)

      Testing Requirements

      • BSON compat tests pass

      Documentation Requirements

      • None

      Follow Up Requirements

      • None

            Assignee:
            Pavel Safronov
            Reporter:
            Pavel Safronov
            Johnathan Martell
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: