4 April 2025
Overview
We are very pleased to announce the release of IBM DevOps Deploy 8.1.1 (2025.03).
IBM DevOps Deploy is an application-release solution that infuses automation into the continuous delivery and continuous deployment (CI/CD) process and provides robust visibility, traceability and auditing capabilities. IBM DevOps Deploy is the new name of IBM UrbanCode Deploy from 8.0.0 onward.
We introduced many new enhancements and features in the 8.1.1 release. To see all the details of What’s New in 8.1.1, please see the What's New page.
Enhancements in DevOps Deploy 8.1.1
Version 8.1.1 includes the following enhancements:
| Feature Title |
Description |
| Added support for Java 11 in FIPS mode |
You can install the server, agent, and agent relay on IBM Semeru Runtimes which includes FIPS 140-3. You can also enable FIPS manually on the systems running the server, agent, and agent relay.
See FIPS mode enablement for more information.
|
| Enhanced the new Dashboard view |
Optimized dashboard statistics reporting time to more quickly update the dashboard with latest deployment details.
See Dashboard for more details on how it helps you to better track, analyze, and monitor your deployments and agents.
|
| Added support for Java distribution on AIX hosts running the Deploy Agent |
You can now manage Java on your AIX agents as shown in the example below:
See Managing Java packages on an agent for more details.
|
| Enhanced the Maintenance Blackouts feature |
You can now create a maintenance blackout with a usual recurrence pattern, description, schedule, and a calendar view.
See Management of maintenance blackouts for more information.
|
| Enhanced the deployment execution log user interface |
The deployment log user interface is enhanced to add:
- A Status filter to filter the execution steps by status, such as: Any, Not Executed, Success, Canceled, and Failed. With this change, you can get a quicker review of the output in a deployment execution.
|
| Added a secure property for changing Tomcat private key password |
You can change the Tomcat private key password using the tomcat.key.password property in the secured-installed.properties file.
See Changing passwords for the Tomcat keystore for more information.
|
| Added a Cancel option for deployments that are stalled in 'waiting to start' state |
You can cancel deployments that are stalled in the 'waiting to start' state.
See Canceling stalled deployments for more information.
|
| Added support to allow one to select multiple required-role option for application and component processes |
You can assign multiple roles while editing application and component processes.
See Creating component processes for more details.
|
| Added REST APIs to get Deploy tokens with their expiration dates |
Added the following CLI endpoints:
|
| Added REST API to manage the role permission |
Added the updateRoleActions CLI endpoint.
See Update any number of actions for one or more roles and types for more details.
|
| Added REST API to get task ID and task details for manual task approvals using only applicationProcessRequestId |
Added the getApplicationProcessRequest CLI endpoint to return the task ID and details associated with approval processes of an application process request.
See Get applicatlon process request properties for more information.
|
| Added REST APIs to import and export application process |
Added the following CLI endpoints:
|
|
|
|
|
|
|
Mainframe Enhancements
With the DevOps Deploy 8.1.1 release, we also provided the following enhancements to help our zOS customers:
- Submit job plugin step enhanced to handle job archival in a more reliable manner
- Wait-for-job plugin step enhanced to handle job not found behavior
- Z Inventory feature is now supported for agent versions prior to the 7.3.1 release
- V2 version types use CP commands for deploying datasets as opposed to XMIT commands in the past
Process As Code (PAAC)
We have introduced a new Process as Code (PAAC) feature which aims to allow users to configure their processes as code and store them in a git repository as a single source of truth. The processes can be written in a JSON or YAML format and the PAAC tool comes with scripts to interface with DevOps Deploy to update the processes.
As your code is commited to a git repository or a pull request is initiated, you can leverage our utility scripts to upload the new process as code to your Deploy Server. To see an example of how this works with Jenkins, see Integrations. You can follow a similar process with other tools like Azure DevOps and GitLab. To download the utility scripts that allow you to upload your new processes to DevOps Deploy, click Downloads.
See Process as Code for more details.
Summary
As you can see from all of the enhancements above, we are fully commited to the IBM DevOps Deploy product and will continue to enhance the solution with heavy emphasis on the feedback of our customers. Investment is occurring across the board in the product including the mainframe, container deployments, processes as code, and more.
If you have an Idea for the product, we would welcome your input by creating a new Idea.