Self-hosted Git
AppArch has no generic “custom Git” connection: no SSH-key credential, no plain clone URL, no Gitea or Gerrit support.
What is supported
Section titled “What is supported”The only self-hosted Git server AppArch can connect to is a self-managed GitLab (Community or Enterprise Edition):
- Credentials → Add credential → GitLab.
- Choose Self-hosted and enter the instance URL, e.g.
https://gitlab.acme.com(no trailing path). - Continue with an OAuth application or a personal access token, exactly as for gitlab.com - see GitLab.
Every GitLab endpoint AppArch uses is derived from that URL, so the Api must be able to reach your GitLab over HTTPS (or HTTP).
What is not supported
Section titled “What is not supported”| Server | Status |
|---|---|
| GitHub Enterprise Server | Not supported - GitHub is github.com only |
| Bitbucket Data Center / Server | Not supported - Bitbucket is Cloud only |
| Azure DevOps Server (TFS) | Not supported - Azure DevOps is dev.azure.com only |
| Gitea, Gerrit, plain SSH / HTTPS remotes | Not supported |
Air-gapped networks
Section titled “Air-gapped networks”The runner analyses the code inside your CI and sends results only to your own AppArch installation, at the address set in APPARCH_Collector__ApiUrl. With a self-managed GitLab on the same network, nothing has to leave it.