Page Comparison

...

• If you are not a member of ESCP, document what you’re doing however you document things.

  • If you are a member of ESCP, document in the node.yaml file:

    Code Block
    # See https://tuftswork.atlassian.net/wiki/spaces/ESPTS/pages/499220519/Making+a+private+Github+Runner # Git Runner installed as user 'foobaruser' connected to repo [URL of github repo] # Note: This runner will die after the OS is EOL. For RHEL 8 this is May 31, 2029 # Note: This runner will die after the OS is EOL. For RHEL 9 this is May 31, 2032

• In your web browser, browse to your repository.

• Go to Settings > Actions > Runners > New Self-Hosted Runner.

• It will give you a series of commands to paste into the terminal. Instead of pasting them into the terminal, do this:

  • Find the line that says "./config.sh --url=..."

  • Get the URL and the token.

  • Read the URL to ensure it's a specific repository, not the organization or whatever.

  • Run this script as root. The script installs the runner, creates the service, and launches the service as the service account. It records the URL of which repository it's working for, in the service account's home directory under "actions-runner-url.txt":

    Code Block
    # Optionally, if you need your runner to have any custom label, you may specify --labels= /root/bin/create-gitrunner.sh username GithubRepositoryURL token [--labels=foobarlabel]

• Browse back to Actions > Runners, and confirm the new runner appears there, with a green Status, and Idle.

...