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
🚀 Improve cache warm performances by not recompiling already in-cache targets #3585
Conversation
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.
This would be a great productivity boost, I don't see why we should not do this 👀
# Conflicts: # Sources/ProjectDescription/Dependencies/SwiftPackageManagerDependencies.swift
@danyf90 as commented offline I just pushed the fix for the logic, this should now work fine :) It would be great if you could try out a bit with your project! (I didn't update the tests) |
Looks like it's working great 😍 |
The current logic for building the cache is to just prune the graph and build the required targets, but it doesn't replace dependencies with their cached artifact, even if already available.
Resurrection of #2404 and #2377. Now that we are pushing for caching, and especially remote one (which means we would probably compile those from scratch and we might not have their derived data), it is becoming more important to have this behavior