CN113553088A - Patch package distribution method and device, computer equipment and storage medium - Google Patents
Patch package distribution method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN113553088A CN113553088A CN202110719461.4A CN202110719461A CN113553088A CN 113553088 A CN113553088 A CN 113553088A CN 202110719461 A CN202110719461 A CN 202110719461A CN 113553088 A CN113553088 A CN 113553088A
- Authority
- CN
- China
- Prior art keywords
- patch
- package
- engineering
- server
- configuration management
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000010354 integration Effects 0.000 claims abstract description 84
- 238000012360 testing method Methods 0.000 claims abstract description 73
- 230000002085 persistent effect Effects 0.000 claims description 26
- 238000004806 packaging method and process Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 8
- 238000010276 construction Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- 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/77—Software metrics
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application relates to a method and a device for distributing a patch package, computer equipment and a storage medium. The method comprises the following steps: acquiring a patch script code sent by a terminal and engineering information corresponding to the patch script code; sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server; acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. The method can ensure the quality of the issued patch package.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for distributing a patch package, a computer device, and a storage medium.
Background
A patch is a problem solving applet that is issued to a problem exposed during use of a large software system. The developers cannot write programs in perfect perfection, so that the software cannot avoid BUGs, and patches are specially made for repairing the BUGs. The originally released software has defects, and after the defects are discovered, a small program needs to be compiled to be perfect, and the small program is a patch. The patch may be released after it is made by the original author of the software. In the traditional technology, developed patch script codes are directly packaged and released only through a continuous construction tool, and an auditing and releasing mechanism is lacked, so that the quality of a released patch package cannot be guaranteed.
Disclosure of Invention
In view of the above, it is necessary to provide a patch package distribution method, apparatus, computer device, and storage medium capable of ensuring the quality of a distributed patch package in order to solve the above-described technical problems.
A patch package release method is applied to an approval server and comprises the following steps:
acquiring a patch script code sent by a terminal and engineering information corresponding to the patch script code;
sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server;
acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information;
testing the patch package;
and if the test is passed, informing the configuration management server to release the patch package.
In one embodiment, after the patch script code sent by the terminal and the engineering information corresponding to the patch script code are obtained, the method further includes:
and generating a patch record based on the patch script code and the engineering information, and sending the patch record to the configuration management server.
In one embodiment, after the patch script code sent by the terminal and the engineering information corresponding to the patch script code are obtained, the method further includes:
and analyzing the patch script codes, and sending the analyzed patch script codes to the configuration management server so as to instruct the configuration management server to forward the analyzed patch script codes to a file storage server according to a path corresponding to the engineering information.
In one embodiment, the obtaining of the patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information includes:
and acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information from a file storage server according to a path corresponding to the engineering information.
In one embodiment, if the test passes, notifying the configuration management server to release the patch package includes:
if the test is passed, modifying the state of the patch package from a hidden state to a display state;
and sending the state information carrying the display state of the patch package to the configuration management server so as to instruct the configuration management server to release the patch package based on the state information.
A patch package releasing device is applied to an approval server and comprises the following components:
the first acquisition module is used for acquiring the patch script code sent by the terminal and the engineering information corresponding to the patch script code;
the first sending module is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information and send the patch data to a continuous integration server;
the first obtaining module is further configured to obtain a patch package generated by the persistent integration server based on the patch data, the patch script code, and an engineering package corresponding to the engineering information;
the test module is used for testing the patch package;
and the notification module is used for notifying the configuration management server to release the patch package if the test is passed.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring a patch script code sent by a terminal and engineering information corresponding to the patch script code;
sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server;
acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information;
testing the patch package;
and if the test is passed, informing the configuration management server to release the patch package.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
acquiring a patch script code sent by a terminal and engineering information corresponding to the patch script code;
sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server;
acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information;
testing the patch package;
and if the test is passed, informing the configuration management server to release the patch package.
The patch package publishing method, the device, the computer equipment and the storage medium obtain the patch script codes sent by the terminal and the engineering information corresponding to the patch script codes; sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server; acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. Therefore, the patch script codes are automatically packaged by the continued integration server to obtain the patch package, and the examination and approval server and the configuration management server are combined to carry out standardized unified management and test on the patch package, so that the quality of the issued patch package is ensured.
A method for releasing a patch package is applied to a terminal, and comprises the following steps:
acquiring a patch script code and engineering information corresponding to the patch script code;
sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
In one embodiment, before the obtaining of the patch script code and the engineering information corresponding to the patch script code, the method further includes:
acquiring an engineering code corresponding to the engineering information;
and sending the engineering code to a code hosting server to instruct the code hosting server to generate a packaging instruction, and sending the packaging instruction to a continuous integration server, wherein the continuous integration server is used for acquiring the engineering code from the code hosting server based on the packaging instruction, generating an engineering package corresponding to the engineering information based on the engineering code, and sending the engineering package to a file storage server.
A device for distributing a patch package is applied to a terminal, and comprises:
the second acquisition module is used for acquiring the patch script codes and the engineering information corresponding to the patch script codes;
the second sending module is used for sending the patch script codes and the engineering information to an approval server, and the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information and send the patch data to a continuous integration server so as to obtain patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring a patch script code and engineering information corresponding to the patch script code;
sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
acquiring a patch script code and engineering information corresponding to the patch script code;
sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
According to the patch package publishing method, the device, the computer equipment and the storage medium, the patch script codes and the engineering information corresponding to the patch script codes are obtained; sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. Therefore, the patch script codes are automatically packaged by the continued integration server to obtain the patch package, and the examination and approval server and the configuration management server are combined to carry out standardized unified management and test on the patch package, so that the quality of the issued patch package is ensured.
Drawings
FIG. 1 is a diagram illustrating an exemplary implementation of a method for distributing patch packages;
FIG. 2 is a flowchart illustrating a method for distributing a patch package in one embodiment;
FIG. 3 is a flowchart illustrating a method for distributing a patch package according to another embodiment;
FIG. 4 is a diagram of an application scenario of a method for distributing a patch package in another embodiment;
FIG. 5 is a timing diagram illustrating the distribution of a patch package in one embodiment;
FIG. 6 is a block diagram showing the configuration of a patch package distribution apparatus according to one embodiment;
FIG. 7 is a block diagram showing the construction of a patch package distribution apparatus according to another embodiment;
FIG. 8 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The patch package publishing method provided by the application can be applied to the application environment shown in fig. 1. The application environment includes a terminal 102, an approval server 104, a configuration management server 106, and a persistent integration server 108. The terminal 102 may specifically include a desktop terminal or a mobile terminal. The mobile terminal may specifically include at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The approval server 104, the configuration management server 106, and the persistent integration server 108 may each be implemented as a stand-alone server or as a server cluster of multiple servers. Those skilled in the art will understand that the application environment shown in fig. 1 is only a part of the scenario related to the present application, and does not constitute a limitation to the application environment of the present application.
The approval server 104 may obtain the patch script code sent by the terminal 102 and the engineering information corresponding to the patch script code; sending the engineering information to the configuration management server 106 to instruct the configuration management server 106 to generate patch data corresponding to the engineering information, and sending the patch data to the persistent integration server 108; acquiring a patch package generated by the continuous integration server 108 based on the patch data, the patch script code and the engineering package corresponding to the engineering information; testing the patch package; if the test passes, configuration management server 106 is notified to release the patch package.
In one embodiment, as shown in fig. 2, a method for distributing a patch package is provided, which is described by taking the method as an example for being applied to the approval server 104 in fig. 1, and includes the following steps:
s202, obtaining the patch script code sent by the terminal and the engineering information corresponding to the patch script code.
Wherein the patch script code is the code of the applet that addresses the software system bug. The project information corresponding to the patch script code is information of the project to which the patch script code belongs. The engineering information may specifically include at least one of an engineering code, an engineering type, an engineering configuration parameter, and the like.
Specifically, the terminal may download an approval form from the approval server, and the developer may write a patch script code and fill in engineering information corresponding to the patch script code in the approval form based on the terminal. The terminal can obtain the patch script codes and the engineering information corresponding to the patch script codes, and sends the patch script codes and the engineering information corresponding to the patch script codes to the approval server. Furthermore, the approval server can receive the patch script code and the engineering information corresponding to the patch script code transmitted by the terminal.
And S204, transmitting the engineering information to the configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and transmitting the patch data to the continuous integration server.
The patch data is basic data necessary for making a patch package, and it can be understood that the patch data is a patch package object.
Specifically, the approval server may send the engineering information to the configuration management server. The configuration management server may generate patch data corresponding to the engineering information, i.e., create a patch package object corresponding to the engineering information, and further, the configuration management server may transmit the patch data to the persistent integration server.
S206, obtaining a patch package generated by the continuous integration server based on the patch data, the patch script codes and the engineering package corresponding to the engineering information.
Specifically, the persistent integration server may receive patch data sent by the configuration management server and obtain patch script codes and an engineering package corresponding to the engineering information. The persistent integration server may then generate a patch package based on the patch data, the patch script code, and the engineering package corresponding to the engineering information. Further, the approval server may obtain a patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information.
And S208, testing the patch package.
In particular, the approval server may deploy and test the patch package. It is understood that the testing of the patch package is performed to ensure the quality of the patch package.
And S210, if the test is passed, informing the configuration management server to release the patch package.
Specifically, if the test of the patch package passes, it indicates that the quality of the patch package is qualified, and at this time, the approval server may notify the configuration management server to release the patch package. It will be appreciated that after the patch package is released, the user may download and install the patch package from the corresponding website.
In the patch package release method, the patch script codes sent by the terminal and the engineering information corresponding to the patch script codes are obtained; sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server; acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. Therefore, the patch script codes are automatically packaged by the continued integration server to obtain the patch package, and the examination and approval server and the configuration management server are combined to carry out standardized unified management and test on the patch package, so that the quality of the issued patch package is ensured.
In an embodiment, after the step S202, that is, after the step of acquiring the patch script code and the engineering information corresponding to the patch script code, the method for distributing the patch package further includes: and generating a patch record based on the patch script code and the engineering information, and sending the patch record to a configuration management server.
The patch record is information for recording operation related to the patch.
Specifically, the approval server may generate a corresponding patch record based on the patch script code and the engineering information, and send the patch record to the configuration management server.
In the above embodiment, the tracking of the operation related to the patch is realized through the patch record, so as to facilitate the subsequent tracing of the copy.
In an embodiment, after the step S202, that is, after the step of acquiring the patch script code and the engineering information corresponding to the patch script code, the method for distributing the patch package further includes: and analyzing the patch script codes, and sending the analyzed patch script codes to the configuration management server to instruct the configuration management server to forward the analyzed patch script codes to the file storage server according to a path corresponding to the engineering information.
Specifically, the approval server may parse the patch script code and send the parsed patch script code to the configuration management server. The configuration management server can receive the analyzed patch script codes sent by the approval server and forward the analyzed patch script codes to the file storage server according to the path corresponding to the engineering information. Alternatively, the path corresponding to the engineering information may be specifically a version/product/field/engineering.
In the above embodiment, the analyzed patch script codes are stored in the file storage server, so that unified management of the patch script codes can be facilitated, meanwhile, storage spaces of the approval server and the configuration management server can be saved, and service performance of the approval server and the configuration management server can be improved.
In an embodiment, the step S206, that is, the step of obtaining the patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information specifically includes: and acquiring a patch package generated by the continuous integration server based on the patch data, the patch script codes and the engineering package corresponding to the engineering information from the file storage server according to the path corresponding to the engineering information.
Specifically, the persistent integration server may generate a patch package based on the patch data, the patch script code, and the engineering package corresponding to the engineering information, and may transmit the patch package to the file storage server for storage according to a path corresponding to the engineering information. Further, the approval server may acquire, from the file storage server, a patch package generated by the persistent integration server based on the patch data, the patch script code, and the project package corresponding to the project information, according to the path corresponding to the project information. Alternatively, the path corresponding to the engineering information may be specifically a version/product/field/engineering.
In the embodiment, the patch package is stored in the file storage server, so that the uniform management of the patch package can be facilitated, meanwhile, the storage space of the approval server and the configuration management server can be saved, and the service performance of the approval server and the configuration management server can be improved.
In an embodiment, step S210, that is, if the test passes, the step of notifying the configuration management server to issue the patch package specifically includes: if the test is passed, modifying the state of the patch package from a hidden state to a displayed state; and sending the state information carrying the display state of the patch package to a configuration management server to indicate the configuration management server to release the patch package based on the state information.
The hidden state is that the patch package is in an invisible state, and the display state is that the patch package is in a visible state.
Specifically, if the quality test of the patch package passes, the approval server may modify the state of the patch package from a hidden state to a displayed state, and generate state information carrying the displayed state of the patch package. Furthermore, the approval server can send the state information carrying the display state of the patch package to the configuration management server. The configuration management server can receive the state information which is sent by the approval server and carries the display state of the patch package, and the patch package is released based on the state information.
In the above embodiment, the quality of the patch package is tested, and the patch package is released only when the test is passed, so as to ensure the quality of the patch package.
In an embodiment, as shown in fig. 3, a method for distributing a patch package is provided, which is described by taking the method as an example applied to the terminal 102 in fig. 1, and includes the following steps:
s302, obtaining the patch script codes and the engineering information corresponding to the patch script codes.
Specifically, the terminal may download an approval form from the approval server, and the developer may write a patch script code and fill in engineering information corresponding to the patch script code in the approval form based on the terminal. The terminal can obtain the patch script codes and the engineering information corresponding to the patch script codes.
S304, sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
Specifically, the terminal may send the patch script code and the engineering information corresponding to the patch script code to the approval server. Furthermore, the approval server can receive the patch script code and the engineering information corresponding to the patch script code transmitted by the terminal. The approval server may send the engineering information to the configuration management server. The configuration management server may generate patch data corresponding to the engineering information, i.e., create a patch package object corresponding to the engineering information, and further, the configuration management server may transmit the patch data to the persistent integration server. The persistent integration server may receive patch data sent by the configuration management server and obtain patch script codes and an engineering package corresponding to the engineering information. The persistent integration server may then generate a patch package based on the patch data, the patch script code, and the engineering package corresponding to the engineering information. Further, the approval server may obtain a patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information. The approval server may deploy and test the patch package. It is understood that the testing of the patch package is performed to ensure the quality of the patch package. If the test of the patch package passes, the quality of the patch package is qualified, and at this time, the approval server can inform the configuration management server to release the patch package. It will be appreciated that after the patch package is released, the user may download and install the patch package from the corresponding website.
In the patch package release method, the patch script codes and the engineering information corresponding to the patch script codes are obtained; sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. Therefore, the patch script codes are automatically packaged by the continued integration server to obtain the patch package, and the examination and approval server and the configuration management server are combined to carry out standardized unified management and test on the patch package, so that the quality of the issued patch package is ensured.
In an embodiment, before the step S302, that is, before the step of obtaining the patch script code and the engineering information corresponding to the patch script code, the method for distributing the patch package further includes: acquiring an engineering code corresponding to the engineering information; and sending the engineering code to a code hosting server to instruct the code hosting server to generate a packaging instruction, and sending the packaging instruction to a continuous integration server, wherein the continuous integration server is used for acquiring the engineering code from the code hosting server based on the packaging instruction, generating an engineering package corresponding to the engineering information based on the engineering code, and sending the engineering package to a file storage server.
Wherein the engineering code is implementation code of the software system.
Specifically, the developer can write engineering codes corresponding to the engineering information based on the terminal, and the terminal can acquire the engineering codes corresponding to the engineering information and send the engineering codes to the code hosting server. The code hosting server can receive the engineering codes sent by the terminal, generate a packaging instruction based on the engineering codes, and send the packaging instruction to the continuous integration server. The continuous integration server can receive a packaging instruction sent by the continuous integration server, acquire the engineering code from the code hosting server based on the packaging instruction, further generate an engineering package corresponding to the engineering information based on the engineering code, and send the engineering package to the file storage server.
Optionally, when the developer writes the engineering code corresponding to the engineering information based on the terminal, the developer may also perform corresponding configuration on the engineering code to obtain corresponding configuration information. The terminal may send the engineering code and corresponding configuration information together to the code hosting server.
In the above embodiment, the engineering code is automatically packaged through the continuous integration server to obtain the engineering package, so that the manual packaging by developers is avoided, and the packaging efficiency of the engineering package is improved.
In an embodiment, as shown in fig. 4 and 5, the terminal may upload the engineering code of the software system to a gitlab (code hosting warehouse), the gitlab may trigger jenkins (persistent integration tool) to construct, and then the jenkins may pull the engineering code from the gitlab to package, obtain an engineering package, and send the engineering package to the file storage server for storage. When a software system has a bug, the terminal can obtain the patch script code and the corresponding engineering information, and send the patch script code and the corresponding engineering information to the approval server, the approval server can generate a corresponding patch record, analyze the patch script code, and send the analyzed patch script code and the analyzed engineering information to the configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, and send the analyzed patch script code to the file storage server for storage. The configuration management server can manage basic metadata information of the software system, including version, attribution product, attribution field and engineering basic information. jenkins can acquire patch data from a configuration management server, acquire an engineering package and a corresponding patch script code from a file storage server, make a patch package based on the patch data, the engineering package and the corresponding patch script code, and send the patch package to the file storage server. The approval server can pull the patch package from the file storage server, deploy and test the patch package, and if the patch package passes the test, modify the state of the patch and inform the configuration management server to release the patch package.
It should be understood that although the various steps of fig. 2 and 3 are shown sequentially in order, these steps are not necessarily performed sequentially in order. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2 and 3 may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 6, there is provided a patch package issuing apparatus 600 including: a first obtaining module 601, a first sending module 602, a testing module 603 and a notifying module 604, wherein:
the first obtaining module 601 is configured to obtain a patch script code sent by a terminal and engineering information corresponding to the patch script code.
A first sending module 602, configured to send the engineering information to the configuration management server, so as to instruct the configuration management server to generate patch data corresponding to the engineering information, and send the patch data to the persistent integration server.
The first obtaining module 601 is further configured to obtain a patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information.
The testing module 603 is configured to test the patch package.
And a notification module 604, configured to notify the configuration management server to release the patch package if the test is passed.
In one embodiment, the first sending module 602 is further configured to generate a patch record based on the patch script code and the engineering information, and send the patch record to the configuration management server.
In an embodiment, the first sending module 602 is further configured to parse the patch script code and send the parsed patch script code to the configuration management server, so as to instruct the configuration management server to forward the parsed patch script code to the file storage server according to a path corresponding to the engineering information.
In one embodiment, the first obtaining module 601 is further configured to obtain, from the file storage server, a patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information according to a path corresponding to the engineering information.
In one embodiment, the notification module 604 is further configured to modify the state of the patch package from a hidden state to a displayed state if the test passes; and sending the state information carrying the display state of the patch package to a configuration management server to indicate the configuration management server to release the patch package based on the state information.
The patch package releasing device acquires the patch script codes sent by the terminal and the engineering information corresponding to the patch script codes; sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server; acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. Therefore, the patch script codes are automatically packaged by the continued integration server to obtain the patch package, and the examination and approval server and the configuration management server are combined to carry out standardized unified management and test on the patch package, so that the quality of the issued patch package is ensured.
In one embodiment, as shown in fig. 7, there is provided a patch package issuing apparatus 700 including: a second obtaining module 701 and a second sending module 702, wherein:
the second obtaining module 701 is configured to obtain the patch script code and the engineering information corresponding to the patch script code.
A second sending module 702, configured to send the patch script code and the engineering information to an approval server, where the approval server is configured to send the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and send the patch data to a persistent integration server, so as to obtain a patch package generated by the persistent integration server based on the patch data, the patch script code, and an engineering package corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
In one embodiment, the second obtaining module 701 is further configured to obtain an engineering code corresponding to the engineering information. The second sending module 702 is further configured to send the engineering code to the code hosting server, so as to instruct the code hosting server to generate a packaging instruction, and send the packaging instruction to the persistent integration server, where the persistent integration server is configured to obtain the engineering code from the code hosting server based on the packaging instruction, generate an engineering package corresponding to the engineering information based on the engineering code, and send the engineering package to the file storage server.
The patch package releasing device acquires the patch script codes and the engineering information corresponding to the patch script codes; sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package. Therefore, the patch script codes are automatically packaged by the continued integration server to obtain the patch package, and the examination and approval server and the configuration management server are combined to carry out standardized unified management and test on the patch package, so that the quality of the issued patch package is ensured.
For the specific limitations of the patch package distribution device, reference may be made to the above limitations of the patch package distribution method, which will not be described herein again. The modules in the patch package issuing device may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be the approval server 104 of FIG. 1, and its internal structure diagram may be as shown in FIG. 8. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing patch package distribution data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of patch package distribution.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the patch distribution method described above. Here, the steps of the patch package distribution method may be the steps in the patch package distribution method of each of the above embodiments.
In one embodiment, a computer readable storage medium is provided, storing a computer program that, when executed by a processor, causes the processor to perform the steps of the patch distribution method described above. Here, the steps of the patch package distribution method may be the steps in the patch package distribution method of each of the above embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A patch package release method is applied to an approval server, and comprises the following steps:
acquiring a patch script code sent by a terminal and engineering information corresponding to the patch script code;
sending the engineering information to a configuration management server to instruct the configuration management server to generate patch data corresponding to the engineering information, and sending the patch data to a continuous integration server;
acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information;
testing the patch package;
and if the test is passed, informing the configuration management server to release the patch package.
2. The method according to claim 1, wherein after the obtaining of the patch script code sent by the terminal and the engineering information corresponding to the patch script code, the method further comprises:
and generating a patch record based on the patch script code and the engineering information, and sending the patch record to the configuration management server.
3. The method according to claim 1, wherein after the obtaining of the patch script code sent by the terminal and the engineering information corresponding to the patch script code, the method further comprises:
and analyzing the patch script codes, and sending the analyzed patch script codes to the configuration management server so as to instruct the configuration management server to forward the analyzed patch script codes to a file storage server according to a path corresponding to the engineering information.
4. The method of claim 1, wherein obtaining the patch package generated by the persistent integration server based on the patch data, the patch script code, and the engineering package corresponding to the engineering information comprises:
and acquiring a patch package generated by the continuous integration server based on the patch data, the patch script code and the engineering package corresponding to the engineering information from a file storage server according to a path corresponding to the engineering information.
5. The method of claim 1, wherein notifying the configuration management server to release the patch package if the test passes comprises:
if the test is passed, modifying the state of the patch package from a hidden state to a display state;
and sending the state information carrying the display state of the patch package to the configuration management server so as to instruct the configuration management server to release the patch package based on the state information.
6. A method for releasing a patch package is applied to a terminal, and comprises the following steps:
acquiring a patch script code and engineering information corresponding to the patch script code;
sending the patch script codes and the engineering information to an approval server, wherein the approval server is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information, sending the patch data to a continuous integration server, and acquiring patch packages generated by the continuous integration server based on the patch data, the patch script codes and the engineering packages corresponding to the engineering information; testing the patch package; and if the test is passed, informing the configuration management server to release the patch package.
7. The method of claim 6, wherein before obtaining the patch script code and the engineering information corresponding to the patch script code, the method further comprises:
acquiring an engineering code corresponding to the engineering information;
and sending the engineering code to a code hosting server to instruct the code hosting server to generate a packaging instruction, and sending the packaging instruction to a continuous integration server, wherein the continuous integration server is used for acquiring the engineering code from the code hosting server based on the packaging instruction, generating an engineering package corresponding to the engineering information based on the engineering code, and sending the engineering package to a file storage server.
8. A patch package issuing device is applied to an approval server, and comprises:
the first acquisition module is used for acquiring the patch script code sent by the terminal and the engineering information corresponding to the patch script code;
the first sending module is used for sending the engineering information to a configuration management server so as to instruct the configuration management server to generate patch data corresponding to the engineering information and send the patch data to a continuous integration server;
the first obtaining module is further configured to obtain a patch package generated by the persistent integration server based on the patch data, the patch script code, and an engineering package corresponding to the engineering information;
the test module is used for testing the patch package;
and the notification module is used for notifying the configuration management server to release the patch package if the test is passed.
9. 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 steps of the method of any of claims 1 to 7 are implemented by the processor when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110719461.4A CN113553088A (en) | 2021-06-28 | 2021-06-28 | Patch package distribution method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110719461.4A CN113553088A (en) | 2021-06-28 | 2021-06-28 | Patch package distribution method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113553088A true CN113553088A (en) | 2021-10-26 |
Family
ID=78131016
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110719461.4A Pending CN113553088A (en) | 2021-06-28 | 2021-06-28 | Patch package distribution method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113553088A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978938A (en) * | 2022-05-26 | 2022-08-30 | 西安易朴通讯技术有限公司 | Switch testing method, system and equipment |
| CN115348272A (en) * | 2022-08-15 | 2022-11-15 | 四川虹美智能科技有限公司 | Automatic synchronization method and device for server output |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104536745A (en) * | 2014-12-19 | 2015-04-22 | 用友金融信息技术有限公司 | Task modification method and device |
| US20160019043A1 (en) * | 2014-07-15 | 2016-01-21 | Oracle International Corporation | Automatic generation and execution of server update processes |
| CN107463375A (en) * | 2017-07-18 | 2017-12-12 | 上海斐讯数据通信技术有限公司 | A kind of method and system for detecting source code |
| CN112231212A (en) * | 2020-10-16 | 2021-01-15 | 湖南皖湘科技有限公司 | Method for detecting syntax error of program code |
-
2021
- 2021-06-28 CN CN202110719461.4A patent/CN113553088A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160019043A1 (en) * | 2014-07-15 | 2016-01-21 | Oracle International Corporation | Automatic generation and execution of server update processes |
| CN104536745A (en) * | 2014-12-19 | 2015-04-22 | 用友金融信息技术有限公司 | Task modification method and device |
| CN107463375A (en) * | 2017-07-18 | 2017-12-12 | 上海斐讯数据通信技术有限公司 | A kind of method and system for detecting source code |
| CN112231212A (en) * | 2020-10-16 | 2021-01-15 | 湖南皖湘科技有限公司 | Method for detecting syntax error of program code |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978938A (en) * | 2022-05-26 | 2022-08-30 | 西安易朴通讯技术有限公司 | Switch testing method, system and equipment |
| CN115348272A (en) * | 2022-08-15 | 2022-11-15 | 四川虹美智能科技有限公司 | Automatic synchronization method and device for server output |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109460527B (en) | Product data configuration method, device, computer equipment and storage medium | |
| WO2020253061A1 (en) | Page generating method and apparatus, computer device, and storage medium | |
| US20200183683A1 (en) | Application architecture generation | |
| CN113553088A (en) | Patch package distribution method and device, computer equipment and storage medium | |
| CN110647471B (en) | Interface test case generation method, electronic device and storage medium | |
| CN108255701B (en) | Scene testing method and mobile terminal | |
| CN108400978B (en) | Vulnerability detection method and device, computer equipment and storage medium | |
| CN111008132B (en) | Application debugging method and device for Android system, computer equipment and storage medium | |
| CN109726134B (en) | Interface test method and system | |
| CN112491659B (en) | Flow playback test method and device, computer equipment and storage medium | |
| CN111475376A (en) | Method and device for processing test data, computer equipment and storage medium | |
| EP3447635A1 (en) | Application architecture generation | |
| CN112637008B (en) | Link simulation test method, device, system, computer equipment and storage medium | |
| CN111078553B (en) | Data development task testing method and device, computer equipment and storage medium | |
| CN110232018A (en) | Interface test method, device, computer equipment | |
| CN111159025B (en) | Application program interface testing method and device, computer equipment and storage medium | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN112540916A (en) | Automatic rerun method and device for failed case, computer equipment and storage medium | |
| CN110865943A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN112486824B (en) | Case code generation method, device, computer equipment and storage medium | |
| CN111083007B (en) | Test method, test device, computer equipment and storage medium | |
| CN108595327B (en) | Method for executing script by application, application testing method, device and computer equipment | |
| CN113868127A (en) | Online debugging method and device, computer equipment and storage medium | |
| CN110737426B (en) | Program block creating method, program block creating device, computer equipment and storage medium | |
| CN114218188A (en) | Data migration method, device, equipment and storage medium |
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 |