CloudBees platform for SDM changelog

CloudBees solution for software delivery management (SDM) connects the software development lifecycle with the teams, tools, and practices across the organization, enabling the visibility and collaboration to orchestrate feature idea to adoption, resulting in software delivery as a core business process.

Refer to the feature definition page for details on available features.

January 2020

New Jenkins integration

Jenkins integration lets users connect a product to an existing Jenkins master to get visibility into all the jobs and events related to that product being developed. Through the dashboard, users can see the status of last build (success/failed) and duration to understand how work is progressing or being held up.

December 2019

Enhanced user experience, new security guide

This is the second update for technical preview release of CloudBees platform for SDM to customers participating in the link: preview program.

Unified experience foundation: app.cloudbees.com

Users will have a unified sign-on to access all products their organization is subscribed to within the CloudBees suite of products, including CloudBees platform for SDM. This reduces time and confusion having to sign into multiple CloudBees products with different experiences.

The launch of https://app.cloudbees.com and the migration to HoneyUI elements provide the foundation for the unified experience.

Integration management

Integration management provides one place to easily and quickly manage all tool integrations needed to develop products and features in CloudBees platform for SDM. Users can see all tool integrations available and be able to add, remove, and maintain those integrations based on the work that needs to be done.

Updated status labels

Status labels provide an immediate indicator of issues that need attention. These labels are used on Overview and Pull requests screens.

Any repository or pull request that needs attention has a status label. These labels range from severe, such as builds failing, to minor, such as ready to merge. Each label indicates that some action is required.

New security guide details data security, architecture, source scanning

The new CloudBees platform for SDM security guide provides information about data security, system architecture, as well as integrations and security. CloudBees platform for SDM also uses WhiteSource to scan every deployment to detect and prioritize work on security issues found in open source components.

September 2019

Technical preview release

This is the first technical preview release of CloudBees platform for SDM to customers participating in the link: preview program.

Available features include:

Copyright © 2010-2019 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center and DEV@cloud are trademarks of CloudBees, Inc. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.