Build deployment automation for information technology management

Patent metadata

Field	Value
Publication number	US-9323513-B2
Application number	US-201414195383-A
Country	US
Kind code	B2
Filing date	Mar 3, 2014
Priority date	Mar 3, 2014
Publication date	Apr 26, 2016
Grant date	Apr 26, 2016

Abstract

A computer-executable mechanism captures code modifications for a computer-executable process from a development environment into build packages that may be deployed onto specified target environments with trace, audit, code compliance and rollback options from one single web portal. The mechanism supports build package code changes from different sources, automated test of the resulting build packages, and phantom source control of all packaged code base to reduce the burden on developers to manually source control code. The computer-executable mechanism supports a portal web server for building and deploying build packages to render user responses to configurable actions that may be passed on to a job sequencer to execute a series of jobs. A computer-executable roll-back mechanism takes a snapshot of the target environment prior to deployment of a build package so that a complete release rollback or an incremental release rollback may occur as needed.

First claim

What is claimed is:

1. A computer-assisted method for automating a build deployment for a software project, the method comprising:
combining a first artifact collection with a second artifact collection, wherein the first and second collections have different artifact types;
generating build metadata from combined artifact collection, wherein the build metadata includes a manifest list;
forming logical build data from the first and second artifact collections based on the build metadata;
when no build errors are detected with the logical build data, creating a build source data for deployment;
identifying a selected build package for deployment based on a selected target computing device, wherein the selected build package is identified by a build number;
in response to the identifying, extracting the selected build package from the build source data;
generating, based on the manifest list, deployment metadata for objects of the selected build package as identified by the build number for deployment;
resolving all dependences for selected objects based on the deployment metadata;
when no deployment errors are detected, deploying the selected build package for the selected target computing device, wherein the selected build package comprises the selected objects;
generating web page content when the creating of the build source data and the deploying of the selected build package through a first handler and a second handler with different programming languages, wherein the first handler and the second handler generate first and second generated outputs, respectively, that comply with a first markup language;
transforming the first and second outputs to first and second elements, respectively, that comply with a different markup language; and
injecting the first and the second elements into a rendered web page.

2. The computer-assisted method of claim 1 , further comprising:
parsing the combined artifact collection;
sorting the parsed artifact collection; and
generating the build metadata based on the parsed artifact collection.

3. The computer-assisted method of claim 1 , further comprising:
backing up artifact collection objects from a build computer device.

4. The computer-assisted method of claim 3 , further comprising:
when no build errors are detected with the logical build data, moving the artifact collection objects to a source control computer device.

5. The computer-assisted method of claim 4 , further comprising:
updating a software development lifecycle (SDLC) system about the build source data.

6. The computer-assisted method of claim 1 , further comprising:
when a build error is detected with the logical build data, repeating the combining, the generating, and the forming.

7. The computer-assisted method of claim 1 , further comprising:
backing up existing objects from the selected target computing device based on the deployment metadata.

8. The computer-assisted method of claim 1 , further comprising:
based on the deployment metadata, filtering an identified object to be excluded.

9. The computer-assisted method of claim 1 , further comprising:
updating a software development lifecycle (SDLC) system about the selected build package.

10. The computer-assisted method of claim 1 , further comprising:
when a deployment error is detected, repeating the identifying, the extracting, the generating, and the resolving.

11. The computer-assisted method of claim 1 , further comprising:
determining a categorization of one of the selected objects according to an artifact type; and
directing said one selected object to an appropriate handler.

12. The computer-assisted method of claim 1 , further comprising:
detecting a version error when a build version of a component is incompatible with a current version of the selected target computing device.

13. The computer-assisted method of claim 1 , wherein the first markup language comprises an Extensible Markup Language (XML) and the second markup language comprises a HyperText Markup Language (HMTL).

14. The computer-assisted method of claim 1 , wherein the first and the second elements map into a first web page section and a second web page section, respectively.

15. The computer-assisted method of claim 1 , the method further comprising:
generating, from a dictionary, the deployment metadata for the selected objects for deployment, wherein the build metadata includes the dictionary listing all the artifacts included into a build and describing object properties of the artifacts.

16. An apparatus comprising:
at least one memory; and
at least one processor coupled to the at least one memory and configured to perform, based on instructions stored in the at least one memory:
combining a first artifact collection with a second artifact collection, wherein the first and second collections have different artifact types;
generating build metadata from the combined artifact collection;
forming logical build data from the first and second artifact collections based on the build metadata, wherein the build metadata comprises a manifest list;
when no build errors are detected with the logical build data, creating build source data for deployment;
identifying a selected build package for deployment based on a selected target computing device;
in response to the identifying, extracting the selected build package from the build source data;
generating, based on the manifest list, deployment metadata for selected objects for deployment;
resolving all dependences for the selected objects based on the deployment metadata;
when no deployment errors are detected, deploying the selected build package for the selected target computing device, wherein the selected build package comprises the selected objects;
generating web page content when the creating of the build source data and the deploying of the selected build package through a first handler and a second handler with different programming languages, wherein the first handler and the second handler generate first and second outputs, respectively, that comply with a first markup language;
transforming the first and the second outputs to first and second elements, respectively, that comply with a different markup language; and
injecting the first and second elements into a rendered web page.

17. The apparatus of claim 16 , wherein the at least one processor is further configured to perform:
generating, from a dictionary, the deployment metadata for the selected objects for deployment, wherein the build metadata includes the dictionary listing all the artifacts included into a build and describing object properties of the artifacts.

18. A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed, cause a processor at least to perform operations comprising:
combining a first artifact collection with a second artifact collection, wherein the first and second collections have different artifact types;
generating build metadata from the combined artifact collection, wherein the build metadata includes a manifest list;
forming logical build data from the first and second artifact collections based on the build metadata;
when no build errors are detected with the logical build data, creating a build source data for deployment;
identifying a selected build package for deployment based on a selected target computing device, wherein the selected build package is identified by a build number;
in response to the identifying, extracting the selected build package

Assignees

• Bank Of America

Inventors

• Pillay Sanjay
• Sumin Anton
• Burnside Piedad L

Classifications

• G06F8/71

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/60 Primary

  Software deployment · CPC title

• G06F8/41

  Compilation · CPC title

• G06F8/65

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/70

  Software maintenance or management · CPC title