A re-usable static SDK compilation workflow #3019
Open
Conversation
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
rnro
force-pushed
the
static_sdk_workflow
branch
8 times, most recently
from
8994714 to
13c8812
Compare
Motivation: We would like to offer the ability to opt-in to CI coverage for compilation against the Linux static SDK. Modifications: Introduce a workflow which will install a Swift snapshot and Linux SDK and test the repository builds against it. The script which sets up the VM will install snapshots and SDKs for either branch or released-version snapshots. They can be specified as: - a specific version string - the 'latest' version, the script attempts to find the most recent version enumerated on swift.org with both SDK and toolchain available - the most recent snapshot for the specified branch name enumerated on swift.org with both SDK and toolchain available At the moment the script should work on ubuntu and amazonlinux OSes, this can be expanded in the future. The current matrix covers testing building on Ubuntu Jammy for the main branch and latest released Swift version (6.0.2). Result: Increased CI coverage
rnro
force-pushed
the
static_sdk_workflow
branch
from
13c8812 to
177639d
Compare
FranzBusch
reviewed
Dec 13, 2024
| "swift":[ | ||
| { | ||
| "name":"latest-release Jammy", | ||
| "swift_version":"6.0.2", |
There was a problem hiding this comment.
Is this outdated as of today since 6.0.3 got released?
|
Is there any reason not to add this to the Swiftlang workflow repo straight away? |
We are not using the swiftlang repo for our matrix workflows right now. We plan on opening a PR to propose merging our matrix workflows into swiftlang but for now we are keeping them separate to iterate faster to a state where we feel good in upstreaming them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A re-usable static SDK compilation workflow
Motivation:
We would like to offer the ability to opt-in to CI coverage for compilation against the Linux static SDK.
Modifications:
Introduce a workflow which will install a Swift snapshot and Linux SDK
and test the repository builds against it.
The script which sets up the VM will install snapshots and SDKs for
either branch or released-version snapshots. They can be specified as:
version enumerated on swift.org with both SDK and toolchain available
swift.org with both SDK and toolchain available
At the moment the script should work on ubuntu and amazonlinux OSes,
this can be expanded in the future.
The current matrix covers testing building on Ubuntu Jammy for the main
branch and latest released Swift version (6.0.2) and enables it on our periodic CI runs.
See https://github.com/apple/swift-nio/actions/runs/12234697852/job/34124432584?pr=3019 for an example of this workflow in action.
Result:
Increased CI coverage