Changelog

2024-12-05

• Bugfix to no longer stop the reconciliation when a runner’s health check fails.

2024-12-04

• Clean up corresponding OpenStack runner resources when a unit of the charm is removed.

2024-11-27

• Fix “Available Runners” dashboard panel to work for multiple flavors.

2024-11-15

• Catch ReconcileError and set appropriate message in unit status.

2024-11-13

• Added documentation for the reactive mode (howto and mongodb integration references).
• Align the README with the one in GitHub - canonical/is-charms-template-repo: is-charms-template-repo - a terraform managed template repo.

2024-10-24

• Add “expected_runners” to reconciliation metric.

2024-10-23

• Fixed the wrong dateformat usage in the server uniqueness check.

2024-10-21

• Fixed bug with charm upgrade due to wrong ownership of reactive runner log directory.

2024-10-18

• Bugfix for logrotate configuration (“nocreate” must be passed explicitly)

2024-10-17

• Use in-memory authentication instead of clouds.yaml on disk for OpenStack. This prevents the multi-processing fighting over the file handle for the clouds.yaml file in the github-runner-manager.

• Fixed a bug where metrics storage for unmatched runners could not get cleaned up.

2024-10-11

• Added support for COS integration with reactive runners.
• The charm now creates a dedicated user which is used for running the reactive process and storing metrics and ssh keys (also for non-reactive mode).

2024-10-07

• Fixed the removal of proxy vars in .env file for LXD runners.
• Fixed a regression in the removal of leftover directories.
• Improved reconciliation for reactive runners.

2024-09-27

• Added job label validation when consuming a job from the message queue.

2024-09-24

• Added support for spawning a runner reactively.
• Fixed a bug where busy runners are killed instead of only idle runners.

2024-09-18

• Changed code to be able to spawn a runner in reactive mode.
• Removed reactive mode support for LXD as it is not currently in development.

2024-09-09

• Added changelog for tracking user-relevant changes.