[SERVER-63836] Expose server compile flags in the evergreen patch UI Created: 18/Feb/22 Updated: 08/Sep/23 Resolved: 08/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Fix | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Participants: |
| Description |
|
There are times where it is helpful for bug reproducing, to compile the mongodb server with the same compile flags used when building certain variants run in evergreen. Currently, the workflow is to look up the compile flags associated in evergreen.yml. We should see if we can expose this in the patch UI, similar to what we currently do for Resmoke.py Invocation for Local Usage. |
| Comments |
| Comment by Alex Neben [ 03/Jan/23 ] |
|
I think the correct thing is to have variables / build profile for each unique build type. That should also be printed out. |
| Comment by Andrew Morrow (Inactive) [ 01/Mar/22 ] |
|
The SCons invocation used in evergreen is often quite different from the SCons invocation used locally. We already log the SCons invocation in the output, so it is fairly easy to find already, if you want it as a basis for constructing your own build invocation. I'm reluctant to see logic introduced that attempts to understand how to automatically transmogrify the evergreen relevant SCons invocation into a form suitable for local usage, as it would require whatever system handled that work to have detailed knowledge of the workings of the build system interface, which changes fairly frequently and varies by branch. Keeping the two in sync would entail additional work which, if neglected or overlooked, would give inaccurate results that would be actively harmful. |