-
-
Notifications
You must be signed in to change notification settings - Fork 49
Speed up GH build pipeline #3813
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
Conversation
I've asked on the forums if prebuilts might become available for release/6.1. If not, that's another reason to try and drop SwiftPM as a dependency. https://forums.swift.org/t/preview-swift-syntax-prebuilts-for-macros/80202/21 |
Actually, this might work. We have good reason to fork SwiftPM already - there are two open PRs we need and they're unlikely to be be merged and cherrypicked to release/6.1 anyway:
Especially the latter we need. We are currently not getting Postgres-NIO package updates due to that. So since we need that fork, we might as well change SwiftPM's dependency on SwiftSyntax to a release version that has a prebuilt instead of the release/6.1 branch. For what we actually use from SwiftPM this will make no difference. |
3da5237
to
02e010f
Compare
02e010f
to
09def83
Compare
I just bumped into this PR and I want to shamelessly plug this article we published yesterday: https://swiftonserver.com/faster-github-actions-ci-for-swift-projects/ I believe it'll have a way bigger impact on your build times than using prebuilts, although they don't contradict eachother. |
Ah, that looks very interesting! I’ve been meaning to look into caching and his seems to be exactly what we need :) Thanks @MahdiBM ! |
09def83
to
f7e27f7
Compare
Unfortunately, we can't benefit from this new flag that uses pre-built SwiftSyntax libraries at the moment.
Due to our dependence on SwiftPM's branch release/6.1, we depend on SwiftSyntax release/6.1, which does not have a prebuilt library and we end up building it ourselves, as before 😞