Skip to content
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

Merged
merged 3 commits into from
Nov 19, 2023
Merged

Fix caching tuist #5585

merged 3 commits into from
Nov 19, 2023

Conversation

fortmarek
Copy link
Member

Short description πŸ“

This PR does two things:

  • Fixes tuist project definition, so replacing individual binaries works correctly
  • Sets up pipelines to run cache warm both for Sillicon and Intel machines
  • tuist test should now reuse these binaries when available, making those tests faster

The 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 🧐

  • CI should pass
  • If you can connect to our tuist Tuist Cloud instance, run tuist generate tuist -> you should be able to run the CLI with the downloaded binaries.

Contributor checklist βœ…

  • The code has been linted using run make workspace/lint-fix
  • The change is tested via unit testing or acceptance testing, or both
  • The title of the PR is formulated in a way that is usable as a changelog entry
  • In case the PR introduces changes that affect users, the documentation has been updated

Reviewer checklist βœ…

  • The code architecture and patterns are consistent with the rest of the codebase
  • Reviewer has checked that, if needed, the PR includes the label changelog:added, changelog:fixed, or changelog:changed, and the title is usable as a changelog entry

@fortmarek fortmarek changed the title Fix/tuist meta cache Fix caching tuist Nov 16, 2023
.github/workflows/tuist.yml Outdated Show resolved Hide resolved
@@ -29,6 +29,10 @@ func targets() -> [Target] {
.target(name: "TuistKit"),
.target(name: "ProjectDescription"),
.target(name: "ProjectAutomation"),
.external(name: "SwiftToolsSupport"),
Copy link
Contributor

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.

Copy link
Member Author

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 πŸ€”

Copy link
Contributor

@pepicrft pepicrft left a 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

@fortmarek fortmarek force-pushed the fix/tuist-meta-cache branch 4 times, most recently from 143b249 to e706599 Compare November 19, 2023 18:11
@fortmarek fortmarek merged commit 3da5d97 into main Nov 19, 2023
28 checks passed
@fortmarek fortmarek deleted the fix/tuist-meta-cache branch November 19, 2023 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants