public_git
/
actions-runner-controller
mirror of https://github.com/actions-runner-controller/actions-runner-controller.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
actions-runner-controller/docs/adrs/2023-02-02-automate-runner-...

1.5 KiB
Raw Blame History

ADR 2023-02-02: Automate updating runner version

Date: 2023-02-02

Status: Done

Context

When a new runner version is released, new images need to be built in actions-runner-controller/releases. This is currently started by the release-runners workflow, although this only starts when the set of file containing the runner version is updated (and this is currently done manually).

Decision

We can have another workflow running on a cadence (hourly seems sensible) and checking for new runner releases, creating a PR updating RUNNER_VERSION in:

  • .github/workflows/arc-release-runners.yaml
  • Makefile
  • runner/Makefile
  • test/e2e/e2e_test.go

Once that PR is merged, the existing workflow will pick things up.

Consequences

We don't have to add an extra step to the runner release process and a direct dependency on ARC. Since images won't be built until the generated PR is merged we still have room to wait before triggering a build should there be any problems with the runner release.

Considered alternatives

We also considered firing the workflow to create the PR via repository_dispatch as part of the release process of runner itself, but we discarded it because that would have required a PAT or a GitHub app with repo scope within the Actions org and would have added a new direct dependency on the runner side.