[SERVER-61123] Set up evergreen.yml with explicit toolchain revisions Created: 29/Oct/21 Updated: 06/Dec/22 Resolved: 03/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | 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: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Participants: | |||||
| Description |
|
In order to support toolchain-on-EFS in BUILD-14158, we will need to have the server build with explicit toolchain revision IDs in Evergreen. If we didn't do this, then whenever the Build team adds a new toolchain revision, the "currently active" toolchain would switch to the new revision, potentially in the middle of a build. Having the server build against an explicit toolchain revision instead is much more predictable and stable. |
| Comments |
| Comment by Ryan Egesdahl (Inactive) [ 03/Mar/22 ] |
|
We're going to do this a different way. |