print dependency version information in CI in our mocha log

XMLWordPrintableJSON

    • 3
    • 2
    • None
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a driver engineer,
      I want to print package version information for any optional dependencies that are being used for a test run,
      So that we can easily determine what environment a test run executed in.

      While I was working on https://jira.mongodb.org/browse/NODE-5424 (adding tests that always test against mongodb-client-encryption@6.0.0), I realized that there's no easy way (without modifying JS or evergreen scripts) to see which versions of a package are being used for an execution of our test suite. I wanted to confirm that the version of `mongodb-client-encryption` used for the tests was the correct version.

      We could add version information to each package we use to our printout in CI:

      • kerberos
      • zstd
      • snappy
      • mongodb-client-encryption
      • bson (this might not be necessary)
      • saslprep
      • credential-providers
      • gcp-metadata

      Here's an example of the sort of info I think would be useful, implemented for FLE: https://evergreen.mongodb.com/task_log_raw/mongo_node_driver_next_rhel8_custom_dependency_tests_test_latest_driver_mongodb_client_encryption_6.0.0_patch_787bdbf3f7bd974aca1347de427e973217c90009_64d28f272a60edf3c608b767_23_08_08_18_53_34/0?type=T#L687

      User Impact

      n/a

      Dependencies

      n/a

      Unknowns

      • Do we want to export a "version" from each of the packages we support and use that in driver CI?

      Acceptance Criteria

      Implementation Requirements

      • For each package listed above, we should include whether the package is installed and if so, which version is being used in our CI metadata printout.

      Testing Requirements

      n/a

      Documentation Requirements

      n/a

      Follow Up Requirements

      n/a

            Assignee:
            Johnathan Martell
            Reporter:
            Bailey Pearson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: