[SERVER-38654] Migrate embedded C driver build and release to C driver evergreen. Created: 14/Dec/18  Updated: 06/Dec/22  Resolved: 04/Nov/19

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Assigned Teams:
Server Development Platform
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Participants:

 Description   

Currently, the embedded SDK builds the C driver and the C driver extension, then bundles them up, and then takes them apart again for release.

It would be better if the embedded build of the C driver happened in the C drivers evergreen project.

Additionally, we should migrate the embedded C driver extension either into the C driver repository or a new repository, and then build and release it from a process outside of the server. Since the build of the extension depends on the embedded SDK headers, this would need to be a triggered cross-project build.


Generated at Thu Feb 08 04:49:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.