Network

This page covers network-related configuration that may be needed when integrating Tuist with your infrastructure.

Outbound IP addresses#

If your infrastructure restricts inbound traffic by IP address, you may need to allowlist the IP ranges used by Tuist. This is common when Tuist needs to communicate with services behind a firewall or VPN, such as self-hosted Git providers or artifact storage, or when your GitHub organization uses IP allow lists.

Allowlist the server addresses for Tuist integrations and the runner addresses for each platform your workflows use.

Server IP addresses#

Allowlist both addresses for connections from Tuist services and integrations:

Tuist only connects to your infrastructure over HTTPS, so you only need to allow HTTPS traffic (TCP port 443, or the port your HTTPS endpoint listens on) from these addresses. Tuist does not need SSH access.

Tuist Runners#

Jobs that run on Tuist Runners use the outbound addresses below. If a job needs to reach infrastructure that restricts traffic by IP address, for example to check out a repository from a GitHub organization with an IP allow list, allowlist the addresses or ranges for every platform your workflows run on.

macOS#

Allowlist the following ranges for macOS runner jobs:

Linux#

Allowlist the entire range for Linux runner jobs: