v2.5.1
Summary
New ubuntu24 images, additional runner details in logs, scheduling retry mechanism if internal AWS server error when launching, and more.
Note: DO NOT USE this release. The new housekeeping behaviour is not working as expected.
What's Changed
- Add 'Private' dimension to cloudwatch stats
PrivateCloudFormation parameter now acceptsalwaysas value, in which case the runners will always launch in the private subnets by default (unless opt-out withprivate=false).- Fix issue with
privateattribute not being properly loaded from config file. - Add
Environment,IsPrivate, andStaticIp(if IsPrivate) to runner details (in Setup job logs) - Add ubuntu24 official images
- Increase frequency for spot interruption polling + add logs.
- Conform to AWS spec when sanitizing custom tags (key and value). Fixes #125.
- Add housekeeping task to handle edge cases where a job is still seen as queued by GitHub after a few minutes even after an instance has been launched:
// Cases:
// - instance is terminated and doesn't have the `runs-on-job-started` tag (due to spot interruption, AWS EC2 error).
// In this case, we need to launch a new instance, so we reschedule the runner.
// - instance is running and has the `runs-on-job-started` tag, which means the runner was stolen by another workflow job.
// In this case, we need to launch a new instance, so we reschedule the runner.