check-circle-line exclamation-circle-line close-line

VMware vRealize Code Stream 2.4.1 Release Notes

vRealize Code Stream 2.4.1 | 20 SEP 2018 | Build 10078553

Check regularly for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release includes fixes to improve the performance and stability of the core platform.

Improvements

Code Stream will be enabled automatically with the Code Stream license only.

Defect fixes

On the core vRealize Code Stream platform, several security defects were fixed.

License Keys

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.

Documentation

This release of vRealize Code Stream includes the following product documentation:

Upgrading vRealize Code Stream from earlier versions

If you are upgrading an earlier version of vRealize Code Stream to this version, see Upgrading vRealize Code Stream.

Support Information

  • 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
    • Firefox
    • Chrome

Do not enable Code Stream on an appliance that runs in High Availability mode

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.

Known Issues

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.
    Workaround
    1. Edit the pipeline and reconfigure the tasks that are marked as invalid.
    2. Click Activate, then click Execute to run the pipeline.
    If you do not edit the pipeline and reconfigure the tasks, even if you activate and run the pipeline, it fails.
jFrog Artifactory
  • 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.
    Workaround: None
General
  • 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 my-team@example.org or example-corp\my-team. This entry is case-sensitive.