DevOps Automation

 View Only

What's New: IBM UrbanCode Velocity 4.0.9

By Osman Burucu posted Wed April 26, 2023 10:41 AM


A few weeks ago a new version for IBM UrbanCode Velocity (now IBM DevOps Velocity) has been released, and it contains exciting new functionality.

What's new in IBM UrbanCode Velocity 4.0.9

Jenkins plug-in has been completely redesigned, new KPIs were added, automation tasks and manual gates approval enhanced. Let us dive into the new features.

New Jenkins plug-in

The existing plug-in for Jenkins (which was actually a plug-in for Jenkins) is now Jenkins (legacy) as the new plug-in is for Velocity directly. This plug-in is available under Settings -> Integrations -> Available and can be used with Velocity 4.0.9 and later. This plug-in provides better performance and more flexibility.

For configuring the new Jenkins plug-in you need to provide the URL and the API token. To acquire the token please browse in your Jenkins instance to Dashboard -> <user id to be used> -> Configure

Create Jenkins API Token

Provide a name and press Add new Token button. Copy the API token to the clipboard to be used with Velocity plug-in installation/configuration process.

Velocity Jenkins Integration configuration

Fill in the fields for Integration name, your Jenkins Server URL, the User-ID used for the integration and finaly past your newly created API token. Restrict which jobs get synced with an xPath filter string. For example:
'starts-with(fullName,"folder/path/")' to only get jobs in a specific folder or: 'contains(name,"Team Name")' to only get jobs that contain a specific substring or: '(starts-with(fullName,"folder/path/") or contains(name,"Team Name")) and ends-with(name,"my-suffix")'
and so on.
Click on Update to save the changes.

Now in the integration view confirm if it was configured properly.

Velocity Jenkins integration configured view

Next step would be to add a Jenkins managed application to the pipeline view.

Velocity add jenkins app
Velocity Jenkins managed app part 2

Map the Jenkins Jobs to the Velocity pipeline environments.  Note: Jenkisn jobs must be parameterized in order to be mapped to a Velocity environment.

Pick the Jenkins Job:

Velocity Map a jenkins job

Next select the parameter established in the Jenkins Job:

Velocity provide parameter for jenkins job

When all environments are fully mapped your pipeline should resemble the following:

Velocity - Jenkins Jobs fully mapped to environments

Velocity provides very powerful and extensible metrics and with this version a new feature for KPI's has been added. Let us have a look how to use them.

Lead Time and Cycle Time KPIs

To activate and configure this new KPIs you need to navigate to the Settings page and select Insights. Click the hamburger icon on the right for KPI you wish to modify and select edit.

Velocity - edit a KPI

In the new dialog, provide a Rule name, clidk Row and adjust the range as desired along with an associated color. Repeat this steps until all Ranges have been defined.

Velocity - define ranges for KPI

Next scroll down and specify the team, value stream(s) and application(s) the rules should be applied to.

Velocity - configure KPI part 2

Click on Submit to save and apply the rules.

In the Insights view you can now add the Lead Time and Cycle Time KPIs to any of the existing dashboards by clicking Add Charts and selecting the KPI.

Velocity - KPI chart

More about Velocity 4.0.9 

can be found in the full online documentation, what's new history and fixlist information here in the overview page.