Communicating with self-hosted runners

A self-hosted runner connects to GitHub Enterprise Server 인스턴스 to receive job assignments and to download new versions of the runner application. The self-hosted runner uses an HTTP(S) long poll that opens a connection to GitHub for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run GitHub Actions jobs.

GitHub Actions 실행기 애플리케이션이 오픈 소스입니다. 실행기 리포지토리에서 기여하고 문제를 제출할 수 있습니다. When a new version is released, the runner application will automatically update within 24 hours.

14일 넘게 GitHub Actions에 연결되지 않은 경우 자체 호스트 실행기는 GitHub에서 자동으로 제거됩니다. 1일 넘게 GitHub Actions에 연결되지 않은 경우 임시 자체 호스트 실행기는 GitHub에서 자동으로 제거됩니다.

자체 호스트 실행기와 GitHub 간의 연결은 HTTP(포트 80) 또는 HTTPS(포트 443)를 초과합니다. HTTPS를 통한 연결을 보장하려면 GitHub Enterprise Server에 대한 TLS를 구성합니다. 자세한 내용은 TLS 구성을(를) 참조하세요.

Only an outbound connection from the runner to GitHub Enterprise Server is required. There is no need for an inbound connection from GitHub Enterprise Server to the runner. For caching to work, the runner must be able to communicate with the blob storage and directly download content from it.

GitHub Enterprise Server must accept inbound connections from your runners over HTTP(S) at GitHub Enterprise Server 인스턴스's hostname and API subdomain, and your runners must allow outbound connections over HTTP(S) to GitHub Enterprise Server 인스턴스's hostname and API subdomain.

Self-hosted runners do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and GitHub Enterprise Server. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to GitHub Enterprise Server, with no need for traffic to traverse a public network.

Communication between self-hosted runners and GitHub.com

Self-hosted runners do not need to connect to GitHub.com unless you have enabled automatic access to GitHub.com actions for GitHub Enterprise Server. For more information, see 엔터프라이즈에서 작업 사용 정보.

If you have enabled automatic access to GitHub.com actions, then the self-hosted runner will connect directly to GitHub.com to download actions. You must ensure that the machine has the appropriate network access to communicate with the GitHub URLs listed below.

github.com
api.github.com
codeload.github.com
pkg.actions.githubusercontent.com

github.com
api.github.com
codeload.github.com
pkg.actions.githubusercontent.com

Further reading

• 자체 호스트형 실행기를 사용하는 프록시 서버 사용
• 자체 호스트형 실행기 모니터링 및 문제 해결