CN111124429B - Continuous delivery method and device - Google Patents

Continuous delivery method and device Download PDF

Info

Publication number
CN111124429B
CN111124429B CN201911422465.5A CN201911422465A CN111124429B CN 111124429 B CN111124429 B CN 111124429B CN 201911422465 A CN201911422465 A CN 201911422465A CN 111124429 B CN111124429 B CN 111124429B
Authority
CN
China
Prior art keywords
node server
target installation
installation package
slave node
continuous delivery
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.)
Active
Application number
CN201911422465.5A
Other languages
Chinese (zh)
Other versions
CN111124429A (en
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 CN201911422465.5A priority Critical patent/CN111124429B/en
Publication of CN111124429A publication Critical patent/CN111124429A/en
Application granted granted Critical
Publication of CN111124429B publication Critical patent/CN111124429B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482—Procedural

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The application provides a continuous delivery method and a device, wherein the method is applied to a master node server of a continuous integrated system, and the master node server is provided with a continuous delivery plug-in based on a callback mechanism, and the method comprises the following steps: acquiring target installation package information; calling a continuous delivery plug-in, triggering a slave node server to execute a first callback function through a first calling instruction, and searching a target installation package in the slave node server according to target installation package information; receiving first data returned from the node server and determining whether the target installation package is searched from the node server according to the first data; and when the target installation package is searched from the node server, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform. The scheme can realize that the installation package constructed from the node server is searched in the multi-node task and automatically uploaded to the continuous delivery platform.

Description

Continuous delivery method and device
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a continuous delivery method and apparatus.
Background
Currently, continuous integration and continuous delivery have become important links in software project management. Wherein the continuous integration step is typically performed on a Jenkins et al tool and generates the corresponding deliveries (typically installation packages or deployment packages of software). To implement delivery flows for these deliveries, enterprises typically use specialized persistent delivery platforms to effect deployment delivery of the software product.
Continuous integration on Jenkins is implemented in the form of jobs, both single-node jobs and multi-node jobs. Wherein a single node job can only perform construction at a single designated node, while multiple nodes job can perform construction at multiple nodes in a decentralized manner. Typically, enterprise-level Jenkins persistent integration environments are configured in a multi-node job fashion. After the multi-node job is constructed, a delivery object is generated, and the generated delivery object needs to be automatically pushed to a continuous delivery platform. However, the Jenkins platform and the continuous delivery platform are two relatively independent environments, and a solution capable of automatically pushing generated deliveries to the continuous delivery platform is lacking.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the application provides a continuous delivery method and device, which aims to solve the problem that a scheme capable of automatically pushing generated deliveries to a continuous delivery platform is lacking in the prior art.
The embodiment of the application provides a continuous delivery method, which is applied to a master node server in a continuous integrated system, wherein the master node server is provided with a continuous delivery plug-in based on a callback mechanism, and the continuous integrated system further comprises a slave node server, and the method comprises the following steps: acquiring target installation package information, wherein the target installation package information comprises information of a target installation package constructed in a target task; calling a continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to target installation package information; receiving first data returned by the slave node server through executing a first callback function, and determining whether the slave node server searches for a target installation package according to the first data; and calling the continuous delivery plug-in under the condition that the target installation package is searched from the node server, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform.
In one embodiment, the first callback function is issued in advance by the persistent delivery plug-in and is placed on the slave node server.
In one embodiment, invoking the persistent delivery plug-in, through a first call instruction, triggers the slave node server to execute a first callback function to search for a target installation package in the slave node server according to target installation package information, comprising: verifying the target installation package information; and calling the continuous delivery plug-in under the condition that the information of the target installation package passes the verification, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the information of the target installation package.
In one embodiment, before invoking the persistent delivery plug-in, triggering the slave node server to execute the first callback function by the first call instruction to search the slave node server for the target installation package according to the target installation package information, the method further comprises: acquiring login information of a continuous delivery platform; correspondingly, calling the continuous delivery plug-in, triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information, wherein the method comprises the following steps: calling a continuous delivery plug-in, and triggering the slave node server to execute a third callback function through a third calling instruction so as to log in to a continuous delivery platform according to login information; receiving third data returned by the slave node server for executing a third callback function, and determining whether the slave node server is successfully logged in according to the third data; and under the condition that the login of the slave node server is successful, calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information.
In one embodiment, in a case that it is determined that the target installation package is searched from the node server, calling the persistent delivery plug-in, and triggering the slave node server to execute a second callback function through a second call instruction to upload the target installation package to the persistent delivery platform, including: under the condition that the target installation package is searched from the node server, calling a continuous delivery plug-in, and triggering the node server to execute a fourth callback function through a fourth calling instruction so as to perform format verification on the searched target installation package; receiving fourth data returned from the node server by executing a fourth callback function, and determining whether the target installation package is legal or not according to the fourth data; and under the condition that the target installation package is determined to be legal, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform.
In one embodiment, the target installation package information includes information of a plurality of target installation packages; correspondingly, after the continuous delivery plug-in is called and the second callback function is triggered to be executed from the node server through the second calling instruction so as to upload the target installation package to the continuous delivery platform, the method further comprises the following steps: receiving second data returned by the node server executing the second callback function, and determining whether the uploading of the target installation package is finished or not according to the second data; under the condition that the uploading of the target installation package is determined to be finished, a confirmation request is sent to the continuous delivery platform; receiving information of a target installation package received by a continuous delivery platform, wherein the information is returned by the continuous delivery platform in response to a confirmation request; determining whether uploading of a plurality of target installation packages is successful or not according to information of the target installation packages received by the continuous delivery platform; and under the condition that the plurality of target installation packages are successfully uploaded, generating confirmation information and sending the confirmation information to a continuous delivery platform, wherein the continuous delivery platform responds to the confirmation information to generate version numbers for the installation packages of the plurality of target installation packages and issue the target installation packages of the plurality of target installation packages.
In one embodiment, after determining whether the target installation package is searched from the node server according to the first data, further comprising: in the event that it is determined that the target installation package is not searched from the node server, an error log is generated from the first data.
In one embodiment, the continuous integration system comprises a Jenkins continuous integration system.
The embodiment of the application also provides a continuous delivery device, which is located in a master node server in a continuous integrated system, wherein the master node server is provided with a continuous delivery plug-in based on a callback mechanism, and the continuous integrated system further comprises a slave node server, and the device comprises: the acquisition module is used for acquiring target installation package information, wherein the target installation package information comprises information of a target installation package constructed in a target task; the first calling module is used for calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to the target installation package information; the receiving module is used for receiving first data returned by the slave node server through executing the first callback function and determining whether the slave node server searches for the target installation package according to the first data; and the second calling module is used for calling the continuous delivery plug-in under the condition that the target installation package is searched from the node server, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform.
The embodiment of the application also provides a master node server, which comprises a processor and a memory for storing instructions executable by the processor, wherein the steps of the continuous delivery method described in any embodiment are realized when the instructions are executed by the processor.
Embodiments of the present application also provide a computer readable storage medium having stored thereon computer instructions that when executed implement the steps of the continuous delivery method described in any of the embodiments above.
In an embodiment of the present application, a persistent delivery method is provided, which is applied to a master node server in a persistent integrated system, where the master node server is configured with a persistent delivery plug-in based on a callback mechanism, the persistent integrated system further includes a slave node server, the master node server obtains target installation package information, invokes the persistent delivery plug-in, triggers the slave node server to execute a first callback function according to the target installation package information by a first call instruction, searches the slave node server for the target installation package according to the target installation package information, receives first data returned by the slave node server by executing the first callback function, determines whether the slave node server searches for the target installation package according to the first data, invokes the persistent delivery plug-in when it is determined that the slave node server searches for the target installation package, and triggers the slave node server to execute a second callback function by a second call instruction, so as to upload the target installation package to a persistent delivery platform. In the scheme, the main node server can acquire the target installation package information, and the target installation package information is configured, so that the method can be applied to different continuous integration tasks, different target installation packages can be designated according to different development stages, the functions are rich, and the compatibility is good. In addition, the master node server can trigger the slave node server to execute a first callback function by calling a continuous delivery plug-in based on a callback mechanism and deployed in the continuous delivery plug-in, so that a target installation package can be searched in the slave node server according to target installation package information, and whether the target installation package is searched in the slave node server or not can be determined according to first data returned by the slave node server when executing the first callback function, so that the installation package constructed by the slave node server is searched in a task of multi-node operation and automatically uploaded to a continuous delivery platform, a continuous integration system and the continuous delivery platform can be connected, the continuous delivery efficiency is improved, and a delivery pipeline in a real sense is realized.
Drawings
The accompanying drawings are included to provide a further understanding of the application, and are incorporated in and constitute a part of this application. In the drawings:
FIG. 1 is a schematic diagram of an application scenario of a continuous delivery method according to an embodiment of the present application;
FIG. 2 illustrates a flow chart of a continuous delivery method in an embodiment of the present application;
FIG. 3 illustrates a schematic diagram of a callback mechanism in a persistent delivery plug-in one embodiment of the present application;
FIG. 4 shows a schematic diagram of a continuous delivery apparatus in an embodiment of the present application;
fig. 5 shows a schematic diagram of a master node server in an embodiment of the present application.
Detailed Description
The principles and spirit of the present application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are presented merely to enable one skilled in the art to better understand and practice the present application and are not intended to limit the scope of the present application in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Those skilled in the art will appreciate that embodiments of the present application may be implemented as a system, apparatus device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
The embodiment of the application provides a continuous delivery method which is applied to a master node server in a continuous integrated system, wherein the master node server is provided with a continuous delivery plug-in based on a callback mechanism, and the continuous integrated system further comprises a slave node server. Fig. 1 shows a schematic diagram of an application scenario of a persistent delivery method according to an embodiment of the present application. As shown in fig. 1, the persistent integrated system may include a master node server and a slave node server. By way of illustration and not limitation, one master node server and 3 slave node servers (slave node server 1, slave node server 2, and slave node server 3) are shown in fig. 1. Wherein the master node server and the slave node server are in relation to a certain multi-node persistent integration task (e.g., multi-node job). For a multi-node job, it may generally correspond to a master node server and one or more slave node servers. The multi-node job may be used to construct one or more installation packages, where the one or more installation packages may be used to implement the same or similar functionality, but configured differently. For example, the one or more installation packages may correspond to different environments, one installation package may be used for testing, and another installation package may be used for production. For another example, the one or more installation packages may include different versions of installation packages.
A callback mechanism-based persistent delivery plug-in may be deployed in the primary node server, which may be added to the target persistent integration task in the primary node server. The target persistent integration task may be used to build one or more target installation packages and the persistent delivery plug-in may be used to automatically upload the one or more target installation packages to the persistent delivery platform. Specifically, the master node server may allocate one or more slave node servers to construct one or more installation packages according to the target persistent integration task, and may upload the one or more installation packages constructed from the slave node servers to the persistent delivery platform according to the persistent delivery plug-in.
As shown in fig. 1, the master node server may call the persistent delivery plug-in, trigger the slave node server to execute the callback function by using the call instruction, and after the slave node server executes the callback function, may return an execution result to the master node server. Wherein the master node server may determine whether to perform the next step according to the received return result. The callback function is executed from the node server, so that functions of searching, logging in, uploading and the like can be realized. The searching function refers to searching the target installation package file in the slave node server by the slave node server. The login function refers to logging in from the node server to the persistent delivery platform. The uploading function refers to uploading the constructed installation package from the node server to the continuous delivery platform. For example, the master node server may obtain target installation package information, where the target installation package information includes information of a target installation package constructed in the target task. The master node server may invoke the persistent delivery plug-in, by means of the first invocation instruction, triggering the slave node server 1, the slave node server 2 and the slave node server 3 to execute a first callback function to search for the target installation package in the slave node server 1, the slave node server 2 and the slave node server 3 according to the target installation package information, respectively. The slave node server 1, the slave node server 2 and the slave node server 3 respectively send the first data returned by executing the first callback function to the master node server. The primary node server may determine whether all target installation packages are searched based on the received first data. In the case that all the target installation packages are searched, the master node server calls the persistent delivery plug-in, and through a second call instruction, the slave node server 1, the slave node server 2 and the slave node server 3 are triggered to execute a second callback function so as to upload the searched target installation packages to the persistent delivery platform respectively.
Fig. 2 shows a flowchart of a persistent delivery method in an embodiment of the present application, where the method is applied to a master node server in a persistent integrated system, and the master node server is configured with a persistent delivery plug-in based on a callback mechanism, and the persistent integrated system further includes a slave node server. Although the present application provides a method operation step or apparatus structure as shown in the following examples or figures, more or fewer operation steps or module units may be included in the method or apparatus based on routine or non-inventive labor. In the steps or structures where there is no necessary causal relationship logically, the execution order of the steps or the module structure of the apparatus is not limited to the execution order or the module structure shown in the drawings and described in the embodiments of the present application. The described methods or module structures may be implemented sequentially or in parallel (e.g., in a parallel processor or multithreaded environment, or even in a distributed processing environment) in accordance with the embodiments or the method or module structure connection illustrated in the figures when implemented in a practical device or end product application.
Specifically, as shown in fig. 2, the continuous delivery method provided in one embodiment of the present application may include the following steps:
Step S201, obtaining target installation package information, wherein the target installation package information comprises information of a target installation package constructed in a target task.
The master node server may obtain the target installation package information. The target installation package information may be information of one or more target installation packages input by a developer at a front-end page. The target installation package information may also be included in a preset configuration file. By configuring the target installation package information, the method in the embodiment can be applied to different continuous integration tasks, different target installation packages can be designated according to different development stages, functions are rich, and compatibility is good. Wherein the target installation package information may include a name of the target installation package. The target installation package information may include information of a target installation package constructed in the target task. The target tasks may include target integration tasks, among others.
Step S202, calling a continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to target installation package information.
Specifically, the master node server may invoke the persistent delivery plug-in, and trigger the slave node server to execute the first callback function through the first call instruction. When the slave node server executes the first callback function, the target installation package can be searched in the slave node server according to the target installation package information, and first data obtained by executing the first callback function is returned to the master node server.
Step S203, first data returned from the node server by executing the first callback function is received, and whether the target installation package is searched by the node server is determined according to the first data.
The master node server may receive first data returned from the slave node server by executing the first callback function. The master node server may also determine from the first data whether the slave node server has searched for the target installation package. For example, the first data may be a name of a target installation package searched from the node server, and the master node server may determine whether the target installation package is searched from the node server according to the first data and the target installation package information.
Step S204, calling the continuous delivery plug-in under the condition that the target installation package is searched from the node server, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform.
And under the condition that the slave node server searches the target installation package, the master node server can call the continuous delivery plug-in and trigger the slave node server to execute a second callback function through a second call instruction. And when the slave node executes the second callback function, the searched target installation package can be uploaded to the continuous delivery platform.
In the continuous delivery method in the above embodiment, the master node server may acquire the target installation package information, and by configuring the target installation package information, the method may be applied to different continuous integration tasks, and may further be used to designate different target installation packages according to different development stages, so that the method is rich in functions and good in compatibility. In addition, the master node server can trigger the slave node server to execute a first callback function by calling a continuous delivery plug-in based on a callback mechanism and deployed in the continuous delivery plug-in, so that a target installation package can be searched in the slave node server according to target installation package information, and whether the target installation package is searched in the slave node server or not can be determined according to first data returned by the slave node server when executing the first callback function, so that the installation package constructed by the slave node server is searched in a task of multi-node operation and automatically uploaded to a continuous delivery platform, a continuous integration system and the continuous delivery platform can be connected, the continuous delivery efficiency is improved, and a delivery pipeline in a real sense is realized.
In some embodiments of the present application, the first callback function may be issued in advance by the persistent delivery plug-in and disposed on the slave node server. Specifically, when the target task is executed, the master node server issues the first callback function in the persistent delivery plug-in to the slave node server. Thus, upon receiving the first call instruction from the node server, the first callback function may be executed. In some embodiments of the present application, the second callback function may also be issued in advance by the persistent delivery plug-in and be provided in the slave node server. By the method, the master server can trigger the slave node server to execute the callback function through the callback mechanism, so that the continuous delivery method is realized.
In some embodiments of the present application, invoking the persistent delivery plug-in, through a first call instruction, triggers the slave node server to execute a first callback function to search the slave node server for the target installation package according to the target installation package information, which may include: verifying the target installation package information; and calling the continuous delivery plug-in under the condition that the information of the target installation package passes the verification, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the information of the target installation package.
After the master node server obtains the target installation package information, the target installation package information may be verified. For example, it may be checked whether the file extension in the target installation package information satisfies a preset condition. For example, for an android project, determining whether the extension in the target installation package information is apk; for the IOS item, it is determined whether the extension in the target installation package information is ipa. And calling the continuous delivery plug-in under the condition that the information of the target installation package passes the verification, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the information of the target installation package. For example, in the case where the target installation package information is input by the developer on the front-end page, a hint information may be generated to hint the developer to correct in time if the verification is not passed. According to the method, before the target installation package is searched from the node server, the target installation package information is checked, so that the situation that an error file is searched or the installation package cannot be searched due to the fact that the target installation package information is wrong can be avoided, the searching efficiency and the accuracy rate can be improved, and the continuous delivery efficiency and the accuracy rate are improved.
In some embodiments of the present application, before invoking the persistent delivery plug-in, by the first call instruction, triggering the slave node server to execute the first callback function to search the slave node server for the target installation package according to the target installation package information, the method may further include: acquiring login information of a continuous delivery platform; correspondingly, calling the continuous delivery plug-in, triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information, wherein the method comprises the following steps: calling a continuous delivery plug-in, and triggering the slave node server to execute a third callback function through a third calling instruction so as to log in to a continuous delivery platform according to login information; receiving third data returned by the slave node server for executing a third callback function, and determining whether the slave node server is successfully logged in according to the third data; and under the condition that the login of the slave node server is successful, calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information.
Specifically, the primary node server may obtain login information for the continuous delivery platform. The login information may include information such as a background address, a user name, a password, and the like. After obtaining the login information of the continuous delivery platform, the master node server may call the continuous delivery plug-in, and trigger the slave node server to execute a third callback function through a third call instruction. The slave node server may log into the continuous delivery platform according to the login information when executing the third callback function. The slave node server may also return third data generated by executing a third callback function to the master node server. The master node server may determine whether the slave node server successfully logs in based on the third data. And under the condition that the login of the slave node is successful, calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information. In the above scheme, the subsequent steps of searching, uploading and the like are executed after the continuous delivery platform is successfully logged in, and the login information can be configured so that the slave node server can upload the installation package to a different continuous delivery platform. In the above embodiment, the target installation package is logged in to the continuous delivery platform before being searched from the node server, and in other embodiments, the target installation package may be logged in to the continuous delivery platform before being uploaded after being searched from the node, which is not limited in this application.
In some embodiments of the present application, in a case that it is determined that the target installation package is searched from the node server, invoking the persistent delivery plug-in, and triggering the slave node server to execute the second callback function through the second call instruction to upload the target installation package to the persistent delivery platform may include: under the condition that the target installation package is searched from the node server, calling a continuous delivery plug-in, and triggering the node server to execute a fourth callback function through a fourth calling instruction so as to perform format verification on the searched target installation package; receiving fourth data returned from the node server by executing a fourth callback function, and determining whether the target installation package is legal or not according to the fourth data; and under the condition that the target installation package is determined to be legal, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform.
And under the condition that the target installation package is searched from the node server, calling a continuous delivery plug-in, and triggering the slave node server to execute a fourth callback function through a fourth calling instruction. And when the slave node server executes the fourth callback function, the format verification can be carried out on the searched target installation package. Specifically, the format of the target installation package may be verified, for example, if it is an apk installation package, to verify whether the content or format of the installation package meets the requirements of the apk installation package. The slave node server may return fourth data generated by executing the fourth callback function to the master node server. The master node server may determine whether the target installation package is legal according to the received fourth data. And under the condition that the target installation package is determined to be legal, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform. In the scheme, before uploading the target installation package, the target installation package is subjected to format verification, so that the risk of uploading the installation package can be reduced to the minimum, and only the installation package which is confirmed to be legal through verification can be uploaded to the continuous delivery platform.
In some embodiments of the present application, the target installation package information includes information of a plurality of target installation packages; correspondingly, after the continuous delivery plug-in is called and the second callback function is triggered to be executed from the node server through the second calling instruction so as to upload the target installation package to the continuous delivery platform, the method further comprises the following steps: receiving second data returned by the node server executing the second callback function, and determining whether the uploading of the target installation package is finished or not according to the second data; under the condition that the uploading of the target installation package is determined to be finished, a confirmation request is sent to the continuous delivery platform; receiving information of a target installation package received by a continuous delivery platform, wherein the information is returned by the continuous delivery platform in response to a confirmation request; determining whether uploading of a plurality of target installation packages is successful or not according to information of the target installation packages received by the continuous delivery platform; and under the condition that the plurality of target installation packages are successfully uploaded, generating confirmation information and sending the confirmation information to a continuous delivery platform, wherein the continuous delivery platform responds to the confirmation information to generate version numbers for the installation packages of the plurality of target installation packages and issue the target installation packages of the plurality of target installation packages.
The target installation package information may include information of a plurality of target installation packages. After the master node server calls the persistent delivery plug-in, the slave node server is triggered to execute a second callback function through the second call instruction to upload the installation package to the persistent delivery platform, and the master node server can confirm whether the uploading of the installation package is successful. Specifically, the master node server receives second data returned by the slave node server executing the second callback function, and determines whether the uploading of the target installation package is finished according to the second data. And sending a confirmation request to the continuous delivery platform under the condition that the uploading of the target installation package is determined to be finished. The persistent delivery platform may return information of the target installation package received by the persistent delivery platform to the primary node server in response to the received confirmation request. The master node server may determine whether uploading of the plurality of target installation packages is successful according to the information of the target installation packages received by the continuous delivery platform. The information of the target installation packages received by the continuous delivery platform may include the names and numbers of the received target installation packages. For example, if the number of target installation packages received by the continuous delivery platform is the same as the number of installation packages in the target installation package information, then it is determined that the upload was successful. And under the condition that the uploading of the plurality of target installation packages is successful, the master node server generates confirmation information and sends the confirmation information to the continuous delivery platform. And the continuous delivery platform responds to the received confirmation information, generates a version number for each of the plurality of installation packages and issues each of the plurality of target installation packages. In some embodiments, if it is determined that one or more of the plurality of target installation packages were not successfully uploaded, a rollback is performed and the installation package that has been successfully uploaded is disabled. In the scheme, before the continuous delivery platform issues the installation package, whether all the target installation packages constructed in the target task are successfully uploaded is verified, and consistency of the uploaded installation packages can be ensured.
In some embodiments of the present application, the method may further include: the master node server sends the target task information to the continuous delivery platform. Wherein the target task information may include, but is not limited to, at least one of: task identification, task number, execution time, execution log, execution path, etc. In the scheme, the target task information is sent to the continuous delivery platform, so that the continuous delivery platform can be convenient to check later.
In some embodiments of the present application, after determining whether the target installation package is searched from the node server according to the first data, further comprising: in the event that it is determined that the target installation package is not searched from the node server, an error log is generated from the first data. Specifically, in the case where it is determined that the slave node server has not searched for the target installation package, the master node server may generate an error log from the first data. For example, the error log may record information of the unsearched target installation package and information of the corresponding slave node server.
In some embodiments of the present application, the master node server may generate an error log from the third data if it is determined from the third data that the slave node server was not successfully logged in. For example, the error log may be described with information of the cause of the login failure and the slave node server of the login failure.
In some embodiments of the present application, the master node server may generate an error log from the fourth data in the event that the target installation package is determined to be illegal from the fourth data. For example, the error log may include information of an illegal target installation package and information of a corresponding slave node server.
In the above embodiment, after generating the error log, the master node server may return the generated error log to the front end, so that the developer may debug according to the error log. By generating an error log, it is possible to facilitate developers to find problems in parameter configuration and code writing and development.
In some embodiments of the present application, the persistent integration system comprises a Jenkins persistent integration system.
The Jenkins platform is an open source software project, and with the use of more and more enterprises, IT has been developed into an established standard in the industry, and almost all large IT companies are using the platform for continuous integration of software. The Jenkins continuous integrated system is rich in functions, is open and flexible, and can be conveniently expanded according to own needs by users. The Jenkins plug-in development technology is a main method for expanding the functions of Jenkins continuous integrated systems by taking the Jenkins continuous integrated systems as basic frameworks.
Specifically, in the Jenkins persistent integration system, callback functions of the core FilePath of the plug-in are continuously delivered. The FilePath class is used for representing file paths in the Jenkins workspace, and a master node server of the Jenkins system creates an object of the class in the construction process of Job, which represents a workspace root directory where Job executes. In order for the plug-in to process the installation package file smoothly at the slave node server of the Jenkins system, a class must be created to implement filepath. Interfaces and reloads callback functions in plug-ins. And, to ensure that this FilePath class is serializable, code logic to be subject to install package processing is placed into the callback function. The FilePath class in the Job execution process calls the FilePath.act method, and the FilePath.act method is triggered from the master node, so that the callback function of the FilePath.act method can be actively called and executed in the Jenkins slave node server.
Referring to fig. 3, fig. 3 shows a schematic diagram of a FilePath callback mechanism. As shown in fig. 3, the FilePath class is deployed in the Jenkins master node server, and the invoke callback functions are distributed in each Jenkins slave node server. When the master node server executes the FilePath.act method, each slave node server executing the installation package construction is triggered to execute an invoke callback function. After the invoke callback function is executed, each Jenkins slave node server returns a result to the FilePath class of the master node server. In this way, an executed closed loop is formed. The Invoke callback function may include multiple callback functions to perform the multiple steps shown in the right-side flow chart. Firstly logging in to a continuous delivery platform, then searching an installation package in a Jenkins slave node, then carrying out format verification after finding the installation package, and uploading the installation package to the continuous delivery platform after the installation package is successfully verified.
According to the scheme, a plurality of installation packages constructed by the multi-node job in different slave node servers can be uploaded through parameter configuration, and different constructed outputs can be designated according to different development stages. According to the scheme, the background address and login authentication information of the continuous delivery platform in butt joint with the plug-in can be parameterized and configured, and then the installation package and multi-node job related construction information are uploaded to the continuous delivery platform. By the method, the installation package constructed in the Jenkins continuous integration system can be automatically uploaded to the continuous delivery platform, and the code of the continuous delivery plug-in is executed in the Jenkins from the node server, so that the continuous integration link and the continuous delivery link are connected, and a delivery assembly line in the real sense is realized.
The above method is described below in connection with a specific embodiment, however, it should be noted that this specific embodiment is only for better illustrating the present application and is not meant to be a undue limitation on the present application.
In this particular embodiment, the continuous delivery method may include the steps of:
step 1, a master node server acquires target installation package information and login information of a continuous delivery platform, wherein the target installation package information comprises information of a target installation package constructed in a target task.
And 2, the master node server checks the target installation package information, and under the condition that the target installation package information passes the check, the master node server calls the continuous delivery plug-in and triggers the slave node server to execute a third callback function through a third call instruction.
And step 3, when the slave node server executes the third callback function, logging in the continuous delivery platform according to the login information, and returning third data generated by executing the third callback function to the master node server.
And step 4, the master node server receives third data returned by the slave node server by executing the third callback function, and determines whether the slave node server successfully logs in according to the third data.
And step 5, under the condition that the login of the slave node server is successful, the master node server calls the continuous delivery plug-in and triggers the slave node server to execute a first callback function through a first call instruction.
And 6, searching the target installation package in the slave node server according to the target installation package information when the slave node server executes the first callback function, and returning first data generated by executing the first callback function to the master node server.
And 7, the master node server receives first data returned by the slave node server through executing the first callback function, and determines whether the slave node server searches the target installation package according to the first data.
And step 8, under the condition that the slave node server searches the target installation package, the master node server calls the continuous delivery plug-in and triggers the slave node server to execute a fourth callback function through a fourth call instruction.
And 9, when the slave node server executes the fourth callback function, performing format verification on the searched target installation package, and returning fourth data generated by executing the fourth callback function to the master node server.
And step 10, the master node server receives fourth data returned by the slave node server executing the fourth callback function, and determines whether the target installation package is legal or not according to the fourth data.
And step 11, under the condition that the target installation package method is determined, the master node server calls the continuous delivery plug-in and triggers the slave node server to execute a second callback function through a second call instruction.
And step 12, uploading the target installation package to the continuous delivery platform when the slave node server executes the second callback function, and returning second data generated by executing the second callback function to the master node server.
And step 13, the master node server receives second data returned by the slave node server executing the second callback function, and determines whether the uploading of the target installation package is finished according to the second data.
And step 14, the master node server sends a confirmation request to the continuous delivery platform under the condition that the uploading of the target installation package is determined to be finished.
And step 15, the continuous delivery platform returns the information of the target installation package received by the continuous delivery platform to the main node server in response to the confirmation request.
And step 16, the master node server determines whether uploading of the plurality of target installation packages is successful according to the information of the target installation packages received by the continuous delivery platform.
And step 17, in the case that the uploading of the plurality of target installation packages is successful, the master node server generates confirmation information and sends the confirmation information to the continuous delivery platform.
In step 18, the continuous delivery platform generates a version number for each of the plurality of target installation packages and issues each of the plurality of target installation packages in response to the validation information.
In the scheme, the main node server can acquire the target installation package information, and the target installation package information is configured, so that the method can be applied to different continuous integration tasks, different target installation packages can be designated according to different development stages, the functions are rich, and the compatibility is good. The main node server can also acquire login information of the continuous delivery platform, and can upload installation packages generated by the target tasks to different continuous delivery platforms by configuring the login information. In addition, the master node server can trigger the slave node server to execute a first callback function by calling a continuous delivery plug-in based on a callback mechanism, so as to search a target installation package in the slave node server according to target installation package information, and can determine whether the slave node server searches the target installation package according to first data returned by the slave node server executing the first callback function, thereby realizing the purposes of searching the installation package constructed by the slave node server in a task of multi-node operation and automatically uploading the searched installation package to a continuous delivery platform. In addition, the front end and the rear end of the installation package can be checked by the scheme, so that the validity of the installation package is ensured. The continuous integrated system and the continuous delivery platform can be connected by the scheme, so that the continuous delivery efficiency is improved, and the delivery assembly line in the true sense is realized.
Based on the same inventive concept, a continuous delivery apparatus is also provided in the embodiments of the present application, as described in the following embodiments. Since the principle of the continuous delivery apparatus for solving the problem is similar to that of the continuous delivery method, the implementation of the continuous delivery apparatus can be referred to the implementation of the continuous delivery method, and the repetition is not repeated. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements the intended function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated. Fig. 4 is a block diagram of a continuous delivery apparatus according to an embodiment of the present application, as shown in fig. 4, including: the configuration is described below, and the acquisition module 401, the first calling module 402, the receiving module 403, and the second calling module 404 are described below.
The obtaining module 401 is configured to obtain target installation package information, where the target installation package information includes information of a target installation package constructed in a target task.
The first calling module 402 is configured to call the persistent delivery plug-in, and trigger the slave node server to execute a first callback function according to the first calling instruction, so as to search the slave node server for the target installation package according to the target installation package information.
The receiving module 403 is configured to receive first data returned from the node server by executing the first callback function, and determine whether the target installation package is searched by the node server according to the first data.
The second calling module 404 is configured to call the persistent delivery plug-in when it is determined that the target installation package is searched from the node server, and trigger the slave node server to execute a second callback function through a second calling instruction, so as to upload the target installation package to the persistent delivery platform.
In some embodiments of the present application, the first callback function may be issued in advance by the persistent delivery plug-in and disposed on the slave node server.
In some embodiments of the present application, the first invoking module may be specifically configured to: verifying the target installation package information; and calling the continuous delivery plug-in under the condition that the information of the target installation package passes the verification, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the information of the target installation package.
In some embodiments of the present application, the acquisition module may also be configured to acquire login information for the continuous delivery platform. Accordingly, the first calling module may be specifically configured to: calling a continuous delivery plug-in, and triggering the slave node server to execute a third callback function through a third calling instruction so as to log in to a continuous delivery platform according to login information; receiving third data returned by the slave node server for executing a third callback function, and determining whether the slave node server is successfully logged in according to the third data; and under the condition that the login of the slave node server is successful, calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information.
In some embodiments of the present application, the second invoking module may be specifically configured to: under the condition that the target installation package is searched from the node server, calling a continuous delivery plug-in, and triggering the node server to execute a fourth callback function through a fourth calling instruction so as to perform format verification on the searched target installation package; receiving fourth data returned from the node server by executing a fourth callback function, and determining whether the target installation package is legal or not according to the fourth data; and under the condition that the target installation package is determined to be legal, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to the continuous delivery platform.
In some embodiments of the present application, the target installation package information includes information of a plurality of target installation packages; correspondingly, the device can also comprise a confirmation module. The confirmation module may be specifically configured to: after the continuous delivery plug-in is called and a second callback function is triggered to be executed by the slave node server through a second call instruction so as to upload the target installation package to the continuous delivery platform, receiving second data returned by the slave node server for executing the second callback function, and determining whether the uploading of the target installation package is finished or not according to the second data; under the condition that the uploading of the target installation package is determined to be finished, a confirmation request is sent to the continuous delivery platform; receiving information of a target installation package received by a continuous delivery platform, wherein the information is returned by the continuous delivery platform in response to a confirmation request; determining whether uploading of a plurality of target installation packages is successful or not according to information of the target installation packages received by the continuous delivery platform; and under the condition that the plurality of target installation packages are successfully uploaded, generating confirmation information and sending the confirmation information to a continuous delivery platform, wherein the continuous delivery platform responds to the confirmation information to generate version numbers for the installation packages of the plurality of target installation packages and issue the target installation packages of the plurality of target installation packages.
In some embodiments of the present application, the apparatus may further include a generating module, where the generating module may be specifically configured to: after determining whether the slave node server searches for the target install package according to the first data, generating an error log according to the first data in a case that the slave node server is determined not to search for the target install package.
In some embodiments of the present application, the persistent integration system comprises a Jenkins persistent integration system.
From the above description, it can be seen that the following technical effects are achieved in the embodiments of the present application: the main node server can acquire the target installation package information, and can be applied to different continuous integration tasks by configuring the target installation package information, and can be used for designating different target installation packages according to different development stages. In addition, the master node server can trigger the slave node server to execute a first callback function by calling a continuous delivery plug-in based on a callback mechanism and deployed in the continuous delivery plug-in, so that a target installation package can be searched in the slave node server according to target installation package information, and whether the target installation package is searched in the slave node server or not can be determined according to first data returned by the slave node server when executing the first callback function, so that the installation package constructed by the slave node server is searched in a task of multi-node operation and automatically uploaded to a continuous delivery platform, a continuous integration system and the continuous delivery platform can be connected, the continuous delivery efficiency is improved, and a delivery pipeline in a real sense is realized.
The embodiment of the application further provides a main node server, and in particular, referring to fig. 5, the main node server according to the continuous delivery method provided by the embodiment of the application may include an input device 51, a processor 52, and a memory 53. Wherein the memory 53 is configured to store processor-executable instructions. The processor 52, when executing the instructions, implements the steps of the persistent delivery method described in any of the embodiments above.
In this embodiment, the input device may specifically be one of the main apparatuses for exchanging information between the user and the computer system. The input device may include a keyboard, mouse, camera, scanner, light pen, handwriting input board, voice input device, etc.; the input device is used to input raw data and a program for processing these numbers into the computer. The input device may also acquire and receive data transmitted from other modules, units, and devices. The processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor, and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a programmable logic controller, and an embedded microcontroller, among others. The memory may in particular be a memory device for storing information in modern information technology. The memory may comprise a plurality of levels, and in a digital system, may be memory as long as binary data can be stored; in an integrated circuit, a circuit with a memory function without a physical form is also called a memory, such as a RAM, a FIFO, etc.; in the system, the storage device in physical form is also called a memory, such as a memory bank, a TF card, and the like.
In this embodiment, the functions and effects specifically implemented by the master node server may be explained in comparison with other embodiments, and will not be described herein.
There is also provided in an embodiment of the present application a computer storage medium based on a persistent delivery method, the computer storage medium storing computer program instructions that, when executed, implement the steps of the persistent delivery method described in any of the embodiments above.
In the present embodiment, the storage medium includes, but is not limited to, a random access Memory (Random Access Memory, RAM), a Read-Only Memory (ROM), a Cache (Cache), a Hard Disk (HDD), or a Memory Card (Memory Card). The memory may be used to store computer program instructions. The network communication unit may be an interface for performing network connection communication, which is set in accordance with a standard prescribed by a communication protocol.
In this embodiment, the functions and effects of the program instructions stored in the computer storage medium may be explained in comparison with other embodiments, and are not described herein.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.
It is to be understood that the above description is intended to be illustrative, and not restrictive. Many embodiments and many applications other than the examples provided will be apparent to those of skill in the art upon reading the above description. The scope of the application should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
The foregoing description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and variations may be made to the embodiment of the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims (11)

1. A persistent delivery method, the method being applied to a master node server in a persistent integration system, wherein the master node server is configured with a callback mechanism-based persistent delivery plug-in, the persistent integration system further comprising a slave node server, the method comprising:
acquiring target installation package information, wherein the target installation package information comprises information of a target installation package constructed in a target task;
The continuous delivery plug-in is called, and the slave node server is triggered to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to the target installation package information;
receiving first data returned by the slave node server through executing the first callback function, and determining whether the slave node server searches the target installation package according to the first data;
and under the condition that the slave node server searches the target installation package, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to a continuous delivery platform.
2. The method of claim 1, wherein the first callback function is issued in advance by the persistent delivery plug-in and is provisioned on the slave node server.
3. The method of claim 1, wherein invoking the persistent delivery plug-in to trigger the slave node server to execute a first callback function via a first invocation instruction to search the slave node server for a target installation package according to the target installation package information comprises:
Checking the target installation package information;
and calling the continuous delivery plug-in under the condition that the target installation package information passes verification, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search the target installation package in the slave node server according to the target installation package information.
4. The method of claim 1, wherein, before invoking the persistent delivery plug-in, triggering the slave node server to execute a first callback function by a first invocation instruction to search the slave node server for a target installation package according to the target installation package information, further comprising:
acquiring login information of the continuous delivery platform;
correspondingly, the continuous delivery plug-in is called, and the slave node server is triggered to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to the target installation package information, wherein the method comprises the following steps:
calling the continuous delivery plug-in, and triggering the slave node server to execute a third callback function through a third calling instruction so as to log in to the continuous delivery platform according to the login information;
Receiving third data returned by the slave node server for executing the third callback function, and determining whether the slave node server is successfully logged in according to the third data;
and under the condition that the login of the slave node server is successful, calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to the target installation package information.
5. The method of claim 1, wherein invoking the persistent delivery plug-in if it is determined that the slave node server searched the target installation package, by a second invocation instruction, triggers the slave node server to execute a second callback function to upload the target installation package to a persistent delivery platform, comprising:
under the condition that the slave node server searches the target installation package, calling the continuous delivery plug-in, and triggering the slave node server to execute a fourth callback function through a fourth calling instruction so as to perform format verification on the searched target installation package;
receiving fourth data returned by the slave node server for executing the fourth callback function, and determining whether the target installation package is legal or not according to the fourth data;
And under the condition that the target installation package method is determined, calling the continuous delivery plug-in, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to a continuous delivery platform.
6. The method of claim 1, wherein the target installation package information comprises information of a plurality of target installation packages;
correspondingly, after the continuous delivery plug-in is called and the secondary node server is triggered to execute the second callback function through the second calling instruction so as to upload the target installation package to the continuous delivery platform, the method further comprises the following steps:
receiving second data returned by the slave node server for executing the second callback function, and determining whether the uploading of the target installation package is finished according to the second data;
sending a confirmation request to the continuous delivery platform under the condition that the uploading of the target installation package is determined to be finished;
receiving information of a target installation package received by the continuous delivery platform, wherein the information is returned by the continuous delivery platform in response to the confirmation request;
determining whether the uploading of the target installation packages is successful or not according to the information of the target installation packages received by the continuous delivery platform;
And under the condition that the plurality of target installation packages are successfully uploaded, generating confirmation information and sending the confirmation information to the continuous delivery platform, wherein the continuous delivery platform responds to the confirmation information to generate version numbers for the installation packages of the plurality of target installation packages and issue the target installation packages of the plurality of target installation packages.
7. The method of claim 1, further comprising, after determining from the first data whether the slave node server has searched the target installation package:
and generating an error log according to the first data under the condition that the slave node server does not search the target installation package.
8. The method of claim 1, wherein the persistent integration system comprises a Jenkins persistent integration system.
9. A persistent delivery device, the device being located at a master node server in a persistent integration system, wherein the master node server has a callback mechanism-based persistent delivery plug-in deployed, the persistent integration system further comprising a slave node server, the device comprising:
the acquisition module is used for acquiring target installation package information, wherein the target installation package information comprises information of a target installation package constructed in a target task;
The first calling module is used for calling the continuous delivery plug-in, and triggering the slave node server to execute a first callback function through a first calling instruction so as to search a target installation package in the slave node server according to the target installation package information;
the receiving module is used for receiving first data returned by the slave node server through executing the first callback function and determining whether the slave node server searches the target installation package according to the first data;
and the second calling module is used for calling the continuous delivery plug-in under the condition that the slave node server searches the target installation package, and triggering the slave node server to execute a second callback function through a second calling instruction so as to upload the target installation package to a continuous delivery platform.
10. A host node server comprising a processor and a memory for storing processor executable instructions, the processor implementing the steps of the method of any one of claims 1 to 8 when the instructions are executed.
11. A computer readable storage medium having stored thereon computer instructions, which when executed, implement the steps of the method of any of claims 1 to 8.
CN201911422465.5A 2019-12-31 2019-12-31 Continuous delivery method and device Active CN111124429B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911422465.5A CN111124429B (en) 2019-12-31 2019-12-31 Continuous delivery method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911422465.5A CN111124429B (en) 2019-12-31 2019-12-31 Continuous delivery method and device

Publications (2)

Publication Number Publication Date
CN111124429A CN111124429A (en) 2020-05-08
CN111124429B true CN111124429B (en) 2023-05-02

Family

ID=70507059

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911422465.5A Active CN111124429B (en) 2019-12-31 2019-12-31 Continuous delivery method and device

Country Status (1)

Country Link
CN (1) CN111124429B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112286580B (en) * 2020-10-31 2023-08-04 成都新潮传媒集团有限公司 Method and device for processing pipeline operation and computer equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108228190A (en) * 2018-01-25 2018-06-29 杭州时趣信息技术有限公司 Continuous integrating and delivery method, system, equipment and computer readable storage medium
CN109344080A (en) * 2018-10-31 2019-02-15 江苏电力信息技术有限公司 It is lasting to deliver and the integrated Software Quality Assurance method of automatic test
CN110209421A (en) * 2019-05-23 2019-09-06 北京奥鹏远程教育中心有限公司 For educating the automation continuous integrating management method of cloud platform
CN110493028A (en) * 2019-06-28 2019-11-22 浪潮电子信息产业股份有限公司 A kind of clustered deploy(ment) method, system, device and computer readable storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9569204B2 (en) * 2012-09-27 2017-02-14 Ebay Inc. End-to-end continuous integration and verification of software

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108228190A (en) * 2018-01-25 2018-06-29 杭州时趣信息技术有限公司 Continuous integrating and delivery method, system, equipment and computer readable storage medium
CN109344080A (en) * 2018-10-31 2019-02-15 江苏电力信息技术有限公司 It is lasting to deliver and the integrated Software Quality Assurance method of automatic test
CN110209421A (en) * 2019-05-23 2019-09-06 北京奥鹏远程教育中心有限公司 For educating the automation continuous integrating management method of cloud platform
CN110493028A (en) * 2019-06-28 2019-11-22 浪潮电子信息产业股份有限公司 A kind of clustered deploy(ment) method, system, device and computer readable storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
xiangnan10.Jenkins自动化部署-----持续交付，网址：https://blog.csdn.net/xiangnan10/article/details/80332866.《CSDN》.2018, *

Also Published As

Publication number Publication date
CN111124429A (en) 2020-05-08

Similar Documents

Publication Publication Date Title
CN108960830B (en) Intelligent contract deployment method, device, equipment and storage medium
CN109951547B (en) Transaction request parallel processing method, device, equipment and medium
CN107241315B (en) Access method and device of bank gateway interface and computer readable storage medium
JP2018530070A (en) System and method for building, optimizing and implementing a platform on a cloud-based computing environment
KR101579493B1 (en) Staging control method for source code, Computer program for the same, Recording medium storing computer program for the same
CN111290742A (en) Parameter verification method and device, electronic equipment and readable storage medium
CN104780076B (en) A kind of code check method and apparatus
CN111240892A (en) Data backup method and device
CN111078274A (en) Code development method and device, electronic equipment and computer storage medium
US10606730B2 (en) Networked digital data processor log file viewer
CN113515303B (en) Project transformation method, device and equipment
CN116257438A (en) Updating method of interface test case and related equipment
CN111124429B (en) Continuous delivery method and device
US11977872B2 (en) Method and system for code maintenance
Haenisch A case study on using functional programming for internet of things applications
CN112261114A (en) Data backup system and method
JP6904364B2 (en) System construction support device, method and program
CN102984229B (en) For configuring the method and system of trust machine
CN114996955A (en) Target range environment construction method and device for cloud-originated chaotic engineering experiment
CN111460436B (en) Unstructured data operation method and system based on blockchain
CN109101408A (en) The detection method and device of service availability in joint debugging environment
CN114003250A (en) Software deployment method and device
US11379434B2 (en) Efficient and automatic database patching using elevated privileges
CN108920172B (en) Program publishing and calling method and system for voice conversation platform
CN111651189A (en) Product delivery method and device of continuous integration system and electronic equipment

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
GR01 Patent grant
GR01 Patent grant