Wasmtime GitHub notifications bot (Mar 20 2025 at 20:27): Wasmtime GitHub notifications bot (Mar 20 2025 at 20:27):alexcrichton opened PR #10438 from alexcrichton:more-ci to bytecodealliance:main:
This commit is preparation for the infrastructure to be used when supporting [Wasmtime LTS releases][rfc]. The goal here is to add some automation and infrastructure to perform a weekly build of all active release branches which will file an issue on failure. This should ideally keep branches up-to-date and ensure that we don't forget to backport any fixes to older branches. Or rather when we do forget to backport fixes this'll be a reminder to go do that anyway.
The general architecture here is:
- A new
ci-cron-trigger.ymlworkflow is added.- This new workflow runs once-a-week and runs a small script that triggers CI for all active release branches.
- The main CI,
main.yml, is updated to file an issue on failure when triggered in this fashion.While I was here I additionally removed the
schedule:from themain.ymlto instead fold the daily scheduling of CI runs into this new script as well. That way all our cron CI jobs are gated in workflows that require this exact repository meaning that forks won't be running cron jobs.[rfc]: https://github.com/bytecodealliance/rfcs/pull/42
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Mar 20 2025 at 20:27):alexcrichton requested fitzgen for a review on PR #10438.
Wasmtime GitHub notifications bot (Mar 20 2025 at 20:27):alexcrichton requested wasmtime-default-reviewers for a review on PR #10438.
Wasmtime GitHub notifications bot (Mar 20 2025 at 20:28):alexcrichton commented on PR #10438:
I've tested things locally except for the final bit of logic to file an issue, which I think I've fixed after testing locally as well. I'll manually trigger this CI run when this merges to ensure everything's working though. My hope is that 24.0.0 is probably broken at this time and we'll need to fix something so we should see an issue pop up.
Wasmtime GitHub notifications bot (Mar 20 2025 at 20:30):alexcrichton submitted PR review.
Wasmtime GitHub notifications bot (Mar 20 2025 at 20:30):alexcrichton created PR review comment:
This is technically somewhat inaccurate. If an LTS branch has been created, but not released, then we need to still look back 2 releases. The risk of that causing issues is pretty small though as that's a 2-week window and I otherwise don't know how to easily test for whether the latest branch has been released or not as part of this script.
Wasmtime GitHub notifications bot (Mar 20 2025 at 20:47):fitzgen submitted PR review.
Wasmtime GitHub notifications bot (Mar 20 2025 at 21:33):alexcrichton merged PR #10438.
Last updated: Apr 17 2025 at 21:03 UTC