[SERVER-40000] Only inject the --release flag for builds run in the mongo-release project Created: 06/Mar/19 Updated: 29/Oct/23 Resolved: 01/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | 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 Tools 2019-05-06, Dev Tools 2019-10-07 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
None of the releases built in the main mongodb evergreen projects actually are released. Using the --release flag has the effect of turning off certain build performance enhancements that come with some degree of correctness risk. However, we apply those flags on all builds right now, without regard for whether we are actually doing a release build or not. If we arranged things so that the presence of the --release flag was conditioned on whether we were doing a real release build out of the mongo-release project, we could use these faster build modes in our regular waterfall build. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 01/Oct/19 ] |
|
This has been applied such that the --release flag is only applied for waterfall and release project builds of variants that have a push bucket. Waterfall builds without push bucket, and all patch and merge queue builds, will build without the --release flag and with the --implicit-cache flag, which should speed up all secondary compiles that run on the same machine, like compile_all. |
| Comment by Githook User [ 01/Oct/19 ] |
|
Author: {'email': 'andrew.morrow@10gen.com', 'name': 'Andrew Morrow'}Message: |