-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: iOS interop [WPB-15034] #850
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e2568dd
feat: iOS interop client
typfel 3b19886
feat: integrate iOS interop client into interop tests
typfel c1d1dc9
ci: add helper scripts for running the interop iOS app in the simulator
typfel 0f20492
ci: setup interop test for ios and re-use job for building ios artifacts
typfel 54f9a86
fix: chrome webdriver crashing when running on macos-latest runner
typfel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
concurrency: | ||
group: "${{ github.workflow }}-${{ github.ref }}-build-ios" | ||
cancel-in-progress: true | ||
|
||
on: | ||
workflow_call: | ||
|
||
env: | ||
CARGO_TERM_COLOR: always | ||
CARGO_NET_GIT_FETCH_WITH_CLI: true | ||
CARGO_REGISTRIES_CRATES_IO_PROTOCOL: sparse | ||
|
||
jobs: | ||
build-ios: | ||
runs-on: macos-latest | ||
strategy: | ||
matrix: | ||
task: | ||
- ios-device | ||
- ios-simulator-x86 | ||
- ios-simulator-arm | ||
steps: | ||
- uses: actions/checkout@v4 | ||
|
||
- name: determine rust target | ||
id: rust-target | ||
run: | | ||
if [[ "${{ matrix.task }}" == "ios-device" ]]; then | ||
echo "target=aarch64-apple-ios" >> $GITHUB_ENV | ||
elif [[ "${{ matrix.task }}" == "ios-simulator-x86" ]]; then | ||
echo "target=x86_64-apple-ios" >> $GITHUB_ENV | ||
elif [[ "${{ matrix.task }}" == "ios-simulator-arm" ]]; then | ||
echo "target=aarch64-apple-ios-sim" >> $GITHUB_ENV | ||
fi | ||
|
||
- uses: actions-rust-lang/setup-rust-toolchain@v1 | ||
with: | ||
target: ${{ env.target }} | ||
|
||
- name: setup cargo-make | ||
uses: davidB/rust-cargo-make@v1 | ||
|
||
- name: build ${{ matrix.task }} | ||
run: | | ||
cd crypto-ffi | ||
cargo make ${{ matrix.task }} | ||
|
||
- name: upload artifact | ||
uses: actions/upload-artifact@v4 | ||
with: | ||
name: ${{github.event.number}}-${{ matrix.task }} | ||
path: target | ||
retention-days: 1 | ||
overwrite: 'true' | ||
# Only needs to be uploaded once, this step finishes fastest. | ||
- name: upload ffi artifact | ||
if: startsWith(matrix.task, 'ios-simulator-arm') | ||
uses: actions/upload-artifact@v4 | ||
with: | ||
name: ${{github.event.number}}-swift-ffi | ||
path: crypto-ffi/bindings/swift/WireCoreCrypto | ||
retention-days: 1 | ||
overwrite: 'true' |
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Here we're using
github.event.number
, elsewhere we're usinggithub.run_id
to uniquely name artifacts. I think we should be consistent, and usegithub.run_id
everywhere, unless there is a good reason to prefergithub.event.number
here.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 just moved the job into separate file maybe @coriolinus can give a reason.
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 didn't touch that actually; it appears to come from 1ce7d95, which is @SimonThormeyer.
I don't think there's a strong reason here to prefer either one here. TBH we'd probably be fine without a distinguishing number in either case; looking deeper into the download artifact action, it automatically partitions by run id anyway. Adding an event number or run id just helps us keep track of things if we happen to download some artifacts for manual inspection.
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.
Ah, didn't know that, thanks!