Warning: Self-hosted runners are currently disabled for GitHub AE. This is because GitHub AE offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with GitHub AE and understand the security implications, you can contact GitHub support for a security exception that will enable self-hosted runners.
If you don't need self-hosted runners, then you can use AE hosted runners to run your workflows. For more information, see "About AE hosted runners."
Note: GitHub Actions is currently in beta for GitHub AE.
- About self-hosted runners
- Adding self-hosted runners
- Configuring the self-hosted runner application as a service
- Using a proxy server with self-hosted runners
- Using labels with self-hosted runners
- Using self-hosted runners in a workflow
- Managing access to self-hosted runners using groups
- Monitoring and troubleshooting self-hosted runners
- Removing self-hosted runners