You can host your own runners to run workflows in a highly customizable environment.
Adding self-hosted runnersYou can add a self-hosted runner to a repository, an organization, or an enterprise.
Running scripts before or after a jobScripts can automatically execute on a self-hosted runner, directly before or after a job.
Customizing the containers used by jobsYou can customize how your self-hosted runner invokes a container for a job.
Configuring the self-hosted runner application as a serviceYou can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.
Using a proxy server with self-hosted runnersYou can configure self-hosted runners to use a proxy server to communicate with GitHub.
Using labels with self-hosted runnersYou can use labels to organize your self-hosted runners based on their characteristics.
Using self-hosted runners in a workflowTo use self-hosted runners in a workflow, you can use labels or groups to specify the runner for a job.
Managing access to self-hosted runners using groupsYou can use policies to limit access to self-hosted runners that have been added to an organization.
Monitoring and troubleshooting self-hosted runnersYou can monitor your self-hosted runners to view their activity and diagnose common issues.
Removing self-hosted runnersYou can permanently remove a self-hosted runner from a repository or organization.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4