vRealize Code Stream 2.4.2 | 11 APR 2019 | Build 13027280
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
- Known Issues
This release includes fixes to improve the performance and stability of the core platform.
Code Stream will be enabled automatically with the Code Stream license only.
On the core vRealize Code Stream platform, several security defects were fixed.
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:
- vRealize Code Stream documentation, available at https://docs.vmware.com/en/vRealize-Code-Stream/index.html
- 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
To maintain consistency with VMware content standards, the glossary has been removed from vRealize Code Stream 2.4.2 documentation.Upgrading 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.
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 email@example.com or example-corp\my-team. This entry is case-sensitive.