Version control systems, pipeline types, and feature support

Cloud Server

CircleCI supports various pipeline types which map directly to the version control system (VCS) in which your code is stored, and the method used by CircleCI to get your code. Pipeline types are indicated with badges in the CircleCI web app, and the options are as follows:

GitHub App
GitHub OAuth
GitHub OAuth (Server)
GitLab
GitLab Self-manages
Bitbucket
Bitbucket Data Center

This guide provides an overview of the VCS options, organization types and pipeline types supported by CircleCI and the features available to each..

Which version control systems are supported?

CircleCI Cloud pipelines 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

CircleCI Server supports the following:

GitHub.com
GitHub Enterprise Cloud
GitHub Enterprise Server

Which organization types support which VCS providers?

For a full guide to organization types, see the Users, Organizations, and Integrations Guide.

circleci type organizations can be integrated with:

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

github type organizations can be integrated with:

GitHub.com
GitHub Enterprise Cloud

bitbucket type organizations can be integrated with:

Bitbucket Cloud

If you are using CircleCI Server you are using a github type organization.

Feature support for each pipeline type

The following table shows feature support for each pipeline type.

Features that are supported for a pipeline type are indicated with Yes.
Features that are not supported for a pipeline type are indicated with No.

For an overview of users, orgs, and pipeline types, see the Users, Organizations, and Integrations Guide.

The table below is not a full list of CircleCI features. Only features where the pipeline type is relevant to support are included. If a feature is not in this table, it is supported for all pipeline types.

Feature Category GitHub App GitHub OAuth GitHub OAuth on Server GitLab.com GitLab self-managed Bitbucket Cloud Bitbucket Data Center

Feature	Category	GitHub App	GitHub OAuth	GitHub OAuth on Server	GitLab.com	GitLab self-managed	Bitbucket Cloud	Bitbucket Data Center
The method used to check out your code when using the `checkout` step in your configuration file. See more in the Configuration Reference.	Code checkout	HTTPS	SSH	SSH	SSH	SSH	SSH	SSH
Deploy key required for code checkout. See the Users, Organizations, and Integrations guide for more information.	Code checkout	No	Yes	Yes	No	No	Yes	No
Fine-grained permissions when integrating with CircleCI. Select a subset of repositories to be used with CircleCI.	Security	Yes	No	No	No	No	No	Yes
Custom configuration file path. If No then CircleCI config is stored at `.circleci/config.yml` in the repository.	Configuration	Yes	No	No	Yes	Yes	No	Yes
Centralized configuration management and job overrides. Read more in the How to Override Config guide.	Configuration	Yes	No	No	No	No	No	No
Test Run Config From VS Code	Configuration	No	Yes	Yes	No	No	Yes	No
View your configuration file in the CircleCI web app	Configuration	Yes	Yes	Yes	No	No	Yes	No
Edit your configuration file in the CircleCI web app	Configuration	No	Yes	Yes	No	No	Yes	No
GitHub Checks to track the status of your pipeline in the GitHub UI	Notifications	Yes	Yes	Yes	No	No	No	No
Outbound Webhooks. Send real-time information about your pipelines to external services. Payload varies depending on pipeline type.	Notifications	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Cross-repo pipeline and trigger setups	Triggers	Yes	No	No	No	No	No	No
Custom Webhook Triggers. Trigger pipelines from external services.	Triggers	Yes	No	No	No	No	No	No
Schedule Triggers. Trigger pipelines based on a schedule.	Triggers	Yes	Yes	No	No	No	Yes	No
Scheduled Workflows. Schedules defined in the `config.yml` file.	Triggers	No	Yes	Yes	No	No	Yes	No
API Triggers. Trigger pipelines via the API.	Triggers	Yes	Yes	Yes	No	No	Yes	Yes
UI Triggers. Trigger pipelines via the CircleCI web app.	Triggers	Yes	Yes	Yes	No	No	Yes	No
Pull request event triggers. See more in the Triggers Overview	Triggers	Yes	No	No	Yes	Yes	No	No
Only build on push to pull/merge requests. See more in the Open Source Support guide	Triggers	Yes	Yes	Yes	Yes	Yes	Yes	No
Rerun Failed Tests.	Testing	Yes	Yes	No	Yes	Yes	Yes	Yes
Use Deploy Markers to track deployments in the CircleCI web app	Deployment	Yes	Yes	Yes	Yes	Yes	Yes	No
Set up Rollback Pipelines to manually revert your application to a previous stable version directly from the CircleCI web app	Deployment	Yes	Yes	No	No	No	No	No
Set up Deploy Pipelines to automatically deploy your application to a target environment directly from the CircleCI web app	Deployment	Yes	Yes	No	No	No	No	No
Build Pull Requests From Forked Repositories	Open source support	No	Yes	Yes	Yes	No	Yes	No
Pass Secrets to Builds From Forked Pull Requests	Open source support	No	Yes	Yes	Yes	No	Yes	No
Chunk, CircleCI’s AI CI/CD agent. Learn more in the Chunk Setup Guide	Agentic support	Yes	Yes with GitHub App installed	No	No	No	No	No

The method used to check out your code when using the checkout step in your configuration file. See more in the Configuration Reference.

Code checkout

HTTPS

SSH

Deploy key required for code checkout. See the Users, Organizations, and Integrations guide for more information.

Code checkout

Yes

Fine-grained permissions when integrating with CircleCI. Select a subset of repositories to be used with CircleCI.

Security

Yes

Custom configuration file path. If No then CircleCI config is stored at .circleci/config.yml in the repository.

Configuration

Yes

Centralized configuration management and job overrides. Read more in the How to Override Config guide.

Configuration

Yes

Test Run Config From VS Code

Configuration

Yes

View your configuration file in the CircleCI web app

Configuration

Yes

Edit your configuration file in the CircleCI web app

Configuration

Yes

GitHub Checks to track the status of your pipeline in the GitHub UI

Notifications

Yes

Outbound Webhooks. Send real-time information about your pipelines to external services. Payload varies depending on pipeline type.

Notifications

Yes

Cross-repo pipeline and trigger setups

Triggers

Yes

Custom Webhook Triggers. Trigger pipelines from external services.

Triggers

Yes

Schedule Triggers. Trigger pipelines based on a schedule.

Triggers

Yes

Scheduled Workflows. Schedules defined in the config.yml file.

Triggers

Yes

API Triggers. Trigger pipelines via the API.

Triggers

Yes

UI Triggers. Trigger pipelines via the CircleCI web app.

Triggers

Yes

Pull request event triggers. See more in the Triggers Overview

Triggers

Yes

Only build on push to pull/merge requests. See more in the Open Source Support guide

Triggers

Yes

Rerun Failed Tests.

Testing

Yes

Use Deploy Markers to track deployments in the CircleCI web app

Deployment

Yes

Set up Rollback Pipelines to manually revert your application to a previous stable version directly from the CircleCI web app

Deployment

Yes

Set up Deploy Pipelines to automatically deploy your application to a target environment directly from the CircleCI web app

Deployment

Yes

Build Pull Requests From Forked Repositories

Open source support

Yes

Pass Secrets to Builds From Forked Pull Requests

Open source support

Yes

Chunk, CircleCI’s AI CI/CD agent. Learn more in the Chunk Setup Guide

Agentic support

Yes

Yes with GitHub App installed

Feature support for each organization type

The following table shows feature support for each organization type. This list does not include all CircleCI features. Only features where the organization type is relevant are included.

For a guide to organization types, see the Users, Organizations, and Integrations Guide.

Feature	GitHub	Bitbucket	CircleCI
Test Insights. View insights into your test performance.	Yes	Yes	No
Security Group Context Restriction. Restrict the use of contexts to specific users and groups.	Yes	No	No
User management and permissions system within CircleCI including: Roles, Groups, SSO, MFA. See the Roles and Permissions Overview for more information.	No	No	Yes
Project creation process.	Imported from VCS	Imported from VCS	Manual
Multiple projects to track a single monorepo.	No	No	Yes
Set up Multiple Pipelines and Configuration Files for a Project	Yes	No	Yes

Feature

GitHub

Bitbucket

CircleCI

Test Insights. View insights into your test performance.

Yes

Security Group Context Restriction. Restrict the use of contexts to specific users and groups.

Yes

User management and permissions system within CircleCI including: Roles, Groups, SSO, MFA. See the Roles and Permissions Overview for more information.

Yes

Project creation process.

Imported from VCS

Manual

Multiple projects to track a single monorepo.

Yes

Set up Multiple Pipelines and Configuration Files for a Project

Yes

[path]

[title]

Version control systems, pipeline types, and feature support

Which version control systems are supported?

Which organization types support which VCS providers?

Feature support for each pipeline type

Feature support for each organization type