[SERVER-64620] Add a SCons tool to manage export files via scanners Created: 17/Mar/22  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0 Desired

Type: New Feature Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-57393 Replace use of for_signature based ge... Closed
Related
related to SERVER-82515 Complete TODO listed in SERVER-64620 Needs Scheduling
Assigned Teams:
Server Development Platform
Participants:

 Description   

We now have multiple instances of hand-rolled generators to manage export files for the cases where we need them:

They are actually all a little bit wrong: using the `csig` like that in the `for_signature` case is effective, in that it means if the file changes the target will be rebuilt, but it will be rebuilt because the signature of the action changed. That isn't really what happened though: the build action is really the same. Instead, if we wrote a scanner, then these would be picked up as implicit dependencies of the target automatically.

Build a tool to inject a scanner for export files and do all the magic automatically, then replace these usages. We should consider doing this for other places we are abusing the `csig` mechanism to detect changes, like in the sanitizer deny list setup.


Generated at Thu Feb 08 06:00:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.