HCL UrbanCode Velocity 1.5.1 has several new features to improve your software delivery flexibility, governance, and analytics. Keep scrolling to check out some of the highlights of the latest release of our Value Stream Management tool.
A Value Stream Swim Lanes view is now available for all value streams. The new view reorganizes your original value steam based on assigned user. You can use this view to identify who owns certain work items and how far along these items are in the value steam. Take your agile ceremonies to the next level, by being able to spot who needs help or which items might be stuck.
Shell Script Tasks
A new “Shell” plugin brings the powerful flexibility of containerized shell execution as part of deployment plans. Simply add the plugin and integration to Velocity and you will be able to configure deployment plan templates with a new type of task to “Run a Shell Script”.
First, you need to add the shell script plugin to your instance of Velocity. Refer to documentation to see how to add an integration to your specific version of Velocity. If adding via a vsm.json file, check to see what fields to provide. Refer to documentation for the latest image string. An example vsm.json object is provided below.
Adding the integration and plugin through a vsm.json file it will do three things:
- Adds the shell script plugin to your instance of Velocity.
- Creates a new shell script integration. For shell scripts, we should only ever need one integration per instance of Velocity. A rare exception might be to use different plugin versions.
- Adds the shell script integration to the vsm.json for the value stream we uploaded it to. This is a side effect. Because this is not needed and might cause future confusion, you may want to re-download, remove the integration, and re-upload the vsm.json file, or just use a temporary value stream to upload the vsm.json and then delete the value stream when done.
After the shell script plugin has been added and an integration created, you need to add shell script tasks from deployment plan templates. Simply navigate to your deployment plan and create a new task. When the task form is shown select “Shell Script” and type your script into the box provided.
Deployment Plan Task Support for UrbanCode Deploy Properties
Velocity 1.5.1 introduces the ability to pass properties to an UrbanCode Deploy (UCD) task as part of a deployment plan. The UCD task is executed by UCD with application process request property values being passed from Velocity according to property name.
An UrbanCode Deploy (UCD) integration is required. Create a deployment plan and create (or edit) an UrbanCode Deploy task.
Simply add property name-value pairs to the “UCD Properties” text box within the create/edit task form. Name-value pairs should be formatted as “<property name>=<property value>”, with one property being set per line, as shown in the screenshot below. Properties of type “Text” and “Single Select” are set as literal values, while properties of type “Multi-Select” are set as comma delimited literal values. Properties of type “Checkbox” are set as Boolean (true or false).
The values shown above correspond to the following UCD properties.
Run the task from Velocity.
Per execution, the application process request property values in UCD will match the values set in Velocity.
Learn more about HCL UrbanCode Velocity here.