Self Hosted Token

Is there a way to automate the token pull for the runner?

echo ${RUNNER_NAME:-default}$'\n\n' | ./config.sh --url ${REPO_URL} --token ${RUNNER_TOKEN}

Works, but the config.sh is interactive so this is kludgy at best.

Are there plans to make the runner name config based or flag based?

The Token seems to shift “over time” in the  UI for adding a new self hosted runner. Is there a way to automate this or generate tokens that dont expire randomly?

4 Likes

Currently looking for this feature also.

Hello :slight_smile:

Currently the only way to get a token is via the UI. Definitely agree we can make this easier on people who are registering a lot of runners. We’re working on adding API endpoints for this.

Tokens from the UI expire after 1 hour.

3 Likes

Is there a changelog I can watch for the self hosted runner package?

What about a roadmap?

1 Like

When available we will share on the change log. https://github.blog/changelog

I don’t have a date yet for when this will be shipped.

1 Like

what about for the runner versions?

I just found out that 2.161.0 came out which added arm32/arm64 support.

it would be nice to be able to subscribe to the agent versions

1 Like

Plan is to open source the runner, then you could subscribe to releases.

I’m not sure timeline on that (different team than I’m personally on). I’ll try to find out.

1 Like

Any updates? 2.162.0 is out and only noticeable if i go and look for it in the Settings  -> Actions menu

For anyone stumbling here: http://github.com/actions/runner