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.
If you need a self-hosted runner to communicate via a proxy server, the self-hosted runner application uses proxy configurations set in the following environment variables:
https_proxy: Proxy URL for HTTPS traffic. You can also include basic authentication credentials, if required. For example:
http_proxy: Proxy URL for HTTP traffic. You can also include basic authentication credentials, if required. For example:
no_proxy: Comma separated list of hosts that should not use a proxy. Only hostnames are allowed in
no_proxy, you cannot use IP addresses. For example:
The proxy environment variables are read when the self-hosted runner application starts, so you must set the environment variables before configuring or starting the self-hosted runner application. If your proxy configuration changes, you must restart the self-hosted runner application.
On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example
HTTPS_PROXY, the self-hosted runner application uses the lowercase environment variable.
If setting environment variables is not practical, you can set the proxy configuration variables in a file named .env in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in .env for the proxy configuration.
An example .env proxy configuration is shown below:
If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables.
For information on the required Docker configuration, see "Configure Docker to use a proxy server" in the Docker documentation.