Skip to content

Conversation

@bkhouri
Copy link
Owner

@bkhouri bkhouri commented Dec 2, 2025

Add additional configurability to the GitHub automerger workflow to optionally create the PR as non-draft, and to trigger testing

ahoppen and others added 30 commits September 1, 2025 19:53
This allows Swift Packages to be tested in combination with PRs updating their dependencies. To reference a linked PR, `Linked PR: <link to PR>` needs to be added to the PR description, eg:

```
Linked PR: swiftlang/swift-syntax#2859
```
This change adds a call to `clang --version` after `swift --version` in the PR
workflow YML file. The result of this command is useful for investigating issues
stemming from out-of-date clang builds such as
swiftlang/swift-testing#1320.
* Add workflow to build packages for iOS.

Add workflow to build packages for iOS on a macOS VM. Can't run tests at this
time, but we can at least confirm source compiles.

* Build script can just use pwd instead of a child directory maybe

* Rename tests_ios
On some distributions (like Debian Bookworm), unzip is not installed in containers by default. Ensure we install it when needed.
* Update Android SDK build name to include NDK version

This allows differentiating them when multiple NDKs are used.

As far as multiple triples, I think those should be handled within the workflow, rather than splitting off into new matrix entries (especially as we already have some multi-triple build capabilities in swiftpm for macOS now and could conceivably extend that to Android), but that's for another PR.

* Fix variable reference in Android build script
* De-matrix Android triples

Building for multiple ABIs at once is something the swift-build frontend does for macOS and should eventually do for other platforms. Don't "lift" the triple into a new matrix axis.

This also renames the android_sdk_triple and android_ndk_version properties to plurals, since they support multiple versions. This is breaking, but the Android workflow is only a couple of days old, so this should be fine.

* Always use the current version of the Android script
…ng#182)

* Always use the current version of the scripts (Linux + Wasm)

This applies the changes previously made for Android to:

- Linux
- Linux Static SDK
- Wasm SDK
- Embedded Wasm SDK

* Apply checkout fix for Amazon Linux 2 to the embedded wasm SDK build

This was missed earlier.
This applies the changes previously made for Android to Windows
…ftlang#180)

This applies the changes previously made swift_package_test to the soundness checks.
Now disabled jobs will just disappear entirely, rather than appear with confusing unexpanded placeholders.
…#186)

The workspace is mounted into `C:\source` when using docker, update the
script root to take that into account.
* Add missing executable bit to install-and-build-with-sdk.sh script

* Don't use unnecessary piping

This causes failures to be ignored when -o pipefail is not set.

* Check out github-workflows into subdirectory

checkout@v1 and checkout@v4 differ in their behavior, try to make v1 clone the workflows repo in the same place as v4.

* Stop installing curl when we don't need it

This can save tens of seconds on some of the soundness checks.
…g#191)

This just installs and runs shellcheck. It doesn't need a 1 GB Swift toolchain image, use the much smaller baseline Ubuntu Noble variant. This makes shellcheck run faster and doesn't waste resources.
This avoids using unnecessary disk space that the action might need.
…t.sh` (swiftlang#193)

This allows us to override the `swift-format` executable to a locally built copy by adding the locally built version to PATH in swiftlang/swift-format#1093.
Add additional configurability to the GitHub automerger workflow to optionally create the PR as non-draft, and to trigger testing
@bkhouri
Copy link
Owner Author

bkhouri commented Dec 2, 2025

@swift-ci please test

@bkhouri bkhouri closed this Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.