[SERVER-64140] Implement toolchain release selection for server builds Created: 02/Mar/22 Updated: 21/Jun/23 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sdp-backlog-purge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||
| Sprint: | Dev Platform 2022-04-04, Dev Platform 2022-04-18 | ||||||||
| Participants: | |||||||||
| Description |
|
Now that we have a means of providing data about the toolchain to clients, we can set up the server build to run against the toolchain release configured for the platform. In cases where the required toolchain is not present, the build should look for "latest" path at /opt/mongodbtoolchain/<version> and fail if a toolchain is not found there, or emit a warning and use it. (This last part preserves the behavior for local developer builds and allows us to migrate Evergreen away from the path.) |
| Comments |
| Comment by Alex Neben [ 19/Jun/23 ] |
|
This has been identified as work that the SDP team won't do in the near term. Please reopen with a comment if you feel this work should be reprioritized and explain why. |
| Comment by Iryna Zhuravlova [ 02/May/22 ] |
|
The team decided to kick off this ticket to the backlog we don't technically need it to roll out v4. We will revisit this work after the further strategy regarding v4 is decided. |
| Comment by Githook User [ 25/Mar/22 ] |
|
Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}Message: |