CloudBees changelog

Add and filter artifact versions using custom labels

(Release ID: 1.64) New feature

Attach one or more custom text labels to artifact versions and filter them based on those labels. This makes organizing, searching, and managing artifact versions easier when viewing component details.

Coordinate multiple component deployments with the application release model

(Release ID: 1.64) New feature

Coordinate the release of multiple components using the application release model. This model includes a manifest editor to specify the exact artifact versions to be deployed with a pre-configured workflow.

References:

Create multiple components in a single step

(Release ID: 1.64) New feature

Create multiple components at once, streamlining setup and saving time. This enhancement removes the previous limitation of creating components one at a time.

References:

Applications now model how your software is built

(Release ID: 1.64) New feature

Applications are a new construct in the CloudBees platform that lets you model how your software is built. Each application can connect to a source code repository, components, and environments. Applications are required to use features such as release orchestration, feature flag management, application security posture management, and more.

References:

Identify cleanup candidates with code references

(Release ID: 1.64) New feature

Use Code references to review where a feature flag appears in your codebase. This helps you assess stale or inactive flags and decide whether to clean them up, reducing technical debt.

References:

Monitor platform health with the system status indicator

(Release ID: 1.64) New feature

Check the current health of the CloudBees platform services using the new system status indicator in the UI. You can also view past incidents and subscribe to real-time updates at "cloudbees.io".

References:

Preview staged workflows to manage end-to-end releases

(Release ID: 1.64) New feature

Staged workflows—now available for preview—let you organize jobs into distinct phases for better control over end-to-end release processes. Staged workflows offer a visual composer for streamlined authoring and a runtime view that shows the current stage in execution. This preview feature will continue to evolve with new capabilities.

References:

Publish external scan results from GitHub Actions

(Release ID: 1.64) New feature

Integrate external security scanning tools such as Trivy, BlackDuck, and Coverity into your GitHub Actions workflows. Scan results can be automatically published to the CloudBees platform, enabling centralized visibility and policy enforcement across your development pipeline.

References:

Attach labels to artifact versions being published from a GitHub Action workflow

(Release ID: 1.65) Feature enhancement

The existing Register a build artifact action now accepts a new labels parameter. Use it to tag published artifact versions with one or more text labels, making it easier to organize, search, and manage artifact versions in the CloudBees Platform.

Authenticate CloudBees GitHub actions using GitHub-issued OIDC tokens

(Release ID: 1.65) Feature enhancement

Authenticate CloudBees GitHub actions using GitHub-issued OIDC tokens to eliminate PATs and enhance security. The enhanced actions are:

Manage triggers in the staged composer

(Release ID: 1.65) Feature enhancement

Manage your triggers for staged workflows in our new staged composer.

View why a job was cancelled in the UI

(Release ID: 1.65) Feature enhancement

View more explicit information about the reasons a job is cancelled for exceeding compute constraints. This provides more feedback so you can adjust your workflow or resource requests accordingly.

Navigate the platform with enhanced clarity and control

(Release ID: 1.64) Feature enhancement

This update improves platform usability with refreshed navigation elements designed for a more intuitive experience:

Introduced support for Github Actions (GHA) workflows within the platform

(Release ID: 1.63) New feature

Configure the CloudBees platform to deeply integrate with GHA. Display GHA workflows and runs in the platform UI, including test results, generated artifacts, and evidence data. In addition, you can run a CloudBees platform workflow from GHA. Use your preferred CI tools seamlessly with the CloudBees platform to increase software development efficiency and performance.

Introduced the ability to run a CloudBees platform workflow from GHA

(Release ID: 1.63) New feature

Trigger a CloudBees platform workflow from a GHA workflow run. This enables you to orchestrate your software workflows between the CloudBees platform and GHA. This action is published in the GHA marketplace.

Introduced the ability to publish an evidence item from GHA

(Release ID: 1.63) New feature

Capture job-level evidence data and publish it to the CloudBees platform. This action is published in the GHA marketplace.

Introduced the ability to publish test results to the CloudBees platform from GHA

(Release ID: 1.63) New feature

Publish test results from JUnit, Tosca, ProdPerfect, and other tools to the CloudBees platform from GHA. This action is published in the GHA marketplace.

Enhanced the action to register build artifacts from a GHA workflow

(Release ID: 1.63) Feature enhancement

Informs the CloudBees platform that an artifact version has been created, and reports build artifact data generated by a GHA workflow run. The previous version associated the given artifact to the component only, and not to the workflow run.

Added AWS ECR integration for private image use

(Release ID: 1.61) New feature

Added support for integrating the CloudBees platform with AWS Elastic Container Registry (ECR). This integration allows you to use your own private container images in workflows.

Included Github Actions information in VSM dashboards

(Release ID: 1.61) Feature enhancement

Enhanced the Software delivery activity dashboard to include workflows and workflow runs from Github Actions (including enriching drill-down views).

Strengthened OIDC token security — action may be required

(Release ID: 1.61) Feature enhancement

Enhanced the security of the OIDC token implementation to better align with industry standards. As part of this update, the documentation is improved with clearer guidance, best practices, and examples for configuring trust policies.

Action required

If you’re using OIDC tokens, take the following steps to ensure continued functionality:

References:

Notified users of a CloudBees platform GitHub App permissions update request

(Release ID: 1.60.1) New feature

Users have been notified by email that a permission update for the installed CloudBees platform GitHub App is necessary to support an upcoming feature that enables users to view GitHub Actions workflows and runs directly in the CloudBees platform.

References:

Enabled hybrid plugin support for security tools

(Release ID: 1.60) New feature

Enhance CloudBees core plugins for seamless integration with the CloudBees platform implicit security orchestration workflow. These updates allow hybrid plugins to function both as plugins and as actions within CloudBees platform. The following security tools are now available as hybrid plugins: Gosec, Trivy, Gitleaks, Grype, SonarQube, Blackduck, and Coverity.

Introduced component environment inventory view

(Release ID: 1.60) New feature

Gain visibility into where your component’s artifacts are deployed with the new component environment inventory view. This feature allows users to see which environments a particular component’s artifacts are deployed to, improving traceability and deployment insights.

Enhanced platform navigation and contextual awareness

(Release ID: 1.60) Feature enhancement

Improved the user experience with significant updates to navigation and contextual awareness, including:

Updated feature management entity inheritance behavior

(Release ID: 1.60) Feature enhancement

Maintain independent configurations in feature management. Previously, any feature management entity created in a parent organization was automatically inherited by sub-organizations. With this enhancement, inheritance has been removed, and feature management entities created in a parent organization are no longer available in a sub-organization.

Introduced action to register build artifacts from a GitHub Actions workflow

(Release ID: 1.59) New feature

Use this new action to instrument a GitHub Actions workflow and register a build artifact to CloudBees platform, enabling a workflow to deploy and track the artifact version in the environment inventory.

Can now view component environment inventory

(Release ID: 1.59) New feature

Visualize the deployed environments from a component’s artifacts with the new component environment inventory view.

Provided input parameters for manual approval jobs

(Release ID: 1.59) Feature enhancement

Provide input parameters as part of a manual approval, making the values available for use in subsequent workflow jobs.

Enhanced artifact feature with delete artifact versions

(Release ID: 1.58) Feature enhancement

Delete registered artifact versions from the component artifact list view.

Added Bitbucket Data Center metrics

(Release ID: 1.57) New feature

View all Bitbucket Data Center metrics directly on the Component summary and Software delivery activity dashboards for better visibility and tracking.

Added a conflict check for ServiceNow blackout windows

(Release ID: 1.57) New feature

Check for conflicting blackout windows before creating a change request in ServiceNow. If a blackout window exists, you can decide whether to proceed, improving control and automation in ServiceNow workflows.

Introduced reusable workflows

(Release ID: 1.57) New feature

Reuse workflows to reduce duplication, simplify maintenance, and promote best practices. Call a reusable workflow within your workflow to streamline automation.

Enabled deployment with the new Chef Client action

(Release ID: 1.56) New feature

Initiate deployments on the Chef Client application directly from a CloudBees platform workflow.

Introduced the ability to initiate a Tosca test scan from a workflow

(Release ID: 1.56) New feature

Initiate a Tosca test scan directly from a CloudBees platform workflow. The scan results are available in the workflow logs and the Test Insights dashboard, providing greater visibility and traceability.

Trigger multiple workflows with the new dispatch action

(Release ID: 1.56) New feature

Use the new dispatch-workflows action to trigger multiple workflows in parallel or sequentially from a single main workflow, with status tracking for each workflow. This feature simplifies multi-component releases by enabling a single workflow to invoke deployment workflows across components.

Enabled use of sidecar services in jobs

(Release ID: 1.56) New feature

Specify sidecar services in your workflow jobs, such as a database, memory cache, or other required services for building and testing code. Sidecar services are automatically spun up before the job starts and torn down after it completes. While the job is running, it can connect to these services and execute scripts seamlessly.

Added validation to prevent deletion of in-use custom properties

(Release ID: 1.57) Feature enhancement

Delete custom properties with built-in checks to ensure safe removal. If a property is in use, deletion is disabled, and the system alerts the user. The property must be removed from all flag configurations before deletion can proceed.

Improved deployment traceability and environment inventory

(Release ID: 1.57) Feature enhancement

Track built and deployed artifacts. A new environment inventory view shows the latest versions of artifacts in an environment with links to the jobs responsible for the deployment or build. The new artifact deployment history view shows where a particular artifact version was deployed and which version is currently active. Refer to View artifacts deployed in an environment for more information.

Released new REST API documentation

(Release ID: 1.57) Feature enhancement

Introduced new documentation for the CloudBees cloud-native platform REST API. The documentation explains how to integrate with platform data using standard HTTP methods and JSON-formatted responses, including tasks like creating and managing feature flags, target groups, and custom properties. Detailed examples and parameter tables guide you through authentication, retrieving resource IDs, and handling errors. You can automate workflows, build custom integrations, and enhance your CloudBees platform experience with these APIs. Refer to the platform API documentation for more information.

Log in to ECR across multiple regions

(Release ID: 1.56) Feature enhancement

Added support that enables users to log in to Amazon Elastic Container Registry (ECR) across multiple regions, simplifying workflows that require access to ECR repositories in different geographic locations.

Log in to an EKS cluster in a non-default region

(Release ID: 1.56) Feature enhancement

Added support that allows users to log in to an Amazon Elastic Kubernetes Service (EKS) cluster in a region other than the default. This enhancement provides greater flexibility for managing clusters across multiple regions.