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

Updated on: 28 JULY 2017

vRealize Code Stream 2.3 | 16 MAY 2017 | Build 6158087

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 of vRealize Code Stream simplifies licensing to enable DevOps for IT use cases, and entitles vRealize Suite Enterprise and vRealize Automation users to use the vRealize Code Stream Management Pack for IT DevOps without separate vRealize Code Stream licenses. This release also supports developer use cases involving Git and Gerrit through utilities that can trigger pipeline executions. Additionally, this release includes new plug-ins which integrate with external systems over REST APIs, and includes other minor enhancements to the user interface.


You can now use your vRealize Automation license to enable vRealize Code Stream for your vRealize Automation environments. The vRealize Automation license allows you to unlock vRealize Code Stream so that you can use it with the vRealize Code Stream Management Pack for IT DevOps.

To enable vRealize Code Stream, you must have either vRealize Suite Enterprise, vRealize Automation Advanced, or vRealize Automation Enterprise, and a new license for vRealize Automation 7.3. 

You must install the vRealize Code Stream Management Pack on a separate and dedicated appliance that has vRealize Automation and vRealize Code Stream enabled in a non-HA (High Availability) mode. For more information, see the vRealize Code Stream Reference Architecture Guide. You cannot install the vRealize Code Stream Management Pack on your existing vRealize Automation production instance for the following reasons:
  • The extra load might negatively impact the performance of your vRealize Automation production instance.
  • vRealize Code Stream does not support installation on an appliance that is configured for HA. Do not enable vRealize Code Stream on a vRealize Automation instance that is in HA mode. If you do, your vRealize Automation environment might become unstable.

For more information, see the vRealize Code Stream Information Center.

Pipeline Triggering Utilities for Git and Gerrit

Pipeline executions can be triggered based on Git and Gerrit events by using the easy-to-setup command line utilities. For more information, see the vRealize Code Stream Information Center.


  • Generic REST plugin: Pipeline tasks can be modeled to interact with any external system with REST APIs. It supports all standard HTTP methods such as GET and POST. The plug-in also supports parsing JSON responses to bind specific parts of the JSON response in subsequent tasks.
  • Poll Plugin: Pipeline tasks can be modeled to wait on an external system’s REST API for status change. Apart from supporting success and failure criteria, you can configure timeout and periodicity.

Pipeline Import and Export

With the pipeline import and export selections, you can import and export pipeline templates directly from the user interface. You can use the import and export selections to easily create backups of pipeline templates on the local system, and to restore them.

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.


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

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

Patches for vRealize Code Stream Management Pack for IT DevOps 2.2.1

Apply these patches to enable support of vRealize Code Stream in vRealize Automation 7.3 when you use a license key for vRealize Suite 7 Advanced or Enterprise, or vRealize Suite 2017 Advanced.

You can obtain these patches from MyVMware or from another location, then download them to your vRealize Automation appliance. Applying these patches restarts the vcac-server service.

To download the RPM files from MyVMware: 

  1. From your vRealize Automation appliance, log in to your MyVMware account.
  2. On the Download Product page for VMware Realize Code Stream Management Pack for IT DevOps 2.2.1, on the Product Downloads tab, locate the patches.
  3. For the patch named vRealize Automation 7.3 license keys patch, click Download Now.
  4. Run the command: rpm –U --force <vcac->
  5. For the patch named vRealize Automation 7.3 VAMI Licensing Wizard and Licensing tab patch, click Download Now.
  6. Run the command: rpm –U --force <vmware-studio-vami-service-cafe->

To download the RPM file from another location: 

  1. Obtain the patch by using the command format: wget –no-check-certificates <URL of RPM file>
  2. Upload the RPM into the vRealize Automation virtual appliance.
  3. On your virtual appliance, run the command: “rpm –U --force <vcac->”

To verify that the patch is corrrectly applied:

  1. Login in to the vRealize Automation Virtual Appliance Management Interface (VAMI).
  2. After the download completes, reload the vRealize Automation 7.3 Virtual Appliance Management Interface (VAMI) to load the new content.
  3. Click Services and verify that the status of the vRealize Automation services, including the service named vcac-server, are REGISTERED.

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.

Resolved Issues

  • 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.

Known Issues

The known issues are grouped as follows.

  • Upgrading vRealize Code Stream from earlier versions
    If you are upgrading an earlier version of vRealize Code Stream to this version, see the previous version of release notes.
Import and Export Pipelines
  • 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.
    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.
  • 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.
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