[SERVER-47341] Run build against a read-only source tree Created: 05/Apr/20 Updated: 29/Oct/23 Resolved: 09/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| 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 Platform 2020-04-06, Dev Platform 2020-04-20 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 55 | ||||||||
| Description |
|
We try hard to avoid writing to the source tree during a build, but we have no way to detect when we fail. We should mark the whole tree as read-only at the start of the build in the CI system. This will also help diagnose issues where some other process than the build itself alters the source tree out from under the build. |
| Comments |
| Comment by Githook User [ 10/Mar/21 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: Revert " This reverts commit 7d99356126fb3e921370c24c0a61499513bc78b6. |
| Comment by Githook User [ 08/Apr/20 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: Also, validate the presence of the file that goes missing before |