Integrating Source Control Platforms

OX supports App, Webhook, and Direct CI/CD methods for integrating with your source control system. These methods are not mutually exclusive; you can combine them.

Required scopes and permissions for each source control integration are described in their respective configuration guides.

Comparison of Integration Methods

Method	Pros	Considerations
GitHub App and Bitbucket App	Minimal setup per repo, UI-based control	Available only for supported platforms (GitHub, Bitbucket).
Direct CI/CD	Full customization per repo	Requires configuring and maintaining YAML file in each repository. Setup can be more complex and requires familiarity with YAML syntax.
Webhook	Centralized setup, easy to apply at scale	Less flexible than per-repo YAML.

OX integrates with the following source control platforms:

• App

  • GitHub App

  • Bitbucket App

• Webhooks

  • GitLab Webhooks

• Direct CI/CD

  • GitHub Actions

  • GitLab CI/CD

  • Bitbucket Pipelines

  • Jenkins

  • Azure Pipelines and Azure DevOps

Configuring SaaS and On-Prem source control platforms

All source control systems operate both as Software as a Service (SaaS) and on-premises solutions, with the exception of Gerrit, which only functions as an on-prem solution.

To configure your source control system on-premises, it must meet the following requirements:

• Whitelist IPs for OX connection.

• OX_HOST_URL: https://your.onprem.url/

• For OX Broker, you need to whitelist outgoing traffic to OX IPs.