vRealize Code Stream 2.4 | 12 APRIL 2018 | Build 8229492
Check regularly for additions and updates to these release notes.
The release notes cover the following topics:
- What's New
- License Keys
- Upgrading vRealize Code Stream from earlier versions
- Support Information
- Do not enable Code Stream on an appliance that runs in High Availability mode
- Resolved Issues
- Known Issues
This release includes a number of improvements and defect fixes that improve the performance and stability of the core platform, and the integrations with vRealize Automation and Cloud Foundry.
- To help with auditing requirements, the name of approvers is now recorded in the pipeline execution results details
- Manual approvals now have an expiration date. If the approval is not granted in the time allowed, the pipeline fails.
- The plugin for vRealize Automation 7 now includes an out-of-the box action to destroy a deployment
This release fixes a number of issues on the core platform and several plug-ins:
- On the core vRealize Code Stream platform, several defects were fixed to improve overall system performance and stability
- The vRealize Automation, Jenkins, and Cloud Foundry plug-ins were improved to better handle certain action responses.
For details about these fixes, see the list of Resolved Issues in these release notes.
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.
This release of vRealize Code Stream includes the following product documentation:
- Using vRealize Code Stream (PDF)
- vRealize Code Stream Reference Architecture (PDF)
- Installing and Configuring vRealize Code Stream (PDF)
- Upgrading vRealize Code Stream (PDF)
- vRealize Code Stream Trigger for Git Guide, available at https://code.vmware.com/web/sdk/2.3.0/vrealize-code-stream
- vRealize Code Stream Trigger for Gerrit Guide, available at https://code.vmware.com/web/sdk/2.3.0/vrealize-code-stream
- Applying a vRealize Code Stream license from the vRealize Automation CLI is supported.
Run the command, /usr/sbin/vcac-vami license-update --key CodeStreamLicenseKey in the vRealize Automation CLI.
- vRealize Code Stream supports the following Web browsers:
- Internet Explorer 10.0 or later
Although vRealize Code Stream can be enabled on the same virtual appliance as vRealize Automation in lab or evaluation environments, it is not a recommended nor supported configuration for production systems, particularly when vRealize Automation is configured in High Availability (HA) mode. The current version of vRealize Code Stream does not support HA configuration, and if enabled on a vRealize Automation system in HA mode, can leave the overall system in an unpredictable state. For more information, see KB 2145084.
Fixes for security vulnerabilities
Security fixes are included for CVE-2017-5753, CVE-2017-5715 (Specter), and CVE-2017-5754 (Meltdown) vulnerabilities.
Response now includes the IP address of the container
When you provision a container in vRealize Automation 7.x, the response now includes the IP address of the container as an output of the task results.
A pipeline could not be saved when Poll task URLs included non-ASCII characters
You can now save and export a pipeline that includes Poll tasks, which have URLs that contain non-ASCII characters.
Approval IDs took a long time to generate when many approvals were open
When many open manual tasks existed, subsequent pipeline executions that used those manual tasks had to wait for several minutes for new approval IDs to be generated.
The vRealize Automation 7 plug-in did not properly support custom properties
For blueprints that have custom properties, the vRealize Automation 7 plug-in user interface now properly displays allowable values.
For a pipeline in draft state, successive attempts to save it failed
After saving a pipeline in draft state, if you deleted tasks and attempted to save the pipeline again, at times the attempt to save it failed.
Optional custom properties appeared as mandatory in vRealize Automation blueprints
When using custom properties in vRealize Automation blueprints, the vRealize Code Stream task to trigger a vRealize Automation deployment incorrectly displayed optional custom properties as mandatory.
When triggering a Jenkins job, an error appeared in the pipeline execution user interface
Triggering a Jenkins job in Jenkins 2.101 or greater displayed an error in the vRealize Code Stream pipeline execution user interface.
- From the Dashboard, you could not resume a pipeline that had a failed gating rule
From the Dashboard tab, when you resumed a pipeline that had a failed gating rule, vRealize Code Stream displayed the following error: Cannot resume execution due to insufficient context information. Failed Stage and Task details are required.
The known issues are grouped as follows.Import and Export Pipelines
- Pipeline import requests a host password
For pipelines that include a script task, after you export the pipeline, and then attempt to import the pipeline, the import displays the message Please provide host password. As a result, even though the pipeline imports, the script task changes to a warning state.
Workaround A password is not required. Instead, edit the task and save the pipeline to validate the required fields.
- Behavior when Importing Pipelines
When you import a pipeline, the task properties might no longer include password type fields. If endpoints do not exist in the vRealize Code Stream instance where you import the pipeline, vRealize Code Stream displays a warning, but the import succeeds.
- Edit the pipeline and reconfigure the tasks that are marked as invalid.
- Click Activate, then click Execute to run the pipeline.
- Differences between Pro and Open Source jFrog Artifactory
In open source Artifactories, only GAVC search is present, and the REST API used to search for artifacts does not return results for artifacts that have a '.' in the GAVC parameters. For example, if you deploy an artifact that has a group ID of com.vmware.something, and search for com.vmware.something, the search produces no results. This behavior occurs in the Artifactory user interface and through the REST APIs. As a result, this behavior affects the Artifactory plug-in.
- Task group appears as taskGroupDn instead of taskGroupCn
In the task configuration for a vRealize Orchestrator task, when you select Manual Task, the input parameters display the task group as taskGroupDn instead of taskGroupCn.
The Dn and Cn associated with the task group are insignificant. Enter the common name for the taskGroup who must receive and approve the request for the manual task. For example, enter the task group in the form of firstname.lastname@example.org or example-corp\my-team. This entry is case-sensitive.