Running the self-hosted runner application to connect the machine to GitHub Actions.Ĭhecking that your self-hosted runner was successfully addedĪfter completing the steps to add a self-hosted runner, the runner and its status are now listed under "Runners".For more information, see " Configuring the self-hosted runner application as a service." For Linux and macOS, you can install a service after you finish adding the runner. On Windows, the config script also asks if you would like to install the self-hosted runner application as a service.The config script requires the destination URL and an automatically-generated time-limited token to authenticate the request. Running the config script to configure the self-hosted runner application and register it with GitHub Actions.Downloading and extracting the self-hosted runner application.The instructions walk you through completing these tasks: We also recommend that you use C:\actions-runner as the directory for the self-hosted runner application so that Windows system accounts can access the runner directory. Note: On Windows, if you want to install the self-hosted runner application as a service, you must open a shell with administrator privileges. For information about how to add a self-hosted runner with the REST API, see " Actions." For an organization repository, you must be an organization owner or have admin access to the repository. To add a self-hosted runner to a user repository, you must be the repository owner. You can add self-hosted runners to a single repository. You must have access to the machine you will use as a self-hosted runner in your environment.Īdding a self-hosted runner to a repository For more information, see " Security hardening for GitHub Actions." Prerequisites You can register ephemeral runners that perform a single job before the registration is cleaned up by using just-in-time runner registration. For more information, see " Autoscaling with self-hosted runners." You can set up automation to scale the number of self-hosted runners. This is because forks of your public repository can potentially run dangerous code on your self-hosted runner machine by creating a pull request that executes the code in a workflow.įor more information, see " About self-hosted runners." Warning: We recommend that you only use self-hosted runners with private repositories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |