Platform integrations connect CloudBees Unify to your existing enterprise infrastructure, enabling streamlined workflows, unified visibility, and automated data flow across your development toolchain. Rather than replacing your trusted tools, integrations allow CloudBees Unify to orchestrate and enhance your current investments in CI/CD platforms, source code management systems, container registries, and enterprise applications.
Integrations serve three primary functions: collecting data from external systems for analytics and reporting, triggering automated workflows based on external events, and providing authenticated access to external resources during workflow execution. This connectivity transforms CloudBees Unify from an isolated platform into the central orchestration layer for your entire software delivery lifecycle.
Integration categories
Understanding the different types of integrations helps you design an integration architecture that matches your organization’s needs and existing tool landscape.
CI/CD platform integrations
CI/CD integrations serve two distinct purposes that require different configuration approaches.
Build and test data collection integrates individual Jenkins controllers or operations centers to visualize jobs, builds, test results, and artifacts within CloudBees Unify. This integration enables unified monitoring across multiple CI/CD environments and provides the foundation for deployment orchestration.
Analytics insights collection connects CI/CD platforms specifically to gather performance metrics and build data for the CI insights dashboard. This integration focuses on data extraction for reporting rather than operational control.
The choice between single controller and operations center integration depends on your Jenkins architecture. Operations center integration automatically discovers and connects multiple controllers, while single controller integration provides granular control over individual environments.
To configure CI/CD integrations, refer to Configure CI/CD integrations.
Source code management (SCM) integrations
SCM integrations enable repository discovery, webhook configuration, and source code access during workflow execution. These integrations support both cloud-hosted platforms (GitHub, GitLab Cloud, Bitbucket Cloud) and self-managed instances (Bitbucket Data Center, GitLab self-managed, Gerrit).
Each SCM platform uses different authentication mechanisms optimized for their security model. GitHub uses a CloudBees-managed GitHub App that provides granular permissions and automatic updates. GitLab and Bitbucket rely on personal access tokens with configurable scopes. Gerrit uses basic authentication with username and password credentials.
SCM integrations create the foundation for automated workflows by establishing webhook triggers and providing authenticated access to source repositories during pipeline execution.
To configure source code management integrations, refer to Configure source code management.
Container and artifact registry integrations
Container registry integrations serve two primary patterns: security scanning triggers and registry mirroring for performance optimization.
Security scanning integration automatically triggers vulnerability analysis when artifacts are published to connected registries like AWS ECR or JFrog Artifactory. This pattern enables continuous security monitoring without requiring manual scan initiation.
Registry mirroring caches Docker images locally to avoid external registry rate limits and improve build reliability. This integration transparently redirects image pulls to your configured mirrors while maintaining fallback to original registries.
Enterprise registries typically require authentication and may involve complex network configurations, while public cloud registries often integrate through IAM roles and service accounts.
To configure container registry integrations, refer to Configure container registries.
Project management integrations
Project management integration links development work to business initiatives by connecting Jira tickets to flow metrics and deployment tracking. This enables traceability from requirements through deployment and provides data for business reporting on development velocity.
To configure project management integrations, refer to Configure project management integrations.
Organizational scoping and inheritance
Integrations are scoped to the organization where they are created, giving them access to that organization’s environments, components, and resources. Child organizations automatically inherit integrations from their parent organizations, following CloudBees Unify inheritance rules.
This hierarchy enables centralized integration management while allowing organizational autonomy. For example, a platform team can establish organization-wide SCM and registry integrations at the root organization, while individual development teams create project-specific integrations at the team level.
Consider creating integrations at higher organizational levels when they serve multiple teams, and at lower levels when they contain team-specific credentials or configurations.