[COMPASS-6361] Investigate changes in NODE-4869: improve mongodb-client-encryption release process Created: 08/Dec/22  Updated: 06/Jan/23  Resolved: 06/Jan/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: PM Bot Assignee: Unassigned
Resolution: Done Votes: 0
Labels: node-driver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on NODE-4869 improve mongodb-client-encryption rel... Backlog
Documentation Changes: Not Needed

 Description   

We release from the latest master on libmongocrypt.  While this is convenient for libmongocrypt bug fixes, this means that we never pin to a version of libmongocrypt and potentially release mongodb-client-encryption with in-progress changes.  We should instead release from a git tag and pin to particular versions of libmongocrypt.

While we're making this change, we should consider making our prebuild process explicit.  Currently, the prebuild script runs with every node tasks and makes itself a no-op when there are no changes to release.  It also has hard-coded logic to determine the architecture of the current system and conditionally run prebuild.

We could instead pipe an environment variable down from the config to control which build variants we want to release from.  This makes our build matrix explicit and easy to control, and removes the potential for multiple build variants to release the same package (our logic currently allows this for tasks run on the same evergreen distro).



 Comments   
Comment by Rhys Howell [ 06/Jan/23 ]

No changes to do here as this isn't doesn't look like it's changing the output of the `mongodb-client-encryption` package which we consume in both Compass and mongosh.

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