[SERVER-44730] Only enable content signatures for SConscripts in ninja generation Created: 19/Nov/19 Updated: 06/Dec/22 Resolved: 28/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathew Robinson (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Sprint: | Dev Platform 2020-02-24 |
| Participants: |
| Description |
|
Currently the content signature system is not working for the ninja file itself. This causes an awkward bootstrapping step for new users where they have to generate a ninja file then run ninja which will immediately regenerate the ninja file. We should improve this by teaching SCons how to actually determine out of date-ness for the ninja files. This will also allow us to eventually move to incremental ninja generation. |