CloudBees Unify technical requirements

Supported SCM providers

GitHub and Bitbucket (cloud or enterprise) are supported. An SCM integration is essential for most features, including analytics, security scanning, and release orchestration. Learn more at SCM integrations.

Private network access

If your SCM, Jenkins®, artifact registry, or deployment environments are private, utilize a single-tenant CloudBees Unify deployment to establish a secure private connection.

CloudBees Unify Edition

Feature availability varies by subscription edition:

Component creation

Many features depend on defining components to represent applications and services. Components link to SCM and track builds, deployments, and security posture.

CloudBees workflows

Define automation across build, test, deploy, and release stages. Required for:

Jenkins® integration

Required to:

Learn more at CI tools integration.

CloudBees CI plugin

Connect Jenkins to Unify by installing the CloudBees CI Insights plugin, and using the authentication token generated during Jenkins integration configuration.

GitHub Actions support

CloudBees offers reusable GitHub Actions for analytics, such as publishing test results.

Use these actions to populate analytics dashboards from GitHub workflows.

Issue tracking (Jira)

Required for flow metrics, including lead time, cycle time, and WIP. Ensure Jira issues are mapped to software delivery states in a CloudBees Unify analytics project. Learn more at Project management integration.

Continuous security

(if SCM or security tools are private)

(Jenkins support coming)

Optional (to enrich data)

DevOps analytics

(if Jenkins is private)

(for CI Insights and test results)

(for DORA, test insights)

(for flow metrics)

Release orchestration

(if SCM, Jenkins, or environments are private)

(Optional)

(Required)