vRealize Automation 6.2.2 | 09 JUN 2015 | Build 2754336
VMware Identity Appliance 6.2.2 | 09 JUN 2015 | Build 2755560
Last Document Update: 09 JUN 2015
The release notes cover the following topics:
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 the following categories:
Getting Started Tab
Provides product overview and step-by-step instructions on how to set up and create a release pipeline. This informational tab addresses various questions about the vRealize Code Stream core functionality and the extensibility through tools integration such as vRealize Automation and Jenkins.
This tab is supported by the Pipeline tab that provides a reference release pipeline that has tasks set up in various stages and different environments.
Release Pipeline Modeling Enhancements
The usability enhancements simplify the following operations for Release Managers and Release Engineers:
- Drag and drop the release pipeline stages and tasks.
- Copy a task and adding it to any stage in the release pipeline.
- Share an output of one task with another task in the release pipeline.
- Cancel an on-going release pipeline execution.
Enhanced Tools Integration with vRealize Automation
The tools integration enhancements include the following new capabilities for Release Managers:
- Configure the machine blueprint custom properties during release pipeline modeling.
- Configure vRealize Automation to run in a single user mode to enable vRealize Code Stream login credentials to be used for machine provisioning.
Enhanced Tools Integration with Script
The tools integration enhancements include the following new capabilities:
- Release Managers can pass command-line arguments to scripts being invoked using the plug-in.
- The Script plug-in has a simplified user interface.
Enhanced Tools Integration with Jenkins
Release Managers can configure and invoke Jenkins build jobs using the Jenkins support available under the Custom category while modeling a release pipeline.
Users are able to collect logs from the user interface and compare release pipeline executions instances to identify what has changed.
vRealize Code Stream 1.1 includes the following product documentation.
- Installation and Configuration
- Upgrading vRealize Automation 6.2 for vRealize Code Stream 1.1
- Using vRealize Code Stream
Applying a vRealize Code Stream license from the vRealize Automation CLI is supported.
Type 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 Web browser.
- 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.
The resolved issues in the vRealize Code Stream 1.1 release:
- Embedded Artifactory server does not work when the vRealize Code Stream license is applied using vRealize Automation CLI.
- Script task does not support a stage name and a task name with space in it.
- Configuring a provisioning task results in a server error if the machine blueprint name in the IaaS has a space.
- When comparing executed release pipeline instances, the changed, deleted, and added elements that are expanded by default do not collapse.
- Expanded release pipeline executions under the Pipeline Executions tab collapse when you click Enable Auto-refresh.
- Non-ASCII characters are not supported.
- Windows 2008 and Windows 2012 systems with OpenSSH server enabled run indefinitely when a custom script PowerShell is executed with an incorrect script type.
For instructions on how to download and apply the May 2015 hot fix, see KB Article 2115166.
The known issues are grouped as follows.Upgrade
Existing artifact management configuration does not appear in a non-default tenant after upgrade.
Workaround: Reconfigure the Artifactory server from the Administration > Artifact Management tab.
- Storage volumes to support vRealize Code Stream are missing from the virtual appliance after you upgrade from vCloud Automation Center 6.1 to vRealize Automation 6.2.
Workaround: Create an external disk partition for the Artifactory server. See Using vRealize Code Stream documentation.
- Updated endpoint name does not appear in a release pipeline task that is configured using the original endpoint name.
During task configuration, a Server error message appears when an endpoint is not configured properly or has stopped working.
Workaround: Verify that the endpoint is configured properly from the Administration > Orchestration Configuration > Endpoints tab.
Renaming, editing, and moving a task to another stage causes a Task not found exception error.
Workaround: Complete the following steps to fix the error.
- Rename the task.
- Save and close the release pipeline.
- Open the release pipeline.
- Move that task to another stage.
Moving a script task from one stage to another stage that has a defined password input value causes a Last Block Incomplete in decryption error during release pipeline modeling.
Workaround: Complete the following steps to fix the script task error.
- Open the moved script task.
- Reset the password in the task.
- Save the release pipeline.
Modifying a script task name cause the release pipeline execution to fail.
Workaround: Within the release pipeline, add a wrapper to the existing script. For example, vami_ip_addr_wrapper.
Test task with a configured Jenkins server endpoint fails when the Jenkins job input parameter name includes non-English characters.
Workaround: Rename the Jenkins job in the Jenkins server and add that job to the test task in the release pipeline.
Saving a release pipeline task deleted by another user might fail with a Constraint violation exception error.
Workaround: Complete the following steps to fix the error:
- Close the release pipeline you are editing.
- Reopen the release pipeline and save as draft.
- Make any applicable edits to the release pipeline.
- Save your changes to the release pipeline.
Creating an artifact task fails with an error message.
When you create an artifact task for a release pipeline, the following error message, Unable to load plugin user interface. Error while getting response from repository appears.
Workaround: Open the Administrator > Artifact Management tab and verify that the https://vra-hostname/artifactory/ URL is defined to point to the embedded Artifactory server.
Compare view and Troubleshooting view might have rendering problems in the Firefox 33.0.5 Web browser.
Workaround: Refresh the Web browser.
User interface for collecting logs from a remote machine might not allow you to input values when a text box is highlighted with a red border accompanied with an error message.
Workaround: Wait a few seconds for the error message to disappear and add the required values.
Incorrect configuration causes an imported release pipeline execution to fail.
Workaround: Locate the failed task, reconfigure the task, and initiate a release pipeline execution.