![]() ![]() For more information, see " Actions." Controlling runner software updates on self-hosted runnersīy default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available. Instead, the job will remain queued until the 24 hour timeout period expires.Īlternatively, you can create ephemeral, just-in-time runners using the REST API. Note: If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. You can then create your own automation that wipes the runner after it has been de-registered. ![]() The GitHub Actions service will then automatically de-register the runner after it has processed one job. config.sh -url -token example-token -ephemeral To add an ephemeral runner to your environment, include the -ephemeral parameter when registering your runner using config.sh. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs. This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. With ephemeral runners, this can be guaranteed because GitHub only assigns one job to a runner. In certain cases, GitHub cannot guarantee that jobs are not assigned to persistent runners while they are shut down. GitHub recommends implementing autoscaling with ephemeral self-hosted runners autoscaling with persistent self-hosted runners is not recommended. GitHub recommends using actions/actions-runner-controller for autoscaling your runners.įor more information, see " About Actions Runner Controller." Using ephemeral runners for autoscaling Once the job has finished, you can then create automation that removes the runner in response to the workflow_job completed activity. The webhook payload includes label data, so you can identify the type of runner the job is requesting. For example, you can create automation that adds a new self-hosted runner each time you receive a workflow_job webhook event with the queued activity, which notifies you that a new job is ready for processing. You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |