Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6495

Allow easy pinning/unpinning of driver evergreen tools version in our CI

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: CI
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      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

      • set 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 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

            Assignee:
            Unassigned Unassigned
            Reporter:
            daria.pardue@mongodb.com Daria Pardue
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: