Git and network
Git
The runner downloads the projects' code with the machine's git: install git and keep it on the
PATH.
The machine doesn't need an SSH key or a login for GitHub, GitLab, or Bitbucket. The runner uses the credentials of the git integration registered in Proton, under Settings > Integrations, and the project's repository is linked to it under Settings > Git Repository.
The downloaded code is kept in a runner folder, separated by repository, branch, and commit, and serves as a cache for later runs of the same commit.
Network
The runner's machine only makes outbound connections, over port 443 (HTTPS). It needs to reach:
| Address | What it's for |
|---|---|
app.protoncloud.com.br | Proton: the runner connection (HTTPS and WebSocket), the SDK API, uploading logs and evidence, and downloading mobile apps |
proton-runner-updates.s3.us-east-1.amazonaws.com | Proton Runner updates |
The git provider (github.com, gitlab.com, bitbucket.org, or your company's server) | The projects' code |
pypi.org and files.pythonhosted.org | The dependencies of Python projects, including the Proton Cloud SDK |
maven.protoncloud.com.br and repo.maven.apache.org | The Java Proton Cloud SDK and the other dependencies of Java projects |
| Playwright's download servers | The browser for web automations, on the first run |
| The systems the automation tests | The portal, the API, SAP |
If outbound traffic goes through a proxy or a firewall with an address allowlist, allow the addresses above and contact Atomic before installing the runner.