Similarly to the fomu-workshop, in this PR the CI infrastructure of this repo is migrated from Travis CI to GitHub Actions.
The artifacts of each workflow run are uploaded. Hence, users can retrieve the toolchain from specific PRs or any other branch push.
Furthermore, when master or a tagged commit are pushed, the artifacts are uploaded as assets of a (pre)release. If the (pre)release does not exist, it is created. If it exists, the assets are updated and the tag is updated, but the (pre)release is not recreated. The type of the release depends on the tag:
Artifacts produced after running untagged commits from branch master are updated to a prerelease named nightly.
Tagged commits corresponding to prereleases according to semver are published as prereleases.
Tagged commit corresponding to non-prereleases are published as regular releases.
Non semver compliant tagged commits are published as prereleases with the name matching the tag.
See eine/tip for further details about the Action used for uploading artifacts as (pre)release assets.
Some other minor enhancements are applied to build.sh.
Similarly to the fomu-workshop, in this PR the CI infrastructure of this repo is migrated from Travis CI to GitHub Actions.
The artifacts of each workflow run are uploaded. Hence, users can retrieve the toolchain from specific PRs or any other branch push.
Furthermore, when
masteror a tagged commit are pushed, the artifacts are uploaded as assets of a (pre)release. If the (pre)release does not exist, it is created. If it exists, the assets are updated and the tag is updated, but the (pre)release is not recreated. The type of the release depends on the tag:nightly.See eine/tip for further details about the Action used for uploading artifacts as (pre)release assets.
Some other minor enhancements are applied to
build.sh./cc @mithro