Skip to main content

​
Overview

The CircleCI integration connects your CircleCI pipelines to G360 and collects CI/CD execution data for analytics, deployment tracking, and DORA metrics reporting. With this integration, your organization can:
  • Connect CircleCI Cloud or self-hosted CircleCI Server using a CircleCI API token
  • Synchronize repository and pipeline activity
  • Configure deployment tracking
  • Enable engineering analytics and DORA metrics
The workflow is similar to the GitLab, Bitbucket, and Jenkins integrations, with CircleCI-specific authentication and endpoint configuration. Setup has three parts:
  • Connection: the CircleCI endpoint and API token.
  • Data scope: the repositories to sync from that connection.
  • Project mapping: the G360 project that uses those scopes, and its sync schedule.

​
Prerequisites

Before you start, make sure you have:
  • Access to the Engineering Metrics Dashboard
  • A CircleCI user account with access to the projects, pipelines, workflows, and jobs you want to synchronize (see Required access)
  • A CircleCI Personal API Token for that user (see Create a CircleCI Personal API Token)
  • For self-hosted CircleCI Server, the URL of your deployed server

​
Create a CircleCI Personal API Token

1

Open User Settings

Sign in to CircleCI, click your profile icon in the bottom-left corner, and select User Settings.
2

Create the token

Open Personal API Tokens and click Create New Token. Enter a descriptive name, for example G360 Integration Token, then click Add API Token.
3

Copy the token

Copy the generated token immediately and store it securely.
CircleCI displays the Personal API Token only once. If you lose it, create a new token.

​
Required access

CircleCI Personal API Tokens don’t support selecting individual scopes. The token inherits the permissions of the CircleCI user who created it. To connect CircleCI with G360, make sure that user has access to these resources:
An invalid or expired API token causes connection failures, missing repositories, and synchronization issues.

​
Create a CircleCI connection

1

Open CircleCI

In the Engineering Metrics Dashboard, go to Integration → Data Integrations Hub. Under CI/CD Integrations, find CircleCI and click Connect for a new integration, or Manage for an existing one.
2

Start a new connection

On the CircleCI Connections page, click New Connection. The Manage Connections: CircleCI window opens.
3

Enter connection details

4

Test the connection

Click Test Connection. G360 validates API endpoint accessibility, token authentication, and repository access permissions. If the test fails, see Troubleshooting.
5

Save the connection

Click Save Connection. The connection appears in the Connections panel.
By default, G360 manages API request limits automatically. CircleCI doesn’t enforce a fixed default API request limit for G360 integrations, so requests aren’t rate-limited unless your CircleCI administrator has configured a custom limit.

​
Manage existing connections

On the CircleCI Connections page, you can view, search, and select connections. To remove one, click Delete Connection at the top right.
Deleting a connection can stop synchronization for its associated repositories and projects.

​
Configure data scopes

A data scope is a repository authorized for synchronization.
1

Open Add Data Scope

Select the CircleCI connection and click Add Data Scope.
2

Select repositories

Use the search bar to find repositories. The table shows Repository Name, Organization, and Last Updated. Select one or more repositories, then click Add Scopes.
The selected repositories become available for pipeline synchronization, deployment analytics, and CI/CD reporting.

​
Scope configurations

Associate a Scope Configuration with your repository scopes. It defines:
  • Which engineering entities are collected
  • CI/CD synchronization behavior
  • Deployment stage tracking
  • DORA metrics configuration
From the connection, you can also use Associate Scope Config, Delete Data Scope, and the Actions menu on each scope.

​
DORA metrics

To enable DORA metrics, configure your deployment-related pipeline stages in the Scope Configuration, for example deploy, release, or production. G360 uses these stages to identify the deployment events behind:
  • Deployment Frequency
  • Change Failure Rate
  • Lead Time
  • Mean Time to Recovery (MTTR)
Make sure the configured deployment stages accurately represent production deployments. This keeps DORA metrics and deployment analytics reliable. Wrong stage mappings produce inaccurate DORA metrics.

​
Map the connection to a project

1

Open Projects

Go to Projects and create or edit a project.
2

Select the connection and scopes

Select the CircleCI connection and the repository scopes you need.
3

Configure synchronization

Set the synchronization behavior described in Synchronization and metrics, then complete setup.

​
Synchronization and metrics

CircleCI uses the same synchronization flow as the other integrations. After you configure it, synchronization runs automatically on the schedule you set, and pipeline and deployment data becomes available for CI/CD trend analysis and DORA metrics. Use these controls to manage synchronization:
  • Run Sync Now: immediately synchronizes the latest repository and pipeline data. Only newly available data is fetched.
  • Retransform Data: reprocesses already synchronized data into standardized formats for analytics and reporting.
  • Status: shows synchronization history, execution timestamps, task completion details, runtime duration, and success or failure information, so you can monitor and troubleshoot.
Retransform Data doesn’t collect new data. It only transforms previously collected data.

​
Troubleshooting

Possible causes
  • Invalid API token
  • Incorrect endpoint URL
  • Network restrictions
  • Proxy configuration issues
Actions
  • Verify the token is valid.
  • Confirm the endpoint is accessible.
  • Validate the proxy settings.
  • Retry the connection test.
Possible causes
  • Insufficient token permissions
  • Repository access restrictions
  • Synchronization delay
Actions
  • Verify the API token permissions.
  • Confirm the repositories are accessible to the token’s user.
  • Retry synchronization.
Possible causes
  • Pipeline processing issues
  • Invalid deployment stage mappings
  • API throttling
Actions
  • Review the synchronization logs.
  • Adjust rate limits.
  • Validate the stage configurations.
  • Retry failed synchronization tasks.

​
Best practices

  • Use organization-controlled tokens. Use organization-controlled CircleCI API tokens instead of personal user accounts, for better security, easier maintenance, and less dependency on individuals.
  • Limit repository scope. Synchronize only the repositories you need, for faster synchronization, lower API usage, and better dashboard performance.
  • Configure deployment stages carefully. Accurate stages give accurate DORA metrics and deployment analytics.
  • Monitor API usage. When you use custom rate limits, avoid excessive API requests and monitor synchronization performance to prevent CircleCI throttling.

​
Summary

After setup, your CircleCI repositories are connected to G360, pipeline and deployment data is available for analytics, you can monitor CI/CD trends, DORA metrics are available, and synchronization runs automatically on your configured schedule.