Fix Bazel build #3181
Open
Fix Bazel build #3181
+18
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SimplyDanny
requested review from
ahoppen,
bnbarham,
hamishknight,
keith and
rintaro
as code owners
keith
approved these changes
Oct 31, 2025
|
@swift-ci please test |
|
Probably need to clone the repo in the build job as well ... 🤦♂️ |
SimplyDanny
force-pushed
the
bazel-build
branch
from
e02e0c0 to
e05854f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building with Bazel doesn't work at the moment. That's mainly due to the missing dependencies for
SwiftRefactorTestandSwiftSyntaxMacros. However, there is also an issue withrules_pythonwhich gets fixed by the update of the Bazel version.To alleviate the risk of causing an outdated Bazel configuration again, I also added an action that at least builds everything in PRs.