VMware vRealize Code Stream 2.0 Release Notes

|

Updated on 14 April 2016

vRealize Automation 7.0.1 | 15 MARCH 2016 | Build 3622989

Check regularly for additions and updates to these release notes.

IMPORTANT:

While 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 release notes cover the following topics:

What's New

vRealize Code Stream is a release automation product that enables an organization to deliver quality software while leveraging existing tools in the build, development, test, provisioning, and monitoring environments. vRealize Code Stream provides features across several categories.

Parallel Task Execution

The original, workflow-based, vRealize Code Stream engine has been replaced with Xenon, an open source software, which is a newer, faster, more scalable and a more lightweight execution engine. The new execution engine supports native parallel tasks when modeling pipeline templates.The pipeline modeling canvas allows release engineers to model certain tasks to be executed in parallel along with sequential execution supported in the earlier releases. This allows faster executions and developers can get feedback to determine if a code change is ready for production.

Single Appliance Deployment

The Identity Manager is integrated within the same appliance and eliminates the need for setting it up on a separate appliance for authentication services.

Reporting Capability

vRealize Code Stream 2.0 now provides two out-of-the-box reports:

  • Pipeline Success Rate report: The Pipeline Success Rate report provides information on the Successful Vs Failed executions for a given release pipeline over time.
  • Pipeline Failure Analysis report: The Pipeline Failure Analysis report provides visibility into the top failing stages and tasks for a given release pipeline over time.

Integration Enhancements

  • In addition to Microsoft Team Foundation Server 2013, vRealize Code Stream now supports integration with Microsoft Team Foundation Server 2015 to trigger builds and jobs in TFS.

    Integration with vRealize Automation 7.0

    The integration with vRealize Automation 7.0 provides the following capabilities:

    • vRealize Code Stream now includes a new plug-in that supports converged blueprint in vRealize Automation 7.0.
    • The plugin supports triggering provisioning operations in vSphere.
    • Supports deployment of blueprints with application components.
    • Supports additional converged blueprint concepts such as multi-node deployments, network topology, and nesting of blueprints. 

Other Enhancements

The other enhancements are:

  • vRealize Code Stream now includes version 4.4 of JFrog Artifactory, which includes a completely new user interface and several new capabilities including Docker repositories and API improvements.
  • The vRealize Code Stream login page is customizable with properties such as organization logo and corporate colors.
  • Two new global pipeline execution variables are now available. These variables can be used in core pipeline logic like conditional task skipping. It can also be used in custom tasks, for example, when updating external ticketing or auditing systems:
    • ${requestBy}, which captures the username of the user who triggered a pipeline execution
    • ${executionId}, which captures the unique ID of a particular pipeline execution

License Key

You must upgrade your license key to use the latest version of the vRealize Code Stream. For more information, see Licensing Help Center.

Documentation

vRealize Code Stream 2.0 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 Internet Explorer 10.0 or later, Firefox, and Chrome Web browsers.
  • Supported command-line arguments in a release pipeline script task are primitives, constant strings, and single values.
  • Uploading log files with non-ASCII names to the Troubleshooting page is not supported.
  • Uploading log files to the Troubleshooting page when a non-ASCII user account is configured to access an Artifactory repository is not supported.
  • External vRealize Orchestrator server is not supported.
  • vRealize Code Stream provides support for Jenkins plug-in version 1.519 or later.

Resolved Issues

The resolved issues in the vRealize Code Stream 2.0 release:

  • PowerShell Script task fails if the script file name is used in the PowerShell script business logic.

Known Issues

The known issues are grouped as follows.

Upgrade
  • vRealize Code Stream roles are not reassigned to users after you migrate identity store from vRealize Automation 6.2.x to 7.0.1
    Workaround
    : Reassign user roles manually after you upgrade.
  • When you upgrade vRealize Automation from 6.2.x to 7.0.1, the Code Stream tab does not appear due to the unavailability of the tekton server and user roles
    Workaround: Check the status of the Tekton server using the command service tekton-server status. If the status is displayed as not running, start the server using the command service tekton-server start. If the Code Stream tab does not appear after the server restart, restart the vCAC server as well because the user roles are not available for vRealize Code Stream and are not assigned to the user. After you restart the server, manually assign the roles to the user and verify the roles are assigned before you search the Code Stream tab.
  • After you upgrade vRealize Automation 6.2.x to 7.0.1, the pipelines in the activated state prior to upgrade appear in draft state
    Workaround: To continue with the pipeline executions, activate all pipelines individually after you upgrade vRealize Automation.
  • The Artifactory server does not appear after you upgrade from vRealize Automation 6.2.x to 7.0.1
    Workaround: Perform the following procedure to resolve this issue:
    • Add the line host artifactory artifactory 127.0.0.1/32 md5 to the configuration file /storage/db/pgdata/pg_hba.conf.
    • Restart postgres service by running the command service vpostgres restart.
    • Restart the artifactory service using the command service artifactory restart.
    • Restart the vCAC server using the command service vcac-server restart.
  • After you upgrade vRealize Code Stream, the existing artifact management configuration does not appear in a non-default tenant
    Workaround: Reconfigure the Artifactory server from the Administration > Artifact Management tab.
vRealize Automation 7 Converged Blueprint Plug-in
  • Catalog request fails with a null value when you clone a machine blueprint with no storage attached
    Workaround: Navigate to the Advanced tab of the blueprint request configuration screen and delete the JSON node called disks in the data node of every vSphere VM in the blueprint that has no storage attached. The null value is apparent because the array inside the disks element (disks: [ ]) is empty.
  • The secure custom properties in vRA 7 blueprint is not supported. The secure properties are exposed as regular custom properties
    It is recommended not to use the secure custom properties on blueprints, which are used by vRealize Code Stream.
Plug-in Platform
  • The Jenkins task experiences an issue when binding its input properties to JSON output properties from other tasks like vRA provisioning task. The job parameter, which is a string input property does not receive a valid value when bound to JSON output property
    Workaround: When binding a JSON output property to an input property of Jenkins, the property expression should be wrapped.
    For example: Use {“machineOut”: ${stage0.vra7.machines}} as input field instead of referring ${stage0.vra7.machines}. This changes the method to access machine output to machineOut.machines[0] in place of machines[0].
Release Pipeline
  • UI elements appear magnified in Mozilla Firefox browser
    Workaround: Use the zoom in and out options available in the browser.
  • The UI element is unresponsive and the page fails to respond when you drag and drop stages in a pipeline.
    This issue occurs when you use Internet Explorer 11.
    Workaround: Refresh the page and then perform the drag and drop action.
  • When you create user or group names containing upper case characters, the Approval button gets disabled during the pipeline lifecycle
    Workaround: Create user names or group names using lower case characters.
Artifact Management
  • Configuring an Artifactory server fails with an error message
    When you configure the Artifactory server using IP address, an error message Unable to register the Artifactory server because the server is unresponsive. Contact your system administrator is displayed.
    Workaround: Configure the Artifactory server using host name instead of the IP address.
  • When you resolve an artifact using the Artifactory REST API, the API returns the HTTP path to the object instead of the HTTPs path
    Workaround
    : Navigate to Admin > Configuration > General and add HTTPS as the Custom URL Base.
  • Creating an artifact task fails with an error message
    When you create an artifact task for a release pipeline, an error message Unable to load plugin user interface. Error while getting response from repository is displayed.
    Workaround: Open the Administrator > Artifact Management tab and verify that the URL https://vra-hostname/artifactory/ points to the embedded Artifactory server.
Powershell Task
  • Powershell task fails when concurrent operations for a user exceeds the recommended value
    A few pipelines fail when you execute concurrent pipelines exceeding the maximum number. This issue occurs when the pipeline consists of powershell task. An error The WS-Management service cannot process the request. The maximum number of concurrent operations for this user has been exceeded. Close existing operations for this user, or raise the quota for this user is displayed.
    Workaround: Perform the following steps to resolve the issue:
    • Modify winrm service configuration to set a higher value for MaxShellsPerUser. The recommended value is 500 for 50 concurrent pipelines with 5 powershell tasks for each pipeline.
    • Run the command winrm set winrm/config/winrs '@{MaxShellsPerUser="7"}'.
    • Verify the configuration by running the command winrm get winrm/config.
    • Restart the winrm service.
  • Powershell task might fail to respond due to memory constraint on winrm service
    When you execute concurrent pipelines, which has powershell task, a few of the pipelines might fail during execution.
    Workaround: Use the following steps to resolve this issue:
    • Modify winrm service configuration to set a higher value for MaxMemoryPerShellMB. The recommended value is 2048.
    • Run the command winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="2048"}'
    • Verify the configuration by running the command winrm get winrm/config.
    • Restart the winrm service.