vRealize Automation 6.2.3 | 01 OCT 2015 | Build 3093004
VMware Identity Appliance 6.2.3 | 01 OCT 2015 | Build 3011559
Last Document Update: 15 MARCH 2016
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:
Conditional Task Execution
Release Managers can apply conditions to tasks to run special tests such as, performance tests and send notifications to a designated group when the performance falls below a certain threshold. The conditions can also be set to skip a stage in the release pipeline during execution.
Continue Execution on Task Failure
Provides the ability to mark supporting tasks and proceed with the release pipeline execution even if the supporting task fails. Supporting tasks such as, notification tasks or performance tasks can be allowed to fail without affecting the successful execution of the release pipeline.
vRealize Automation Advanced Service Design Integration
The Advanced Service Design integration includes the following new extensibility capabilities for Release Managers:
- Invoke published vRealize Automation service blueprints from a release pipeline.
- Use the Beta version of the Advanced Service Design plug-in workflows in a release pipeline.
Team Foundation Server Integration
The Team Foundation Server integration includes the following new extensibility capabilities:
- Release Managers can configure multiple Team Foundation Server endpoints in a release pipeline.
- Existing build and test jobs configured in Team Foundation Server can be invoked from a release pipeline.
- Monitor real-time status and results of the Team Foundation Server jobs from the vRealize Code Stream release dashboard.
Upgrade to Artifactory Pro 3.9.3
This vRealize Code Stream release includes the Artifactory Pro 3.9.3 version.
Jenkins Plug-In for VMware vRealize Code Stream
The VMware vRealize Code Stream plug-in is now available in the Jenkins continuous integration dashboard.
See VMware vRealize Code Stream plug-in.
vRealize Code Stream 1.2 includes the following product documentation.
- Installation and Configuration
- Upgrading vRealize Automation 6.2.3 for vRealize Code Stream 1.2
- 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
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.2 release:
- Saving a release pipeline task deleted by another user might fail with a Constraint violation exception error.
- Compare view and Troubleshooting view might have rendering problems in the Firefox 33.0.5 Web browser.
- Renaming, editing, and moving a task to another stage causes a Task not found exception error.
- 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.
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
After upgrade, the release pipeline, stage, and task names with a period cannot be edited or saved.
Workaround: Save the release pipeline, stage, or task name without a period and edit.
Existing artifact management configuration does not appear in a non-default tenant after an upgrade from vRealize Code Stream 1.0.
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.
The pipeline execution can fail after you upgrade vRealize Automation 6.2.3 to 6.2.4.
This failure occurs when theWEB-INF lib older in vRealize Orchestrator does not contain the orchestrator-framework-6.2.3.jar file.The pipeline execution might fail when you upgrade vRealize Automation 6.2.3 to 6.2.4.
Workaround: Use the following procedure to fix this problem:
- Copy the orchestrator-framework-6.2.3.jar file at ./usr/lib/vcac/server/webapps/release-management-service/WEB-INF/lib/orchestrator-framework-6.2.3.jar to ./usr/lib/vco/app-server/deploy/vco/WEB-INF/lib.
- Restart vCO server using the command service vco-server restart.
- 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.
PowerShell Script task fails if the script file name is used in the PowerShell script business logic.
Workaround: Complete the following steps to fix the PowerShell script task error.
- Create a wrapper PowerShell script that invokes the actual user PowerShell script.
- Model this wrapper PowerShell script in the vRealize Code Stream script task.
For example, a user PowerShell script which expects two command line arguments.
Actual user script: deployAppServer.sh arg1 arg2
Wrapper PowerShell script: deployAppServer_wrapper.sh
./deployAppServer.sh arg1 arg2
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.
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.
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.