You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering why do a self-hosted runners remove itself from the runners list after 30 days.
I work on a repo with a deployment action that is used approximatively every 3/4 month and I have to reconfigure the action runner each time.
I can understand this limitation for non self-hosted runners, but for self-hosted configured by the users they should always be up and waiting for jobs in queue.
Plus, the reconfiguration of a removed runners is really not straighforward. We need a token to use the config.sh remove script, but as the runners is removed on the github repository we have lost the runner's token.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I was wondering why do a self-hosted runners remove itself from the runners list after 30 days.
I work on a repo with a deployment action that is used approximatively every 3/4 month and I have to reconfigure the action runner each time.
I can understand this limitation for non self-hosted runners, but for self-hosted configured by the users they should always be up and waiting for jobs in queue.
Plus, the reconfiguration of a removed runners is really not straighforward. We need a
token
to use theconfig.sh remove
script, but as the runners is removed on the github repository we have lost the runner's token.Beta Was this translation helpful? Give feedback.
All reactions