-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude derived data folders from from Xcode #64
base: develop
Are you sure you want to change the base?
Conversation
Co-authored-by: Jed Fox <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the addition!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests failing here made me dig deeper, and I'm hoping someone with Xcode experience can help provide context.
From what I've read, Xcode will store build artifacts in the DerivedData/
directory, and this is usually(?) at a system-wide level (e.g. ~/Library/Developer/Xcode/DerivedData
) — is this correct? If so, Asimov would be better-served blocking that directory.
As it stands now, the code in this PR tells Asimov "Look for a DerivedData
directory that sits adjacent to...itself", which seems like a roundabout way of saying "Block all DerivedData
directories from Time Machine backups. However, that runs counter to Asimov's more conservative "make sure there's a matching dependency file so we don't block anything accidentally" ethos.
Granted, "DerivedData" seems very unlikely to be anything else on a developer's machine (save for perhaps some Swift developer's musical side-project), but I'd like to better understand this directory before including it in Asimov, please.
Hey! Thanks for the response. You're right, that the However it's very common to have it in the project directory. I do that as an iOS developer, and I know many other devs that do. That's why it's also listed in the default It's really a time machine killer, because these tend to be ~1GB even for a simple XCode project. What i can suggest is to make it conditional to exclude |
I think that makes the most sense, but it'll require refactoring how the We want to make sure that whatever we do here is still performant, but adding wildcard support would open up some opportunities. |
No description provided.