DevOps Feature: Inflight Parallel Check Report

Susan Cannington

November 2017

The latest release is now out, Rev-Trac v7SPS03! A hidden gem that will convince you that it is high time to upgrade your Rev-Trac version, is the inflight parallel check report. This gem is related to the need to facilitate and manage parallel development, which is becoming a more common occurrence as you embrace DevOps and an Agile delivery methodology.

There are two ways to access this new feature: console menu path or Rev-Trac workbench button.

Via console menu path

To access via menu path – from the console select Request Management – Tools – Parallel Dev Workbench – third tab labelled ‘Inflight parallel check report’ with selection criteria by:

Object name
Transport number(s)
Rev-Trac request number

with additional selection criteria by Project name, Request type and Status.

Via Rev-Trac workbench

From the Rev-Trac Workbench – there is a new button called Inflight parallel check report. After selecting a request, this report will evaluate all objects contained in the request against ALL locked objects in Rev-Trac and provide a list of the transports/requests that also contain the same objects. So why is this important and isn’t that what OOPS check does?

The ad-hoc OOPS check (as well as a regular migration status approval OOPS report) only shows transports/requests with the same objects that are NOT migrated in the required transport release date/time order to the target system assigned in the workflow. It will not show the transports/requests that ARE migrated in their transport release date/time sequence order.

How can this new report benefit you? When you have parallel development, and you want to test your changes, you may not be aware of another parallel changes that has been migrated into the test system AFTER your request. Your test results may not be what was expected. This simple button will tell you if the objects in your request are in other requests and could be the cause of the test results deviation.