WO2015084150A1

WO2015084150A1 - A system and method to determine version of deployed package

Info

Publication number: WO2015084150A1
Application number: PCT/MY2014/000167
Authority: WO
Inventors: Soon Hin LEE
Original assignee: Mimos Bhd
Current assignee: Mimos Bhd
Priority date: 2013-12-05
Filing date: 2014-06-05
Publication date: 2015-06-11
Anticipated expiration: 2016-06-05
Also published as: MY175072A

Abstract

The present invention provides system and method which provides for a version of a deployed package to be determined and verified against release packages stored in a versioning repository. The system (100) of the present invention to determine version of deployed package comprising at least one release package (102) for locating and extracting deposited package; at least one versioning repository (104) for pairing and committing signature with package; at least one signature generator (106) for generating signature; at least one traversor (108a) for traversing down repository tree from said versioning repository; and at least one comparor (108b) for comparing stored signature with signature generated from deployed system. The present invention combines the features of existing and proven versioning repositories with a signature generator to uniquely identify the release system packages. These signatures are stored in the same tag within the repository and these signatures can be compared against the signature generated from the deployed system using an integrated tool. The distinctiveness of the present invention lies in the creation of a single unique signature for the single release package based on a pre-determined list of non-changeable files.

Description

A SYSTEM AND METHOD TO DETERMINE VERSION OF DEPLOYED PACKAGE FIELD OF INVENTION The present invention relates to a system and method to determine version of deployed package. In particular, the invention relates to a system and method which provides for a version of a deployed package to be determined and verified against release packages stored in a versioning repository. BACKGROUND ART

Currently available deployed system relies on control procedures to determine and confirm the version of a deployed system. Verification is executed in one direction from a versioned repository to the deployed environment. Proper and control documentation of the system is maintained separately and requires synchronization. If the documents are not synchronized, it would be very difficult for verification in the reverse direction (i.e. deployed folder back to the versioning repository). The issue of the currently available deployed system drives the need of determining and verifying the version of a deployed system against release packages stored in a versioning repository as proposed in the present invention.

One example of currently available method for verifying a version for each of a plurality of object files is disclosed in United States Patent No. US 7,143,395 B2 entitled "Verifying a Program Version" (hereinafter referred to as the US 395 Patent). In the US 395 Patent, a version of each of a plurality of object files is verified by identifying a version of an object file of a plurality of object files. An alert is generated in response to the different version of the object code file found in one or more version of the remaining object code files. The invention as disclosed in the US 395 Patent does not generate a single unique signature for the single release package based on a pre-determined list of non-changeable files as proposed in the present invention. Further, a proven version repository is not utilized for tracking purpose as provided in the present invention which identifies the version of the package used for deployment based on the repository. Another example as disclosed in an IEEE paper (2001 IEEE) entitled "Design and Implementation of Component Repository for Supporting the Component Based Development Process" by Jung-Eun Cha, Young-Jung Yang, Mun-Sub Song, Hang-Gon Kim suggest a theory for repository construction to support and realize Component Based Development (CBD) process and developed the Component Repository Prototyping System (CRPS) as implementation product of proposal techniques. In the said IEEE paper, component repository is provided as the most important part in Component Based Development (CBD). Further, individual techniques theory for repository construction to support and realize the CBD process is provided and Component Repository Prototyping System (CRPS) is provided for supporting CBD process by managing variety component products classified by each step of component life cycle and domain based on component architecture. The disclosure in the said IEEE paper does not relate to generation of a single unique signature for the single release package based on a pre-determined list of non-changeable files as proposed in the present invention and does not utilize a proven version repository for tracking purpose as proposed in the present invention which is able to identify the version of the package used for deployment based on the repository.

Another mechanism which integrates Use case-based requirements specification into release planning process is disclosed in an IEEE paper (2008 IEEE) entitled "A proposed Method for Release Planning from Use Case-based Requirements Specification" by Akos Szoke. In the said paper, use case modelling is integrated with release planning objective to form a consistent planning repository. Release planning which addresses the decision related to implementation of a selected requirement's collection in incremental development is provided. The disclosure in the said IEEE paper does not relate to generation of a single unique signature for the single release package based on a pre-determined list of non-changeable files as proposed in the present invention and does not utilize a proven version repository for tracking purpose as proposed in the present invention which is able to identify the version of the package used for deployment based on the repository.

The subject matter claimed herein is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described above. Rather, this background is only provided to illustrate one exemplary technology area where some embodiments described herein may be practice.

SU MARY OF INVENTION

The present invention relates to a system and method to determine version of deployed package. In particular, the invention relates to a system and method which provides for a version of a deployed package to be determined and verified against release packages stored in a versioning repository.

One aspect of the invention provides a system (100) to determine version of deployed package. The system comprising at least one release package (102) for locating and extracting deposited package; at least one versioning repository (104) for pairing and committing signature with package; at least one signature generator (106) for generating signature; at least one traversor (108a) for traversing down repository tree from said versioning repository; and at least one comparor (108b) for comparing stored signature with signature generated from deployed system. The at least one signature generator (106) for generating signature further having means to create a single unique signature by combining features of existing and proven versioning repositories by releasing and packaging version of system; depositing in at least one tag in versioning repository; creating non-volatile file list in machine readable code; locating and extracting files from versioning repository; unpackaging the same if required; generating unique signature (UID) using said non-volatile file list; and pairing the generated unique signature (UID) with package and commit back into the same tag in said repository.

Another aspect of the invention provides a method (200) to determine version of deployed package. The method comprising steps of determining version of deployed system against release packages stored in at least one versioning repository (202); creating package signature (204); and verifying version of deployed system package (206). The step for creating package signature further comprises steps of releasing and packaging version of system (502); depositing in at least one tag in versioning repository (504); creating non-volatile file list in machine readable code (506); locating and extracting files from versioning repository (508); unpackaging the same if required (510); generating unique signature (UID) using said non-volatile file list (512); and pairing the generated unique signature (UID) with package and commit back into the same tag in said repository (514). Yet another aspect of the invention relates to the step for determining version of deployed system against release packages stored in at least one versioning repository (202). For repository package (300), the said step (202) further comprises steps of locating and extracting deposited package from versioning repository (304); rehashing and constructing unique signature (306) based on combination of non-volatile file list (308) and deposited package (304); and pairing and committing constructed signature with package into versioning repository (310). For deployed package (400), the said step (202) further comprises steps of rehashing and constructing unique signature (406) based on combination of non-volatile file list (402) and folder of deployed package (404); traversing down repository tree (410) from said versioning repository (408); comparing stored signature against signature generated from the deployed system (412); an generating and forwarding report to user (414).

Still another aspect of the invention provides for the step of verifying version of deployed system package (206). The said step further comprises step of generating unique signature (UID) of the deployed package (604) from the created non-volatile file list (602); traversing versioning repository and comparing signatures to locate version (606); forwarding report version to user upon locating version of report (610); and generating report or exception if fail to locate version of report (612).

The present invention consists of features and a combination of parts hereinafter fully described and illustrated in the accompanying drawings, it being understood that various changes in the details may be made without departing from the scope of the invention or sacrificing any of the advantages of the present invention.

BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS

To further clarify various aspects of some embodiments of the present invention, a more particular description of the invention will be rendered by references to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail through the accompanying drawings in which: FIG. 1 illustrates the general architecture of the system of the present invention.

FIG. 2 is a flowchart illustrating the general methodology of the present invention to determine version of deployed package. FIG. 3 is a flowchart illustrating the steps for determining version of deployed system against release packages stored in at least one versioning repository for a repository package.

FIG. 4 is a flowchart illustrating the steps for determining version of deployed system against release packages stored in at least one versioning repository for a deployed package.

FIG. 5 is a flowchart illustrating the steps for creating package signature. FIG. 6 is a flowchart illustrating the steps for verifying version of deployed system package.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, this specification will describe the present invention according to the preferred embodiments. It is to be understood that limiting the description to the preferred embodiments of the invention is merely to facilitate discussion of the present invention and it is envisioned without departing from the scope of the appended claims.

Referring to FIG. 1.0, a system to determine version of deployed package is illustrated. As illustrated in FIG. 1.0, the system (100) comprising a release package (102) for locating and extracting deposited package; a versioning repository (104) for pairing and committing signature with package; a signature generator (106) for generating signature; a traversor (108a) for traversing down repository tree from said versioning repository; and a comparor (108b) for comparing stored signature with signature generated from deployed system. The signature generator (106) for generating signature further having means to create a single unique signature by combining features of existing and proven versioning repositories by releasing and packaging version of system; depositing in at least one tag in versioning repository; creating non-volatile file list in machine readable code; locating and extracting files from versioning repository; unpackaging the same if required; generating unique signature (UID) using said non-volatile file list; and pairing the generated unique signature (UID) with package and commit back into the same tag in said repository.

A general method (200) of an embodiment of the invention is illustrated in FIG. 2.0 wherein the method (200) to determine version of deployed package of the present invention comprising steps of determining version of deployed system against release packages stored in a versioning repository (202); creating package signature (204); and verifying version of deployed system package (206). A detailed description of the steps to determine version of deployed system against release packages stored in the versioning repository is illustrated in FIGs. 3.0 and 4.0 respectively. As illustrated in FIG. 3.0 for repository package (300); deposited package is first located and extracted from versioning repository (304). Upon locating and extracting deposited package, unique signature is rehashed and constructed (306) based on the combination of non-volatile file list (308) and deposited package (304). The constructed signature is paired and committed with package into versioning repository (310). For deployed package (400), unique signature is rehashed and constructed (406) based on combination of nonvolatile file list (402) and folder of deployed package (404). Subsequently, the process traverse down the repository tree (410) from said versioning repository (408) and stored signature is compared against signature generated from the deployed system (412). Thereafter, the report is generated and forwarded to the user (414).

Referring to FIG. 5.0, the steps for creating package signature is illustrated wherein the version of system is first released and packaged (502) and deposited under a tag in a versioning repository (504). Thereafter, non-volatile file list is created in machine readable code (506) and files are located and extracted from versioning repository (508). The extracted files are unpackage if required (510) and unique signature (UID) is generated using said non-volatile file list (512). The generated unique signature (UID) is paired with package and commit back into the same tag in said repository (514). The said signature is generated based on list of files in a release package stored within said versioning repository and list of files in said deployed package and said unique signature (UID) is used to identify version of package.

Referring to FIG. 6.0, the steps for verifying version of deployed system package (206) is illustrated wherein unique signature (UID) of the deployed package is generated (604) from the created non-volatile file list (602). Thereafter, versioning repository is traversed and signatures are compared to locate version (606). The report version is forwarded to user upon locating version of report (610); and report or exception is generated for failure of locating version of report (612). The step for traversing versioning repository and comparing signatures to locate version (606) further validates authenticity of the deployed package.

The present invention combines the features of existing and proven versioning repositories with a signature generator to uniquely identify the release system packages. These signatures are stored in the same tag within the repository and these signatures can be compared against the signature generated from the deployed system using an integrated tool. The distinctiveness of the present invention lies in the creation of a single unique signature for the single release package based on a pre-determined list of non- changeable files.

Unless the context requires otherwise or specifically stated to the contrary, integers, steps or elements of the invention recited herein as singular integers, steps or elements clearly encompass both singular and plural forms of the recited integers, steps or elements.

Throughout this specification, unless the context requires otherwise, the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated step or element or integer or group of steps or elements or integers, but not the exclusion of any other step or element or integer or group of steps, elements or integers. Thus, in the context of this specification, the term "comprising" is used in an inclusive sense and thus should be understood as meaning "including principally, but not necessarily solely".

It will be appreciated that the foregoing description has been given by way of illustrative example of the invention and that all such modifications and variations thereto as would be apparent to persons of skill in the art are deemed to fall within the broad scope and ambit of the invention as herein set forth.

Claims

1. A system (100) to determine version of deployed package comprising:

at least one release package (102) for locating and extracting deposited package;

at least one versioning repository (104) for pairing and committing signature with package;

at least one signature generator (106) for generating signature; at least one traversor (108a) for traversing down repository tree from said versioning repository; and

at least one comparor (108b) for comparing stored signature with signature generated from deployed system

characterized in that

the at least one signature generator (106) for generating signature further having means to create a single unique signature by combining features of existing and proven versioning repositories by:

releasing and packaging version of system;

depositing in at least one tag in versioning repository;

creating non-volatile file list in machine readable code;

locating and extracting files from versioning repository;

unpackaging the same if required;

generating unique signature (UID) using said non-volatile file list; and

pairing the generated unique signature (UID) with package and commit back into the same tag in said repository.

2. A method (200) to determine version of deployed package comprising steps of:

determining version of deployed system against release packages stored in at least one versioning repository (202);

creating package signature (204); and

verifying version of deployed system package (206)

characterized in that

creating package signature further comprises steps of:

releasing and packaging version of system (502); depositing in at least one tag in versioning repository (504);

creating non-volatile file list in machine readable code (506); locating and extracting files from versioning repository (508); unpackaging the same if required (510);

generating unique signature (UID) using said non-volatile file list (512); and

pairing the generated unique signature (UID) with package and commit back into the same tag in said repository (514).

3. A method according to Claim 2, wherein determining version of deployed system against release packages stored in at least one versioning repository (202) further comprises steps of:

for repository package (300)

locating and extracting deposited package from versioning repository (304);

rehashing and constructing unique signature (306) based on combination of non-volatile file list (308) and deposited package (304); and

pairing and committing constructed signature with package into versioning repository (310)

for deployed package (400)

rehashing and constructing unique signature (406) based on combination of non-volatile file list (402) and folder of deployed package (404);

traversing down repository tree (410) from said versioning repository (408);

comparing stored signature against signature generated from the deployed system (412); and

generating and forwarding report to user (414).

4. A method according to Claim 2, wherein verifying version of deployed system package (206) further comprises step of:

generating unique signature (UID) of the deployed package (604) from the created non-volatile file list (602); traversing versioning repository and comparing signatures to locate version (606);

forwarding report version to user upon locating version of report (610); and

generating report or exception if fail to locate version of report (612).

5. A method according to Claim 2, wherein generating unique signature (UID) using said non-volatile file list (512); said signature is generated based on list of files in a release package stored within said versioning repository and list of files in said deployed package.

6. A method according to Claim 2, wherein said unique signature (UID) is used to identify version of package.

7. A method according to Claim 4, wherein traversing versioning repository and comparing signatures to locate version (606) further comprising validating authenticity of the deployed package.