-
Notifications
You must be signed in to change notification settings - Fork 29
ci: use a shared workflow #1693
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
77be576
to
ea45ee9
Compare
The main motivation apart from reducing redundancy here, is that I am working on a PR to separate the integration testing into separate workflows to avoid the bazillion test deps. It would be nice to not copy around the full workflow |
a2ed382
to
385a309
Compare
CI seems happy
|
36cf033
to
9f70508
Compare
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.
Looks overall good to me, I'm always happy to remove duplication 👍
- name: Prepare build on macOS | ||
if: ${{ startsWith(inputs.os, 'macOS-') && inputs.localjll }} | ||
run: | | ||
echo "SDKROOT=$(xcrun --show-sdk-path)" >> "${GITHUB_ENV}" |
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.
How's this used? Is that picked up automatically by Bazel? Otherwise this seems to be completely unused.
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.
not sure. I picked it from the old local jll script. That said the macos local jll has been broken for ages so this might very well be unused
No description provided.