CloudBees SDM changelog
CloudBees 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.
CloudBees SDM uses the DevOptics plugin for Jenkins integration. For information about the latest updates to the DevOptics plugin used with CloudBees SDM, see the DevOptics plugin release notes.
Jira Server integration
Jira Server integration allows users to link Jira Server projects to associated products, and, through the product Overview, get visibility into all tickets and related data, through queries and reports, enabling more efficient prioritizing and tracking of all work related to those projects.
You can now create a refresh token in the CloudBees SDM UI. A refresh token is a long-lived token used to securely fetch a short-lived access token which can be used to connect to the CloudBees SDM API.
Personal access tokens
You can now create a personal access token in the CloudBees SDM UI. A personal access token is a long-lived token that can be used by scripts and applications to make authenticated requests on behalf of a user.
New developer guide provides information on how to extend CloudBees SDM with apps
The new Developer guide provides information about app manifest, types, data, and relationships as well as app authentication.
GitHub Enterprise integration
CloudBees SDM can use data from GitHub (GitHub.com) and now GitHub Enterprise (on-premises version of GitHub.com) to highlight blocked pull requests, failed tests, and more. Data received from GitHub and GitHub Enterprise is stored in the System of Record and available in CloudBees SDM.
Basic role-based access control
Basic role-based access control (RBAC) allows for two types of users:
Users will be able to use all the data being collected by CloudBees SDM by accessing a number of standard reports related to efficiency, contribution, development status, and health. Additionally, users can create custom reports to query the data and answer questions related to the entire software delivery process.
Policy engine enables engineering managers and leaders to define rules related to the development process of a product or feature. Rules can enforce specific steps that drive best practices, compliance or governance requirements for the process, which help ensure higher quality, more stable software for the customer.
Jira Cloud integration allows users to link Jira cloud projects to associated products, and get visibility into all tickets and related data, enabling more efficient prioritization and tracking of all work related to those projects.
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. Through the dashboard, users can see the status of the last build (success/failed) and the duration to understand how work is progressing or being held up.
This is the second update for the preview release of CloudBees 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.
Managing integrations provides one place to easily and quickly manage all tool integrations needed to develop products and features in CloudBees 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 SDM security guide provides information about data security, system architecture, as well as integrations and security. CloudBees SDM also uses WhiteSource to scan every deployment to detect and prioritize work on security issues found in open source components.
This is the first preview release of CloudBees SDM to customers participating in the link: preview program.
Available features include: