The following enhancements are included in each release. In addition to various bug fixes.

Key Features in 1.5.1


New Deployment Plan Task can “Run a Shell Script”

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

Deployment Plan Task Support for UrbanCode Deploy Properties

Velocity can now pass properties to UrbanCode Deploy (UCD) tasks as part of a deployment plan. Property values can be set from Velocity as name-value pairs in the “UCD Properties” text box when creating or editing a task.

New Value Stream Dot Hover-Over

Dots now display hover-over details making value streams more interactive and data rich. Hover-over is available in all “Dot” views: value stream stage view and value stream swim lanes view.

Added Sprint and Release Details and Sprint Coloring

Dots now have sprint and release fields displayed in the details panel. Both are also available as view coloring schemes.

Jenkins Templates are Hidden

The UI has been improved for Jenkins Jobs by hiding CloudBees Jenkins templates which cannot be run on their own.

Other UI improvements

Other UI improvements include the pipeline deployment version selector and improved spacing for stage names.

Bug Fixes

  • Fixed issue where template deployment plans might not be visible to an authorized user.
  • Fixed issue where multi-select process did not work for combined apps.
  • Fixed issue for dots with long histories.
  • Fixed age in stage value for dot overview.
  • Fixed an issue to support “latest” as a plugin image tag.


Key Features in 1.5.0


New Value Stream Swim Lanes view

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. The DQL querying is available if you are looking for something specific.
Swim Lanes Sample Picture

New Pipeline Executor role

The new Pipeline Executor role allow teams to give developers the ability to push builds through the pipeline, but not modify them. Proper use of this role ensures good division of duties and conformity to each deployment.

Integration logs

Improvements to integration logs have been made to improve troubleshooting. Now, the last ten integration executions are saved in a log and each can be viewed. The Logs Modal dialog has been redesigned to better accommodate the additional information.
Execution Logs Picture

Insights dashboard improvements to the Deployment Count chart

Several improvements have been made to the Deployment Count chart.

  • If a links is available for a Deployment Count chart, it links to additional details.
  • The chart can be filtered by User.
  • The Group By drop down list now expands to display the selected option.

Bug Fixes

Problem: Unable to disable SMTP configuration setting

There is now a Delete button to remove a SMTP configuration. Prior to this fix, the SMTP configuration could not be unset or deleted.

Known Problems

    • Significant Velocity Related Performance Issues for UrbanCode Deploy prior to v7.0.5.1
      APAR PI99803 identified a significant UrbanCode Deploy performance issue due to the Velocity UrbanCode Deploy Integration creating a large number of login requests when gathering deployment information. This issue is resolved with UrbanCode Deploy v7.0.5.1. If you are using UrbanCode Deploy v7.0.0.0 or greater, contact the L2 support team to obtain a performance related patch.
    • Velocity 1.5.1 Possible Loss of Access to Deployment Plans
      A version 1.5.1 issue can cause loss of access to deployment plans for preexisting usernames containing upper case lettering (fully lowercase names/emails are unaffected). If you have users affected by this, contact support for an immediate work around. This issue will be resolved with an early release of 1.5.2.

Plan & Prepare

For supported platforms and requirements you can dynamically generate a system requirements report using the Software Product Compatibility Reports (SPCR) tool.

Install the server

There are two option to obtaining the installation package: online installer and offline installer. Both options will require a master license key, which can be acquired from:

Online installer

The online installer option for installing the product requires an internet connection for the entire process. It requires minimum storage for the downloaded package. The downloaded image contains only the Helm charts used to pull the product Docker images from a GitHub location. This is our recommended installation method.

Download the online installer package depending on the platform, the product is being installed.

After the download completes, start the executable file to begin the install process.

Offline installer

Use the offline installer to install Velocity without internet connection. You will still need internet connection at some point to download the installer itself. Once downloaded, the installer will include all containers needed to successfully install the product. For this reason, the offline installer is larger than the online installer and will require more time/bandwidth and disk space when downloading.

The installation package is available from IBM FixCentral. Search and select the installation package appropriate for the installation platform.

After downloading the installation package, decompress the contents into two directories: one for Kubernetes and the other for Docker Compose. See the documentation section on installation for instructions about how to install the server.

A product license key is required to install the product. To obtain a key, you must agree to the terms and conditions provided on Passport Advantage.


To learn more about UrbanCode Velocity, see documentation.

For help installing or using UrbanCode Velocity, post your questions in the UrbanCode forums. Tag your question with velocity.

To suggest an enhancement to the product, visit the RFE Community

Get support

For information from support, including FAQs, visit the IBM Support portal. You can configure the support portal to view information about specific products.

Starting in 1.5.1

v1.5.1 Supports Upgrades from any Prior Version

All versions, including v1.4.5, can be directly upgraded to v1.5.1. Helm dependent upgrades from v1.4.5 to v1.5.0 were not supported (see 1.5.0 notes) but can be part of the upgrade path: v1.4.5 to v1.5.0 to v1.5.1. Velocity v1.5.1 also fixes an old issue that required versions older than v1.2.6 to upgrade to v1.2.6 before upgrading further.

NOTE: Helm upgrades from versions prior to v1.5.0 still require helm delete --purge <release_name> (see Helm Upgrade Requirements for v1.5.0)

Starting with v1.5.1, service database locations within MongoDB are normalized between Helm and Docker-Compose. This change is automatic and transparent upon upgrade but is worth noting as a difference in database structure.

Case Insensitive Usernames

Usernames (usually email addresses) are no longer case sensitive. This is intentional. A side affect will be that upgrades will merge into a single account any preexisting user accounts differentiated only by grammatical case.

A version 1.5.1 bug is being addressed that can cause loss of access to deployment plans for preexisting usernames containing upper case lettering (fully lowercase names/emails are unaffected). If you have users affected by this, contact support for an immediate work around. This issue will be resolved with an early release of 1.5.2.

Starting in 1.5.0

Upgrade Path from v1.4.5 to v1.5.0 is Not Supported for Kubernetes/OpenShift

The specific upgrade from 1.4.5 to 1.5.0 for helm dependent installations (Kubernetes, OpenShift, and ICP) is not supported. The result might be inaccessible data, especially for integrations. New installations of v1.5.0 and upgrades from v1.4.4 or lower to v1.5.0 are supported. This issue is resolved as of v1.5.1, allowing the upgrade path from v1.4.5 to v1.5.0 to v1.5.1 for Helm dependent installations.

Helm Upgrade Requirements

Starting with v1.5.0, we have added and modified some Helm Selectors to adhere with best practices. Therefore, running the helm upgrade command from a previous version of UrbanCode Velocity will fail. All upgrades from a version prior to v.1.5.0 to v1.5.0 or later will require a Helm purge as described below.

  1. Delete your currently installed release with helm delete --purge <release_name>, where <release_name> is the name of your current UrbanCode velocity release.
  2. Follow the normal install directions with all previous name and values from your previous release.

Note: Your Mongo database will be not be modified as it is maintained outside of the installation.

Starting in 1.4.5

Mongo Database Support and Upgrade Cadence

In v1.4.5, the distributed version of MongoDB was upgraded from v3.4 to v3.6. Docker Compose installs will see the upgrade happen automatically. Other Docker platforms (OpenShift, Kubernetes, etc), will need to manually upgrade their MongoDB instance. MongoDB v3.4 is still supported as of the release of v1.4.5. However, MongoDB v3.4 has been End of Life by Mongo, so we recommend customers upgrade at their earliest convenience.

Going forward, when our shipped version of MongoDB is upgrade, we will continue to support the prior version of MongoDB, but deprecate the version before that. As an example, when the shipped version of MongoDB is upgrade to v4.0, we will continue to support v3.6 and deprecate v3.4. We plan to make two MongoDB upgrades a year, so it would not force our Enterprise Docker Platform users to upgrade their MongoDB image more than once a year.

Starting in 1.4.2

UrbanCode Deploy Audit Logs: APAR PI99803

APAR PI99803 identified a significant performance issue where the UrbanCode Deploy Integration was creating a large amount of login requests when gathering deployment information. If using UrbanCode Deploy v7.0.0.0 or greater, it is highly recommended that you contact the L2 support team to obtain a performance related patch.