[SERVER-50087] Provide a way to disable compile bypass from the command line or config files Created: 01/Aug/20 Updated: 25/Mar/21 Resolved: 25/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
I never want the compile bypass feature to kick in on my patch builds. About every second or third patch build I do, I get erroneous results because of it. I end up needing to make synthetic commits to place comments in files that I know will disable it to work around, and then I need to remember to revert those changes before I send my work to the commit queue. I'd like evergreen to provide a way that I can, using an option to the evergreen command line tool, or better a configuration file setting, ensure that compile bypass is never applied to my patches. |
| Comments |
| Comment by David Bradford (Inactive) [ 25/Mar/21 ] |
|
I'm going to close this issue. We have remove the bypass compile logic. As we have improved the compile times in other ways, the value of bypass compile is less and less. But the cost of bypass compile has been pretty high. It has tended to be very fragile and has historically been broken for months at a time before anyone even noticed. If anyone want to strongly advocate that we should bring it back, we can have that conversation, but we should like investigate alternative designs that have lower maintenance costs. |