Runner cleanup ability
Description
Briefly: mass-deleting runners, possibly based on last contact time.
Context: I've had a botched helm install
of Gitlab Runner, which resulted in a lot of runners being registered that do not actually exist. They have not contacted the master node for 3-24 hours, but are still in the runner list.
Proposal
Give the Admin the ability to multi-select runners for deletion, or better, give the ability to delete all runners that have not contacted the master in a given amount of time. This threshold may be user-configurable (such as "Delete all runners that have last reported more than 6 hours ago!"), or may be hardwired.
Links / references
Documentation blurb
Overview
What is it? - The ability to clean up the runner list. Why should someone use this feature? - someone botched a runner installation and is now left with multiple runners that have registered themselves but subsequently died and are not actually available. What is the underlying (business) problem? - clearing up a cluttered runner list. How do you use this feature? - either with a multi-select for the runner list, or with a button to delete all runners that have not reported in a set amount of time.
Use cases
A botched runner install results in multiple false runner registrations (the runner registers itself, but then dies and restarts, repeating the process). This clutters up the Runners list in the Admin area, and right now, there is no good way to delete runners en masse.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml