What's new in IBM UrbanCode Deploy
The latest version of IBM® UrbanCode® Deploy, includes new functions and enhancements.
7.2.1.2
Version 7.2.1.2 is a maintenance release and includes various bugs and security related fixes.
This release is recommended for all customers.
- IBM Common Licensing supported
- IBM UrbanCode Deploy now supports IBM Common Licensing V9.0 for managing your IBM UrbanCode Deploy licenses.
7.2.1.1
Version 7.2.1.1 is a minor release and includes various bugs and security related fixes. This release is recommended for all customers.
- A new agent script that sets the ANT_HOME and GROOVY_HOME variables.
- The tool_env script is added to the agent directory on upgrading to v7.2.1.1. Agent startup tool uses this script to set and reference the environment variables appropriately.
7.2.1.0
Version 7.2.1.0 is a major release and includes various features and security related fixes. This release is recommended for all customers.
- A new UI for running an application process
- The new UI for deploying applications is a single-page form that has collapsible sections rather than a multi-page wizard. The existing deployment wizard is not removed to allow you to configure each application to use the wizard or the form.
- Scheduled system blackouts
- Maintenance mode can now be scheduled on the system calendar. These calendar events are called maintenance blackouts that consists of a start time and a planned duration. At the start time, maintenance mode gets engaged, but does not end automatically. Processes cannot be scheduled during a planned maintenance mode. When the administrator turns off the maintenance mode, the calendar event is updated with the actual duration of the event.
- Get the start and end time of a plug-in step in the output log
- Three new timestamps are provided in the output log of the plug-in step. The first timestamp logs the time prior to the step running but after the plug-in has been staged. The second timestamp logs the time plug-in step completes. The third timestamp is logged after the post processing script has been evaluated on the plug-in step.
- CLI to download full set of execution logs
- API support is available for downloading the execution logs of a workflow trace. Workflow trace is a generic name for a process. Processes such as generic process, component process, and application process have a workflow trace.
- Get the name of the approver in a manual task as a property
- When a manual task is approved, the approver name and display name are now exposed as output
properties in the step. These properties can be referenced using:
${p:ManualTask/ApproverDisplayName}
and${p:ManualTask/ApproverName}
- Trimmed whitespace in properties files
- The server’s installed.properties values are now trimmed of whitespace to prevent install and deploy problems.
- Install and update information of plug-ins is recorded in the audit log
- The audit logs entries when plug-ins are loaded and updated.
- Script tool_env that sets the appropriate ANT_HOME and GROOVY_HOME
- Added ability to specify a default state for the 'only changed versions' check box on per application basis
- You can now specify if the 'only changed versions' check box should be enabled by default or not for your applications.