[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:
Depends
Problem/Incident
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 "SERVER-47341 Mark sources read only during scons compile"

This reverts commit 7d99356126fb3e921370c24c0a61499513bc78b6.
Branch: master
https://github.com/mongodb/mongo/commit/5102ca3a6c0fa401d129d02ca9854949a6c4a19b

Comment by Githook User [ 08/Apr/20 ]

Author:

{'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}

Message: SERVER-47341 Mark sources read only during scons compile

Also, validate the presence of the file that goes missing before
and after the build. That way we have some idea of whether the file
was deleted by SCons (or concurrently with SCons) or by some other
task running in between SCons runs.
Branch: master
https://github.com/mongodb/mongo/commit/7d99356126fb3e921370c24c0a61499513bc78b6

Generated at Thu Feb 08 05:13:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.