Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate external secret providers
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Understanding CloudBees CI and Jenkins® integration

2 minute read

CloudBees CI and Jenkins® integration connects existing continuous integration infrastructure to CloudBees Unify, preserving automation investments while enabling centralized governance, security scanning, and cross-tool visibility. Understanding this integration helps you leverage platform capabilities without migrating pipelines or replacing infrastructure.

The bridge between CI and unified platform

CloudBees CI and Jenkins integration extends standalone CI infrastructure by connecting it to CloudBees Unify’s unified security, analytics, and release orchestration services.

Controllers retain their existing configuration, plugins, and pipeline definitions. A lightweight plugin establishes communication with CloudBees Unify, transmitting build metadata, test results, and artifact information without affecting pipeline execution performance. This approach recognizes that enterprises have significant investments in Jenkins automation that shouldn’t be discarded.

How controllers connect to CloudBees Unify

The integration uses a secure, asynchronous communication model that preserves CI performance while enabling platform features.

Single controller integration

Single controller integration connects individual CloudBees CI or Jenkins controllers directly to CloudBees Unify. Each controller maintains its own connection with configurable permissions and visibility settings. This pattern suits standalone Jenkins instances, distributed teams, or gradual adoption scenarios.

Multi-controller integration via the operations center

Multi-controller integration uses CloudBees CI operations center to automatically discover and connect all controllers. The operations center coordinates connections and ensures consistent configuration across controllers. This pattern suits enterprises with centralized CI governance and standardized practices.

Component alignment

The repository configured as the branch source maps to a CloudBees Unify component, inheriting platform permissions and organizational boundaries. Each multibranch Pipeline maps to a workflow inside that component. This alignment enables CI data to flow naturally into security posture management, analytics, and release coordination.

Why integrate CI with CloudBees Unify

Integration transforms isolated CI infrastructure into connected components of the software delivery value stream.

Automatic security scanning

Integrated pipelines trigger CloudBees Unify’s security scanning engines without requiring scanner installation in individual pipelines. The platform normalizes findings across different scanner formats (Black Duck, Trivy, SonarQube), enabling consistent vulnerability management. Security teams assess organizational risk and track remediation through centralized dashboards.

Operations health visibility

CloudBees CI and Jenkins controllers also send operations data to CloudBees Unify, which is available in the CI insights for Jenkins dashboard, providing visibility into system health, project activity, and usage patterns.

DORA metrics contribution

Pipelines that include the registerBuildArtifactMetadata and registerDeployedArtifactMetadata steps contribute build and deploy events to DORA metrics, including deployment frequency, lead time, mean time to recovery, and change failure rate. Pre-built dashboards aggregate this data across all controllers.

Artifact traceability

The platform tracks artifact lineage from source commit through build, test, scanning, and deployment. This traceability answers critical questions: what code runs where, which vulnerabilities affect production, how changes propagate through environments.

Test intelligence

Test results flow into analytics that identify execution bottlenecks and failure patterns. Historical analysis reveals tests that frequently fail together or rarely catch real issues.

Common integration patterns

Organizations adopt integration patterns that align with their infrastructure and governance needs.

Incremental adoption starts with one team’s controller to validate value before expanding. This minimizes risk while teams learn platform capabilities.

Centralized governance integrates all controllers simultaneously through the operations center. This suits enterprises with compliance requirements or standardization initiatives.

Hybrid infrastructure connects controllers across on-premises, cloud, and hybrid environments. The platform aggregates data regardless of controller location.

Related pages

Connect CI and Jenkins controllers