As part of our VMware product team I’m excited to announce the availability of the new version vRealize Code Stream 2.2! This is a very important release for vRealize users and we hope that many of our customers will welcome the great benefits of the new features and improvements that we implemented in this new version of vRealize Code Stream.
Let’s get to the facts, what is new in vRealize Code Stream 2.2? Please have a look through this blog and don’t miss the opportunity to download the trial version here.
What’s New in vRealize Code Stream 2.2:
This release of vRealize Code Stream enhances platform capabilities. It extends Role-Based Access Control (RBAC) to pipeline templates, offers the ability to resume a failed pipeline execution from the point of failure, and provides support for integrating with remote jFrog Artifactory instances. It also introduces a Plug-in SDK to build custom plug-ins for vRealize Code Stream.
- Resume from Failure
This feature adds the ability to resume failed pipeline executions from the point of failure onward. Failures can occur because of transient issues such as a network outage or an issue with an external system. When you resume a pipeline after correcting the underlying issue for a failed task, the pipeline keeps the context of all previously executed tasks intact and allows the same pipeline execution to resume.An audit trail is also maintained as part of the execution metadata that highlights the resumed task(s), timestamp, and user information.You can identify the resumed pipeline executions on the Dashboard and Executions details page. You can resume a pipeline execution multiple times as long as you have permissions to trigger the resume action on that specific pipeline.
- Role-Based Access Control on Pipelines
The roles of Release Manager and Release Engineer are now extended to individual pipeline templates. You can optionally assign permissions on pipeline templates to restrict specific sets of users or groups to modify and trigger the pipeline templates.Similar to how users who have the Release Manager role can create and modify any pipeline template, when you assign a pipeline template to a set of Release Managers, the permission to modify or delete the pipeline template is only restricted to that set of Release Managers.Similarly, when you assign a pipeline template to a set of Release Engineers, only that set of Release Engineers can trigger an execution for the pipeline template. Any user that has either the Release Manager or Release Engineer role can continue to view all of the pipeline templates in the tenant. In addition to the explicit list of users who have permissions on the pipeline template, tenant administrators have the Release Manager role assigned implicitly, which allows them to rescue or clean up any pipeline template in the tenant.By default, all Release Managers can create a pipeline. When you do not add any users or groups, the following permissions are available by default:
- All vRealize Code Stream Release Managers can modify and trigger the pipeline.
- All vRealize Code Stream Release Engineers can trigger the pipeline.
- A user who has the Release Manager or Release Engineer role and Tenant Administrator role has implicit access to modify and trigger pipeline templates even when not explicitly added to the permissions list.
- Remote Artifactory Integration
This version of Code Stream supports integration with multiple remote Artifactory instances v4.7.7 or later, which allows teams to directly integrate vRealize Code Stream with their existing Artifactory instances. Teams can now independently upgrade vRealize Code Stream and Artifactory instances, and leverage advanced deployment configurations offered by Artifactory, such as for High Availability.
- Plug-in SDK
Building plug-ins is now possible through the Plug-in SDK that is available from VMware. The Plug-in SDK provides all the necessary components that you need, including examples, documentation, and the build and packaging tools to allow you to build native plug-ins for Code Stream.The Plug-in SDK leverages the widely popular open source framework from Alpaca (http://www.alpacajs.org) to build interactive user interfaces from the JSON Schema. The unique plug-in architecture of Code Stream is built on the open source framework of Xenon (https://github.com/vmware/xenon), which is built to handle operations at cloud scale.
The dashboard now displays the overall status of pipeline executions, including those that were resumed.
- Release Engineers can trigger pipelines.
- Release Managers can modify and trigger pipelines.
Other enhancements for this release include:
- Jenkins Plug-in: Added support for Jenkins Folder plug-in, which includes the ability to list and trigger Jenkins jobs organized within Jenkins sub folders.
- vRealize Automation 7.x Plug-in: Added support for configuring the blueprint deployment count as a pipeline property variable.
Information on Licensing
To use the latest version of vRealize Code Stream, you can continue to use your 2.x license key.
For more information about licenses, see the Licensing Help Center.
Additional Documentation and Information
This release of vRealize Code Stream includes the following product documentation:
- Installation and Configuration
- Upgrading vRealize Code Stream
- Using vRealize Code Stream
- Reference Architecture
Interested in more info? Please have a look to our product page. We also have a blog for our IT and developer audience.
Additionally, here are some really good videos and content to help you get started with vRealize Code Stream:
- DevOps Ready
- VMware Pipeline management with vRealize Automation and vRealize Codestream
- Blog on new version of vRealize Code Stream Management Pack for IT DevOps 2.2 (NEW)
…and of course if you have any additional questions, please contact your Vmware sales or technical representative – we are happy to provide you with any additional information on vRealize Code Stream or any other Vmware product.
We will also provide a webcast on all the news and updates of vRealize Code Stream very soon – stay tuned, we will provide the details and invitation link as an update to this blog.
Daniel Jonathan Valik, firstname.lastname@example.org, Linkedin
One comment has been added so far