gha-setup-swift
gha-setup-swift copied to clipboard
compnerd
Setup Swift (on Windows) on GitHub Actions Builders
Use /etc/os-release for identifying the Linux distribution rather than `lsb_release`. Co-Authored-By: Gwynne Raskind
https://github.com/kelvin13/swift-json/blob/master/.github/workflows/build.yml#L38 as an example
- Use `/etc/os-release` to check Linux versions (`lsb_release` is obsolete and not always available) - Iinstall Linux toolchain to better prefix - Fix GHA syntax of Linux error message -...
If I give a tag name, what is the branch name used for (and vice-versa)? Either one uniquely identifies a release. Please clarify in the README.
This method of getting `TOOLCHAINS` set up is obviously too fragile and hacky in the long run, but seems to be working for now. Please squash-merge
[This run](https://github.com/hylo-lang/Swifty-LLVM/actions/runs/8207602540/workflow) demonstrates. Follow the link to the workflow file if you need to reproduce elsewhere. Maybe you could use this as a unit test case for this action.
See https://github.com/hylo-lang/hylo/actions/runs/9357322028/job/26052808446#step:12:315 Possibly relevant: we [setup-vsdevenv before setting up Swift](https://github.com/hylo-lang/hylo/actions/runs/9357322028/workflow#L242-L248); that used to be necessary but might now be obsolete?
My Windows [ci.yml](https://github.com/skiptools/swift-sqlcipher/blob/main/.github/workflows/ci.yml) just started failing yesterday (since https://github.com/compnerd/gha-setup-swift/commit/17be5ca66ad69b44177f01b6b0b23575d3d7791a): ```yml windows: runs-on: windows-2019 steps: - uses: compnerd/gha-setup-swift@main with: branch: swift-5.9-release tag: 5.9-RELEASE - uses: actions/checkout@v4 - run: swift test ```...
