Skip to main content

This version of GitHub Enterprise Server was discontinued on 2023-09-25. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

High availability for GitHub Actions

There are some special considerations for administering GitHub Actions in a high availability configuration.

Replication or redundancy of your GitHub Actions data

GitHub Actions uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, GitHub Enterprise Server backups and GitHub Enterprise Server high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS.

We strongly recommend that you configure your GitHub Actions external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation:

High availability replicas

Promoting a replica

When enabling a high availability configuration, any replicas are automatically configured to use the GitHub Actions external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for GitHub Actions.

For more information, see "Initiating a failover to your replica appliance."

Removing a high availability replica

Avoid letting multiple instances to write to the same GitHub Actions external storage. This could occur when using the ghe-repl-teardown command to stop and permanently remove a GitHub Actions-enabled replica. This is because the replica will be converted into a standalone GitHub Enterprise Server, and after the teardown it will still use the same external storage configuration as the primary.

To help avoid this issue, we recommend either decommissioning the replica server or updating its GitHub Actions configuration with different external storage.