This topic contains information about fixes and updates in this patch and provides instructions for downloading and installing the patch.
The following table describes the issues that are corrected in this release.
|DRZXB-18357||The values for the Start Date, Start Time, Stop Date, Stop Time fields (accessible from Request > Step > Automation tab) are not getting deleted. For an automation step, if none of these fields are mandatory, one should be able to delete the values.|
|DRZXB-17319||Plan run did not start automatically at the scheduled time.|
|DRZXB-18151||REST API call for updating properties for installed components fails and a |
|DRZXB-17824||For any step within a request, if the value for any of the properties field (accessible from a new step > Properties tab) is set to blank, the blank value is not accepted and instead, the default value of the property is updated in the step.|
|DRZXB-11762||While logging on to BMC Release Process Management Classic or Requester UI, the session ID is not updated after the user has logged on successfully. This makes the application vulnerable and open to a security breach.|
|DRZXB-17970||As a non-root user, if you edit the value for any of the request properties that are marked private and if the value is the same as specified by the root user, the encrypted value changes for the non-root user. The changed encrypted value is displayed in the automation results for any step. The changed encrypted value may cause steps to fail.|
|DRZXB-17749||After upgrading to BMC Release Process Management 5.0.03, some of the fields for the existing automation step are displayed in numbers instead of the actual values. This issue may occur only for a few data retriever scripts.|
|DRZXB-17971||When you integrate BMC Release Process Management with JIRA in a non-SSL mode, automation scripts for JIRA fail to execute and the integration fails.|
|DRZXB-17813||If you go to the Applications tab, select an application, select an environment, and open any installed component for the environment, property names that are too long are truncated or are not visible at all.|
For a complete list of known and corrected issues in this patch, see Known and corrected issues.
This patch contains the following updates.
Updates that containsignificantly improve the performance of the BMC Release Process Management application.
In this release, BMC Release Lifecycle Management Requester UI is renamed to BMC Release Process Management Requester UI. The installation process, installation directories, configuration file paths, service name, and the URL to access the Requester UI remains unchanged.
If you are upgrading to this patch, there is no change to any of the processes, directories, and URLs. The new name reflects on the UI only.
In this release, BMC Release Process Management allows integration with TeamCity, which is a continuous integration server. By integrating with TeamCity, you can run builds created on the TeamCity server. By using automation steps, you can execute specific builds in a scheduled manner. The automation allows the user to run any build type on the TeamCity server. For more information, see TeamCity.
Detailed automation results for a step no longer appear in the server logs. Only a summary, which includes when a step starts and stops and errors, if any, appears in the server logs. To view a detailed automation result for a step, go to the Notes tab of a step and click the automation log results link. The following figure shows the detailed automation results for a step.
Use a rake task to delete request data from the database. When you specify a date, request data before the date is deleted and the results appear in a log file. By default, requests associated with plans are not deleted. You can specify whether to delete the requests associated with plans in the rake task. For more information, see Purging request data from the RPM database.
BMC Release Process Management now supports Transport Layer Security (TLS) version 1.2 as the out-of-the-box secure transfer protocol for client-server communication. For more information, see Configuring TLS secure protocol.
BMC recommends that you assess all security risks and vulnerabilities before switching to an earlier version of TLS.
The following enhancements have significantly helped improve the performance of the BMC Release Process Management. Pages load faster, and it takes less time to perform tasks by using BRPM:
Expandable list of statistics
|Statistics for phases (Environment > Metadata > Manage Phases) such as the number of requests, number of request templates, and the number of procedures appear as a link.|
|Faster page loading||Roles, Phases, and Servers list loads faster and consumes less time.|
|REST API v1 for Installed Components|
REST API response for the PUT API call for REST installed components is updated to contain only the following attributes:
The following table describes the updates made to the BRPM UI in this patch.
|Numerical pagination across BMC Release Process Management||Classic|
In this release, a numerical pagination system is introduced across the application. Page numbers appear at the top and the bottom of each list, which enables easier access to the records on any given page and significantly improves the performance of the application.
The following figure shows updated pagination for the Environment > Servers page.
|Expandable list of Inactive Applications, Inactive Servers, and Inactive Teams||Classic|
In earlier releases, the list of inactive applications appears in a table. If the list runs long, the Applications page takes a long time to load and affects the performance of the application. In this release, the inactive applications are displayed in an expandable table.
This change is also made for the list of Inactive Servers and Inactive Teams.
Click the Inactive Applications link to view a list of servers in the application.
|Expandable statistics for phases||Classic|
Statistics for phases such as the number of requests, number of request templates, and the number of procedures appear as a link. Click the Show Stats link to view the statistics for any phase.
|Updated UI for adding and editing properties||Classic|
While adding or editing properties (Environment > Properties), you can now select components, packages, servers, and work tasks in a new and updated manner.
In earlier releases, check boxes appeared against each of the elements, which made it cumbersome to add/edit properties. In this release, when you click any of the Add Components, Add Packages, Add Servers link, or Add Work Tasks link, a dialog box appears, which enables you to select one or multiple elements and move them all to the selected area.
For more information, see Managing properties.
|Updated UI for adding/updating servers and server level groups for installed components of applications||Classic|
You can now add servers and server level groups to installed components of an environment by using an enhanced UI. The new UI enables you to select one or multiple servers/server level groups and move them to a selected area with a single-click.
The following figure shows the updated UI for adding servers/server level groups to installed components.
For more information, see Associating components with environments.
|Updated UI for adding current members to a group||Classic|
While adding current members to a group (System > Groups > Edit a selected group), when you click the Change User link, a dialog box appears to enable you to select multiple or all users to be added to the group.
For more information, see Managing groups.
|Added a search box for searching applications to be assigned to roles||Classic|
While assigning applications to roles, a search box is added to enable you to search for any specific application that matches your requirement.
For more information, see Managing teams.
|Enhanced search capability for searching request templates||Classic|
While creating or updating requests, if you select a request template, a new search box is added on the UI to help search for a specific template that matches your requirement.
The following figure shows the search box while creating a new request.
New Create Request feature
Global search box for searching requests
In the Classic UI, you can now create a new request directly from the Requests tab.
In this release, a global search box for searching requests is added on the menu bar. You can search for a request from any page in the BMC Release Process Management application.
|One-click access to the Notes tab for a step|
In the Classic UI, you can now click the Notes icon on the Actions area to directly view the Notes tab for any step.
You can also view/add/edit the notes for a step by a single-click.
In the Requester UI, click theNotes icon before the step number to directly view the Notes tab.
- Improves performance of the BMC Release Process Management application
With this release, the following changes are made to the REST API web services.
|REST API updates||Description|
|REST API call for installed components updated|
REST API response for the PUT request for REST installed components is updated to contain lesser attributes. The API response for updating properties of an existing installed component (PUT /v1/installed_components/[id]) contains only the
This change significantly improves the performance of the API calls.
For the sample updated API response, see REST installed components.
|New REST API call for uploading documents|
A new REST API call is introduced in this release that enables you to upload documents to a request or to a step. You can upload documents up to 5 MB only.
For more information, see REST v.2 uploads.
To download the patch, go to the BMC Release Process Management 5.0.03.001 download page and click the Patches tab.
For more information, see Downloading the installation files.
The process to install the patch is like installing any major, minor, or service pack version.
For more information, see Installing.
The process to upgrade the patch is like upgrading to any major, minor, or service pack version.
When you install or upgrade to BMC Release Process Management 5.0.03.001, by default the JVM memory is set to 8 GB. Even if the memory settings in your environment are different, after the upgrade the JVM memory size is set to 8 GB. Ensure that you adjust the memory settings that match your environment. For more information, see Configuring JVM memory settings.
For more information, see Upgrading.