Un ejecutor auto-hospedado se eliminará automáticamente de GitHub Enterprise Server si no se ha conectado a GitHub Actions por más de 30 días.įor more information about installing and using self-hosted runners, see ' Adding self-hosted runners' and ' Using self-hosted runners in a workflow.' Differences between GitHub-hosted and self-hosted runners When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs. Puedes contribuir y emitir informes de problemas en el repositorio runner. La aplicación ejecutora de GitHub Actions es de código abierto.

La máquina de tu ejecutor se conecta aGitHub Enterprise Server utilizando la aplicación para ejecutores auto-hospedados de GitHub Actions. Enterprise-level runners can be assigned to multiple organizations in an enterprise account.Organization-level runners can process jobs for multiple repositories in an organization.Repository-level runners are dedicated to a single repository.You can add self-hosted runners at various levels in the management hierarchy: Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud. With self-hosted runners, you can create custom hardware configurations that meet your needs with processing power or memory to run larger jobs, install software available on your local network, and choose an operating system. For more information about GitHub Actions, see ' Understanding GitHub Actions' and ' About GitHub Actions for enterprises.' About self-hosted runnersĪ self-hosted runner is a system that you deploy and manage to execute jobs from GitHub Actions on tu instancia de GitHub Enterprise Server. Puedes encontrar más información sobre el soporte que se tiene planeado en el futuro en el Itinerario público de GitHub. Nota: Los ejecutores hospedados en GitHub no son compatibles con GitHub Enterprise Server actualmente.

Java ver servicio de puerto conectado