[SERVER-54700] Offer a parameterized builds customization point for compile flags Created: 22/Feb/21 Updated: 29/Oct/23 Resolved: 24/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Dev Platform 2021-03-08 | ||||
| Participants: | |||||
| Description |
|
I’d like to propose that we add support for setting additional compile flags in patch builds for the server, sys-perf, and performance projects by way of https://github.com/evergreen-ci/evergreen/wiki/Parameterized-Builds. Right now if I want to patch build a change to a compile flag, I either need to make a source code edit to the build system to make a flag I want to enable on by default, or I need to edit the yaml file to add the new flag to the declared compile flags. That’s not so bad for a one off test, but it makes it hard to script a whole bunch of experiments. Additionally, local edits have a risk of getting pushed. |
| Comments |
| Comment by Githook User [ 24/Feb/21 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: |
| Comment by Andrew Morrow (Inactive) [ 23/Feb/21 ] |
|
Code review URL: https://mongodbcr.appspot.com/753290013/ |