[CXX-2305] Reduce friction of Evergreen testing with C driver Created: 15/Jul/21  Updated: 08/Feb/23

Status: Backlog
Project: C++ Driver
Component/s: Testing
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: CXX Driver Testing (Evergreen)

 Description   

Motivation

On evergreen, the two active C++ driver projects (development and release) build against two versions of the C driver:

  • The tip of the C driver development branch (most tasks)
  • The minimum required version of the C driver (on the Ubuntu 18.04 with minimum libmongoc variant)

There are some points of friction:

  • On the C++ release branch being tested, if C later deprecates API, the release branch will fail with deprecation warnings. It is atypical to backport a change to remove the deprecated C API.
  • C driver behavior changes may cause test failures and interfere with development. For example, CDRIVER-3958 changed the output of JSON, but did not necessitate a bump in the C++ driver's minimum dependency.

Scope
TBD. Investigate and decide on a strategy for what versions of the C driver makes sense to test against, and what the process should be for handling C behavior changes and deprecations.


Generated at Wed Feb 07 22:05:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.