Version control system integration overview

Cloud

Server

このページの内容

このページはただいま翻訳中です

When you create a CircleCI project you will select a code repository to connect. The code in the repo you select is checked out when your pipelines trigger. CircleCI supports several code version control systems (VCS). This guide gives an overview of the features available to each VCS integration.

Which version control systems are supported?

CircleCI cloud projects can be integrated with code repositories hosted on the following VCS providers:

GitHub.com
GitHub Enterprise Cloud
GitLab
GitLab self-managed
Bitbucket Cloud

Bitbucket Data Center

Bitbucket Data Center support is in closed preview. To get access, sign up here.

CircleCI server supports the following:

GitHub.com
GitHub Enterprise Cloud
GitHub Enterprise Server

Feature support for each integration type

The following tables show feature support per VCS for CircleCI cloud, along with feature support for CircleCI server.

GitHub can be integrated into your CircleCI org in one of two ways, via the GitHub App or GitHub OAuth. To see which integration type you have, navigate to CircleCI web app, select your org, select Organization Home from the sidebar, and inspect the URL in your browser:

This style of URL indicates you authenticated with the GitHub App: https://app.circleci.com/organization/circleci/UTxCZDiJ9MLGLC8hR1ZDmg
This style of URL indicates you authenticated with the GitHub OAuth app: https://app.circleci.com/pipelines/github/<your GitHub username/organization name>

Code checkout and repository integration

Feature	GitLab	GitLab Self-Managed	GitHub OAuth	Bitbucket Cloud	Bitbucket Data Center	CircleCI server
Secure HTTPS checkout
Reduced permissions when integrating with CircleCI. Select a subset of repositories to be used with CircleCI.
CircleCI config suggestions bot
Set up multiple configuration files for a project	¹	¹	¹	¹	¹	¹
GitHub Checks

¹ Possible using dynamic configuration.

Pipeline triggers and integrations

Feature	GitHub App	GitLab	GitLab Self-Managed	GitHub OAuth	Bitbucket Cloud	Bitbucket Data Center	CircleCI server
Custom inbound webhook triggers
Scheduled pipelines	²
Trigger pipelines via API
Trigger pipelines via web app
Outbound webhooks

² One alternative is to use a custom webhook to generate a URL that you curl with a 3rd party scheduling tool.

Core capabilities

Feature	GitHub App	GitLab	GitLab Self-Managed	GitHub OAuth	Bitbucket Cloud	Bitbucket Data Center	CircleCI server
Artifact storage
Test run config from VS Code
Dynamic configuration
Rerun failed tests
Orbs
Test splitting and parallelism
Docker layer caching
Debug with SSH
Auto-cancel redundant workflows
In-app config viewing and editing
Test insights
Only build pull requests

Security and permissions

Feature	GitHub App	GitLab	GitLab Self-Managed	GitHub OAuth	Bitbucket Cloud	Bitbucket Data Center	CircleCI server
OpenID Connect tokens
Config policies
Audit logs
Security group context restriction
Expression context restriction

Open source support

Feature	GitHub App	GitLab	GitLab Self-Managed	GitHub OAuth	Bitbucket	Bitbucket Data Center	CircleCI server
OSS support
Build pull requests from forked repositories
Pass secrets to builds from forked pull requests

Suggest an edit to this page

Make a contribution

Learn how to contribute

Still need help?

Ask the CircleCI community

Join the research community

Visit our Support site