[SERVER-63737] Create mongodbtoolchain interface script Created: 16/Feb/22  Updated: 29/Oct/23  Resolved: 14/Mar/22

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

Type: Improvement Priority: Major - P3
Reporter: Ryan Egesdahl (Inactive) Assignee: Ryan Egesdahl (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Gantt Dependency
has to be done before SERVER-64140 Implement toolchain release selection... Closed
Backwards Compatibility: Fully Compatible
Sprint: Dev Platform 2022-02-21, Dev Platform 2022-03-07, Dev Platform 2022-03-21
Participants:

 Description   

We need some way of telling builds what release of the toolchain should be in use and where to find any tools for a given release and version. Create an interface script that can provide this data to consumers.



 Comments   
Comment by Githook User [ 14/Mar/22 ]

Author:

{'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}

Message: SERVER-63737 Add toolchain data script
Branch: master
https://github.com/mongodb/mongo/commit/36821093f23074d77d7a0aaae59cf56402cdbf50

Comment by Andrew Morrow (Inactive) [ 02/Mar/22 ]

OK I'll have a look when I get to the review.

Comment by Ryan Egesdahl (Inactive) [ 01/Mar/22 ]

acm The Python module can also operate as a CLI script with the same functionality. Non-Bash scripts and scripts in the evergreen directory should be able to use it without a problem.

Comment by Andrew Morrow (Inactive) [ 01/Mar/22 ]

Basically, we should be aiming for zero references to /opt/mongodbtoolchain anywhere except a fixed set of seed files.

Comment by Andrew Morrow (Inactive) [ 01/Mar/22 ]

I think based on recent slack discussions regarding the coverage builder that this feature needs to also encompass ensuring that scripts like those within the evergreen directory are also able to abstract away the toolchain selection.

Generated at Thu Feb 08 05:58:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.