CN113805930A - Increment packaging method and device - Google Patents

Increment packaging method and device Download PDF

Info

Publication number
CN113805930A
CN113805930A CN202111178019.1A CN202111178019A CN113805930A CN 113805930 A CN113805930 A CN 113805930A CN 202111178019 A CN202111178019 A CN 202111178019A CN 113805930 A CN113805930 A CN 113805930A
Authority
CN
China
Prior art keywords
jar
list
package
files
directory
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111178019.1A
Other languages
Chinese (zh)
Inventor
农倩倩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202111178019.1A priority Critical patent/CN113805930A/en
Publication of CN113805930A publication Critical patent/CN113805930A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/658—Incremental updates; Differential updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Abstract

The invention provides an increment group packing method and a device, which can be used in the field of distributed technology, and the method comprises the following steps: comparing the Jar packages in the current version and the baseline version, and searching whether the Jar packages with the same name exist or not; if the Jar packages with the same name do not exist, updating and deleting the Jar list and the newly added Jar list based on the Jar packages with different names; if the Jar package with the same name exists, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name; and performing incremental packaging on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate an incremental package of the current version. The invention can solve the problem of increment group package of the Jar package.

Description

Increment packaging method and device
Technical Field
The invention relates to the field of distributed technology, in particular to an increment packaging method and device.
Background
The following problems exist with current incremental packages:
firstly, the Jar packages upgraded with the same name cannot be compared with each other: the previous increment group package compares the differences of the files in a mode of comparing the md5 values of the files to obtain an increment file. However, even if the code of the Jar package is not changed, the md5 value of the Jar package is different, and a changed Jar package list cannot be obtained.
Secondly, upgrading Jar packages with different names cannot identify the same Jar package due to the fact that the version numbers of the Jar packages are inconsistent, and difference comparison cannot be conducted, for example sme-service-1.0.Jar and me-service-2.0. Jar.
Therefore, all the deployment of Jar packages is realized by adopting a full clearing and full deployment mode, incremental deployment cannot be realized, the deployment time is long, and problems are easy to occur.
Therefore, there is currently a lack of a method for incremental packaging.
Disclosure of Invention
The embodiment of the invention provides an increment group packing method, which is used for solving the increment group packing problem of a Jar package and comprises the following steps:
comparing the Jar packages in the current version and the baseline version, and searching whether the Jar packages with the same name exist or not;
if the Jar packages with the same name do not exist, updating and deleting the Jar list and the newly added Jar list based on the Jar packages with different names;
if the Jar package with the same name exists, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name;
and performing incremental packaging on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate an incremental package of the current version.
The embodiment of the invention provides an increment group packing device, which is used for solving the increment group packing problem of a Jar package and comprises the following components:
the same-name Jar package searching module is used for comparing Jar packages in the current version and the baseline version and searching whether the Jar packages with the same name exist or not;
the different-name Jar package processing module is used for updating and deleting the Jar list and adding the Jar list based on the Jar packages with different names if the Jar packages with the same name do not exist;
the same-name Jar package processing module is used for decompressing the same-name Jar package in the current version to obtain a file under a first directory if the same-name Jar package exists; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name;
and the increment package generating module is used for performing increment package on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate the increment package of the current version.
The embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the processor implements the above incremental packaging method.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program for executing the above incremental packaging method is stored in the computer-readable storage medium.
In the embodiment of the invention, comparing the Jar packages in the current version and the baseline version, and searching whether the Jar packages with the same name exist; if the Jar packages with the same name do not exist, updating and deleting the Jar list and the newly added Jar list based on the Jar packages with different names; if the Jar package with the same name exists, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name; and performing incremental packaging on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate an incremental package of the current version. In the process, when the Jar package with the same name as the reference version is encountered, the Jar package is decompressed without directly adopting comparison file difference, all files in the two Jar packages are compared, automatic incremental packaging can be realized, and the problem caused by the Jar package in the incremental packaging is solved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
FIG. 1 is a first flowchart of an incremental packaging method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for incremental packaging according to an embodiment of the present invention;
FIG. 3 is a flow chart of an incremental packaging method according to an embodiment of the present invention;
FIG. 4 is a first schematic diagram of an incremental packaging apparatus according to an embodiment of the present invention;
FIG. 5 is a second schematic diagram of an incremental group packing apparatus according to an embodiment of the present invention;
FIG. 6 is a third schematic diagram of an incremental group packing apparatus in accordance with an embodiment of the present invention;
FIG. 7 is a diagram of a computer device in an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.
In the description of the present specification, the terms "comprising," "including," "having," "containing," and the like are used in an open-ended fashion, i.e., to mean including, but not limited to. Reference to the description of the terms "one embodiment," "a particular embodiment," "some embodiments," "for example," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The sequence of steps involved in the embodiments is for illustrative purposes to illustrate the implementation of the present application, and the sequence of steps is not limited and can be adjusted as needed.
First, terms involved in the embodiments of the present invention are explained.
Baseline version package: a version package that is baseline to execution code deployed on a production environment is referred to as a baseline version package.
And (4) incremental package: when there is a need for a change, the production needs to be version upgraded, and the execution code that needs incremental deployment is called a baseline-based incremental package.
Increment group packaging: and comparing the difference between the current version package and the baseline version package, keeping changed or newly added files, marking deleted files, and generating a difference file list called increment package.
Incremental deployment: based on the difference file list, files of the incremental package are additionally deployed in the production environment, a new amount of files are directly deployed, changed files replace original files, deleted files are marked to be deleted in the production environment, incremental deployment is completed, and version upgrading is completed.
Fig. 1 is a first flowchart of an incremental packaging method in an embodiment of the present invention, as shown in fig. 1, including:
step 101, comparing Jar packages in the current version and the baseline version, and searching whether Jar packages with the same name exist; if no Jar package with the same name exists, the step 102 is carried out, and if the Jar package with the same name exists, the step 103 is carried out;
102, updating and deleting a Jar list and a new Jar list based on Jar packages with different names;
103, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name;
and 104, performing incremental packaging on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate an incremental package of the current version.
In the embodiment of the invention, automatic increment group package can be realized, and the problem caused by Jar packages in the increment group package is solved.
In step 101, comparing the Jar packages in the current version and the baseline version, and searching whether Jar packages with the same name exist.
Fig. 2 is a flowchart of a method for incremental packaging according to an embodiment of the present invention, which in an embodiment, before comparing Jar packages in the current version and the baseline version, further includes:
step 201, deleting the version number of the current version.
In the above embodiment, the version number is removed to find whether Jar with different version numbers exists in the reference version, and if yes, decompression is performed, and difference comparison is performed, so that the problem of version number change due to upgrading can be solved.
In step 102, the deleted Jar list and the added Jar list are updated based on Jar packages of different names.
In one embodiment, updating the deleted Jar list and the added Jar list based on Jar packages with different names comprises:
if the baseline version has Jar packages which do not exist in the current version, recording the Jar packages which do not exist in the current version into a deleted Jar list;
and if the Jar packages not in the baseline version exist in the current version, recording the Jar packages not in the baseline version into the newly-added Jar list.
In the above embodiment, after the Jar package that the current version does not have is recorded in the deleted Jar list, the total Jar number num1+1 is deleted; and after the Jar packages which are not in the baseline version are recorded in a newly-added Jar list, the total number num2+1 of the newly-added Jar packages is counted, so that version checking is facilitated.
In step 103, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; and comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name.
In one embodiment, the change Jar list includes a deleted file list, an added file list, and a modified file list;
comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name, wherein the updating comprises the following steps:
if the second directory has files which are not in the first directory, recording the files which are not in the first directory into a deleted file list;
if the first directory has files which are not in the second directory, recording the files which are not in the second directory into a newly added file list;
if the files with the same name exist in the first directory and the second directory, comparing the md5 values of the two files with the same name, and if the md5 values of the two files with the same name are not equal, recording the files with the same name in the first directory into a modified file list.
In the above embodiment, if files that are not in the first directory are recorded in the deleted file list, the total number num3+1 of deleted files corresponding to the Jar package; recording files which are not in the second directory into a newly added file list, wherein the number of newly added files num4+1 corresponding to the Jar package is the number of newly added files; and recording the files with the same name in the first directory into a modified file list, wherein the total number num5+1 of the modified files corresponding to the Jar package is obtained.
In step 104, increment packaging is carried out on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name, and an increment package of the current version is generated.
In an embodiment, the incremental packaging of the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name comprises:
the Jar packages in the newly-added Jar list are contained in the increment package;
if the deleted file list and the added file list are empty in the changed Jar list corresponding to the Jar package, and the modified file list only comprises files pom.
And if the deleted file list is not empty, the newly added file list is not empty, or the number of the modified files in the modified file list is not less than 2 in the changed Jar list corresponding to the Jar package, the Jar package is accommodated into the increment package, and the Jar package is recorded into the difference Jar package list.
In the above embodiment, only the files pom.properties are included in the modified file list, but different pom.properties are generated due to different maven construction time points, so that the Jar package is not included in the difference Jar package list. And recording the Jar package into the difference Jar package list, wherein the total number num6+1 of the difference Jar packages.
Fig. 3 is a flowchart of a third method for incremental packaging according to an embodiment of the present invention, where in an embodiment, the method further includes:
step 301, outputting the increment package of the current version, the difference Jar package list, the deletion Jar list and the newly-added Jar list.
The output may further include a total deleted Jar num1, a total added Jar num2, a total difference Jar package num6, and a total deleted files num3, a total added files num4, and a total modified files num5 in each difference Jar package for facilitating subsequent checking.
In summary, in the method provided in the embodiment of the present invention, the Jar packages in the current version and the baseline version are compared to find whether there is a Jar package with the same name; if the Jar packages with the same name do not exist, updating and deleting the Jar list and the newly added Jar list based on the Jar packages with different names; if the Jar package with the same name exists, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name; and performing incremental packaging on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate an incremental package of the current version. In the process, when the Jar package with the same name as the reference version is encountered, the Jar package is decompressed without directly adopting comparison file difference, all files in the two Jar packages are compared, automatic incremental packaging can be realized, and the problem caused by the Jar package in the incremental packaging is solved.
The invention also provides an increment packaging device, the principle of which is the same as that of the increment packaging method, and the details are not repeated.
Fig. 4 is a first schematic diagram of an incremental packaging apparatus according to an embodiment of the present invention, as shown in fig. 4, including:
the corresponding-name Jar package searching module 401 is configured to compare Jar packages in the current version and the baseline version, and search whether a Jar package with the same name exists;
the different-name Jar package processing module 402 is used for updating and deleting the Jar list and adding the Jar list based on the Jar packages with different names if the Jar packages with the same name do not exist;
the corresponding-name Jar packet processing module 403 is configured to decompress the corresponding-name Jar packet in the current version if the corresponding-name Jar packet exists, and obtain a file in the first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name;
and the incremental package generating module 404 is configured to perform incremental package on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name, so as to generate an incremental package of the current version.
Fig. 5 is a second schematic diagram of an incremental packaging apparatus in an embodiment of the present invention, and in an embodiment, the apparatus further includes a version number deleting module 501, configured to:
before comparing the Jar packages in the current version and the baseline version, the version number of the current version is deleted.
In an embodiment, the Jar package processing modules with different names are specifically configured to:
if the baseline version has Jar packages which do not exist in the current version, recording the Jar packages which do not exist in the current version into a deleted Jar list;
and if the Jar packages not in the baseline version exist in the current version, recording the Jar packages not in the baseline version into the newly-added Jar list.
In one embodiment, the change Jar list includes a deleted file list, an added file list, and a modified file list;
the Jar package processing module with the same name is specifically used for:
if the second directory has files which are not in the first directory, recording the files which are not in the first directory into a deleted file list;
if the first directory has files which are not in the second directory, recording the files which are not in the second directory into a newly added file list;
if the files with the same name exist in the first directory and the second directory, comparing the md5 values of the two files with the same name, and if the md5 values of the two files with the same name are not equal, recording the files with the same name in the first directory into a modified file list.
In an embodiment, the incremental package generating module is specifically configured to:
the Jar packages in the newly-added Jar list are contained in the increment package;
if the deleted file list and the added file list are empty in the changed Jar list corresponding to the Jar package, and the modified file list only comprises files pom.
And if the deleted file list is not empty, the newly added file list is not empty, or the number of the modified files in the modified file list is not less than 2 in the changed Jar list corresponding to the Jar package, the Jar package is accommodated into the increment package, and the Jar package is recorded into the difference Jar package list.
Fig. 6 is a third schematic diagram of an incremental packaging apparatus in an embodiment of the present invention, and in an embodiment, the apparatus further includes an output module 601, configured to:
and outputting the increment package of the current version, the difference Jar package list, the deletion Jar list and the newly-added Jar list.
An embodiment of the present invention further provides a computer device, and fig. 7 is a schematic diagram of a computer device in an embodiment of the present invention, where the computer device is capable of implementing all steps in the incremental group packaging method in the foregoing embodiment, and the computer device specifically includes the following contents:
a processor (processor)701, a memory (memory)702, a communication Interface (Communications Interface)703, and a communication bus 704;
the processor 701, the memory 702 and the communication interface 703 complete mutual communication through the communication bus 704; the communication interface 703 is used for implementing information transmission between related devices such as server-side devices, detection devices, and user-side devices;
the processor 701 is configured to call the computer program in the memory 702, and when the processor executes the computer program, the processor implements all the steps in the incremental packaging method in the above embodiments.
An embodiment of the present invention further provides a computer-readable storage medium, which can implement all the steps in the incremental packaging method in the above embodiment, and the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements all the steps of the incremental packaging method in the above embodiment.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (14)

1. An incremental packaging method, comprising:
comparing the Jar packages in the current version and the baseline version, and searching whether the Jar packages with the same name exist or not;
if the Jar packages with the same name do not exist, updating and deleting the Jar list and the newly added Jar list based on the Jar packages with different names;
if the Jar package with the same name exists, decompressing the Jar package with the same name in the current version to obtain a file under a first directory; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name;
and performing incremental packaging on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate an incremental package of the current version.
2. The incremental packaging method of claim 1 further comprising, prior to comparing Jar packages in the current version and the baseline version:
the version number of the current version is deleted.
3. The incremental packaging method of claim 1 wherein updating the delete Jar manifest and the new add Jar manifest based on Jar packages of different names comprises:
if the baseline version has Jar packages which do not exist in the current version, recording the Jar packages which do not exist in the current version into a deleted Jar list;
and if the Jar packages not in the baseline version exist in the current version, recording the Jar packages not in the baseline version into the newly-added Jar list.
4. The incremental packaging method of claim 3 wherein the change Jar manifest includes a delete file list, an add file list, and a modify file list;
comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name, wherein the updating comprises the following steps:
if the second directory has files which are not in the first directory, recording the files which are not in the first directory into a deleted file list;
if the first directory has files which are not in the second directory, recording the files which are not in the second directory into a newly added file list;
if the files with the same name exist in the first directory and the second directory, comparing the md5 values of the two files with the same name, and if the md5 values of the two files with the same name are not equal, recording the files with the same name in the first directory into a modified file list.
5. The incremental packaging method of claim 4, wherein the incremental packaging of the current version based on the deleted Jar list and the newly added Jar list, and the changed Jar list corresponding to each Jar with the same name comprises:
the Jar packages in the newly-added Jar list are contained in the increment package;
if the deleted file list and the added file list are empty in the changed Jar list corresponding to the Jar package, and the modified file list only comprises files pom.
And if the deleted file list is not empty, the newly added file list is not empty, or the number of the modified files in the modified file list is not less than 2 in the changed Jar list corresponding to the Jar package, the Jar package is accommodated into the increment package, and the Jar package is recorded into the difference Jar package list.
6. The incremental packaging method of claim 5 further comprising:
and outputting the increment package of the current version, the difference Jar package list, the deletion Jar list and the newly-added Jar list.
7. An incremental group packing apparatus, comprising:
the same-name Jar package searching module is used for comparing Jar packages in the current version and the baseline version and searching whether the Jar packages with the same name exist or not;
the different-name Jar package processing module is used for updating and deleting the Jar list and adding the Jar list based on the Jar packages with different names if the Jar packages with the same name do not exist;
the same-name Jar package processing module is used for decompressing the same-name Jar package in the current version to obtain a file under a first directory if the same-name Jar package exists; decompressing the Jar packages with the same name in the baseline version to obtain files under a second directory; comparing the files in the first directory with the files in the second directory, and updating the changed Jar list corresponding to the Jar package with the same name;
and the increment package generating module is used for performing increment package on the current version according to the deleted Jar list, the newly added Jar list and the changed Jar list corresponding to each Jar with the same name to generate the increment package of the current version.
8. The delta packaging apparatus as set forth in claim 7, further comprising a version number delete module for:
before comparing the Jar packages in the current version and the baseline version, the version number of the current version is deleted.
9. The incremental packaging apparatus of claim 7, wherein the different-name Jar package processing module is specifically configured to:
if the baseline version has Jar packages which do not exist in the current version, recording the Jar packages which do not exist in the current version into a deleted Jar list;
and if the Jar packages not in the baseline version exist in the current version, recording the Jar packages not in the baseline version into the newly-added Jar list.
10. The incremental packaging apparatus of claim 9 wherein the change Jar manifest includes a deleted files list, an added files list, and a modified files list;
the Jar package processing module with the same name is specifically used for:
if the second directory has files which are not in the first directory, recording the files which are not in the first directory into a deleted file list;
if the first directory has files which are not in the second directory, recording the files which are not in the second directory into a newly added file list;
if the files with the same name exist in the first directory and the second directory, comparing the md5 values of the two files with the same name, and if the md5 values of the two files with the same name are not equal, recording the files with the same name in the first directory into a modified file list.
11. The incremental packaging apparatus of claim 10, wherein the incremental package generation module is specifically configured to:
the Jar packages in the newly-added Jar list are contained in the increment package;
if the deleted file list and the added file list are empty in the changed Jar list corresponding to the Jar package, and the modified file list only comprises files pom.
And if the deleted file list is not empty, the newly added file list is not empty, or the number of the modified files in the modified file list is not less than 2 in the changed Jar list corresponding to the Jar package, the Jar package is accommodated into the increment package, and the Jar package is recorded into the difference Jar package list.
12. The incremental packaging apparatus of claim 11 further comprising an output module for:
and outputting the increment package of the current version, the difference Jar package list, the deletion Jar list and the newly-added Jar list.
13. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 6 when executing the computer program.
14. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 6.
CN202111178019.1A 2021-10-09 2021-10-09 Increment packaging method and device Pending CN113805930A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111178019.1A CN113805930A (en) 2021-10-09 2021-10-09 Increment packaging method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111178019.1A CN113805930A (en) 2021-10-09 2021-10-09 Increment packaging method and device

Publications (1)

Publication Number Publication Date
CN113805930A true CN113805930A (en) 2021-12-17

Family

ID=78897496

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111178019.1A Pending CN113805930A (en) 2021-10-09 2021-10-09 Increment packaging method and device

Country Status (1)

Country Link
CN (1) CN113805930A (en)

Similar Documents

Publication Publication Date Title
US7644111B2 (en) Framework for content representation and delivery
CN106897103B (en) Method for quickly and thermally updating version of mobile terminal network game
CN113114749B (en) Hash chain construction and file data synchronization method, device and system
CN111324359A (en) Plug-in deployment method and device
CN110543427B (en) Test case storage method and device, electronic equipment and storage medium
CN111932207A (en) Project data processing method and device, computer equipment and storage medium
CN112451972A (en) Game engine-based resource compression package construction method, device, system and medium
CN110083372B (en) Block chain data version upgrading method
CN114564227A (en) Application program updating method and device, electronic equipment and storage medium
CN113515303B (en) Project transformation method, device and equipment
US11675772B2 (en) Updating attributes in data
WO2019041891A1 (en) Method and device for generating upgrade package
CN113805930A (en) Increment packaging method and device
CN115562686A (en) Lightweight packaging method, system, terminal and storage medium for Springboot project
CN111736889B (en) Version increment file acquisition method and device
CN113342378B (en) Mirror image generation method, device and medium based on file system update
CN116599946A (en) Thermal updating method and device based on real Native, intelligent device and storage medium
CN116647447A (en) Application program hot update method and device, intelligent device and storage medium
CN116243965A (en) Incremental code grouping method, device, electronic equipment and storage medium
CN108932263B (en) Associated object tracking method and device
CN108228225B (en) Differential packet generation method and device and corresponding terminal
CN113821222A (en) Method and device for generating original OTA packet
CN113741903A (en) Automatic product packaging method and system
CN116089387A (en) Resource allocation method, apparatus, electronic device, readable medium and program product
CN114077438A (en) Version synchronization method, gitlab server and test server

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination