Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Post-deployment Validation of Related Binary Objects

IP.com Disclosure Number: IPCOM000248872D
Publication Date: 2017-Jan-19
Document File: 6 page(s) / 156K

Publishing Venue

The IP.com Prior Art Database

Abstract

A system and method to allow post deployment validation of binary software objects, via the use of 2 utility programs. 1. A post build utility which will append information to each binary object/program in the set of changes, identifying the object as a member of that set. 2. A post deployment utility which will extract and use the appended information in each binary object to validate that the correct version of all of the related objects will be picked up using the current system hierarchy.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

1

Post-deployment Validation of Related Binary Objects

As software development moves towards continuous delivery the frequency and complexity of code changes increases. A related set of changes

will be deployed by a code management system and may comprise of a mix of binary and text based objects. For example a panel definition and

the binary code used to display that panel. Although a code management system may successfully deploy a set of changes, system configuration

may inadvertently invalidate that deployment. To mitigate this deployment risk a mechanism is required to validate that all objects in a set of

changes are being correctly used. Validation of text based objects can be done by observation however validation of binary objects, program

executables, is much harder. What is required is a mechanism to allow post deployment validation of related binary objects.

In order to allow post deployment validation of binary objects this proposal describes the use of 2 utility programs.

1. A post build utility which will append information to each binary object/program in the set of changes, identifying the object as a

member of that set.

2. A post deployment utility which will extract and use the appended information in each binary object to validate that the correct

version of all of the related objects will be picked up using the current system hierarchy.

2

As related binary objects are promoted in a code management system there is a risk that system configuration may invalidate the code promotion.

For example see Figure 1

3

4

The SCM will successfully deploy the set of changes, CS1, consisting of programs P1, P2 and P3. However program P2 will, although

successfully deployed, be invalidated due to a prior version of P2 existing higher up in the system search order, in the quick fix library.

What is required is a mechanism to store and retrieve information in each binary object (program), identifying that object as a member of a

particular set of changes, so that once deployed a utility program can perform binary validation using the system hierarchy.

So taking the example from figure 1. The SCM will build programs P1, P2 and P3 unaltered from existing build p...