Native CI Integration


Native CI Integration

Who needs it?

Developers, applications owners, and DevOps tools teams who set up release pipelines expect a seamless integration between CloudBees products to speed pipeline creation and eliminate errors stemming from manual input.

Release managers who care about release pipeline status, health, and history need a complete, single view of the end to end release process - from code commit to production.

Auditors (and release managers) need to be able to quickly produce detailed audit reports of the entire release pipeline, including CloudBees CI builds, often from months in the past.

The problem

While a Jenkins/CloudBees CI plugin has been available for many years, the integration was not seamless. Build and task data was not persisted into CloudBees CD/RO. CloudBees CI log data is commonly not kept for long; this made it difficult to produce audit reports - often requiring developers to stop coding to help recreate logs of past builds.

In addition, since the plugin was not tightly integrated it required extra time to go back and forth between CloudBees CI and CloudBees CD/RO to copy/paste job names and parameters. If a user made a typo, this would only be detected at runtime, causing the need to troubleshoot and retest the step.

This leads to two problems: 1) a disappointing experience using two products from the same company (for users), and, 2) unnecessary waste, errors, and delays for architects, release managers, and CIOs.

CloudBees can help

Every company wants to optimize their software delivery processes. By natively integrating CloudBees CI and CloudBees CD/RO, CloudBees helps eliminate the waste of slow release pipeline development, manually introduced errors, and interrupting developers to comply with an audit request.

The solution

Native CloudBees CI Integration now treats CloudBees CI builds, tasks, and data as first-class citizens within CloudBees CD/RO.

CloudBees CI (and Jenkins OSS) build data is now automatically pushed to CloudBees CD/RO when triggering a release or pipeline. This data is persisted in CloudBees CD/RO and viewed from the pipeline run. The new integration automatically creates a relationship between the build and a CloudBees CD/RO pipeline or release, and the CloudBees CI build data is persisted and available from the CloudBees CD/RO pipeline. Calling CloudBees CI is now a native pipeline task in CloudBees CD/RO where job data and parameters from CloudBees CI are automatically populated into CloudBees CD/RO.

This allows users to quickly integrate CloudBees CI builds and tasks into their CloudBees CD/RO pipelines and eliminates the errors caused by manual steps. Managers now have end-to-end visibility of their audit-ready release pipelines.

How we do it better

Though many continuous delivery and release automation vendors support Jenkins and CloudBees CI via plugins, having CloudBees CI tasks natively populated into the CloudBees CD/RO release pipeline and persist related CloudBees CI data into CloudBees CD/RO for analysis, reporting, and auditing is unique.