-
-
Notifications
You must be signed in to change notification settings - Fork 506
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
Fix caching tuist #5585
Fix caching tuist #5585
Conversation
7e2bb9d
to
c6dfa9c
Compare
e4bfa3e
to
981478c
Compare
@@ -29,6 +29,10 @@ func targets() -> [Target] { | |||
.target(name: "TuistKit"), | |||
.target(name: "ProjectDescription"), | |||
.target(name: "ProjectAutomation"), | |||
.external(name: "SwiftToolsSupport"), |
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.
Were we importing those in code without explicitly declaring them here? I wonder if we can do something to prevent these things again.
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.
I wonder if we can do something to prevent these things again.
We could scan for import XXX
statements. Not sure if there's a better way π€
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.
Brilliant work @fortmarek ππΌ. Dog-fooding is critical to keep improving Tuist and Tuist Cloud
143b249
to
e706599
Compare
e706599
to
f73e228
Compare
Short description π
This PR does two things:
tuist
project definition, so replacing individual binaries works correctlycache warm
both for Sillicon and Intel machinestuist test
should now reuse these binaries when available, making those tests fasterThe only downside of these changes is that now we have lots of warnings that dependencies are imported by multiple targets. We should follow up on this PR and make it possible to selectively disable this warning for frameworks where you know duplicated symbols won't cause issues.
How to test the changes locally π§
tuist
Tuist Cloud instance, runtuist generate tuist
-> you should be able to run the CLI with the downloaded binaries.Contributor checklist β
make workspace/lint-fix
Reviewer checklist β
changelog:added
,changelog:fixed
, orchangelog:changed
, and the title is usable as a changelog entry