Pipeline deployment method, device, computer equipment, and storage medium
By introducing pause and start components into the pipeline service system, the complexity and low efficiency of multiple pipeline management in traditional microservice systems are solved, and more efficient component deployment management and verification are achieved, improving the efficiency and accuracy of pipeline deployment are improved. sex.
Patent Information
- Application Number
- CN202111550099.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-17
- Publication Date
- 2024-12-17
- Estimated Expiration
- 2041-12-17
AI Technical Summary
Traditional microservice systems require a lot of human resources in the management and maintenance of multiple pipelines, which increases the problems of management complexity and inefficiency.
By introducing a second component into the pipeline service system, it is used to suspend and start the pipeline deployment process, and to realize the verification and management of the deployment results of each component, build a pipeline service system containing multiple business type components, and reduce the number of pipeline settings. Improve deployment management efficiency.
It effectively reduces the complexity and human resource requirements of pipeline management, improves the efficiency and accuracy of component deployment, and ensures the order and consistency of pipeline deployment.
Smart Images

Figure CN114240369B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of cloud computing technology, and in particular to a pipeline deployment method, apparatus, computer equipment, storage medium, and computer program product. Background Art
[0002] With the rapid expansion of business scope and the increasing complexity of business scenarios, banks, Internet companies and other enterprises are facing more and more business demands. Currently, they all adopt microservice systems and deploy multiple service components in different regions to meet business scenario requirements under a larger business scope.
[0003] In traditional microservice system deployment, each service component is built as a business pipeline, and each pipeline implements scanning, compilation, and deployment of the program code of the service component. Since each business pipeline adopts a pipeline process execution method to continuously execute the service components in the pipeline, when a business scenario involves the business content of multiple service components, it is necessary to build multiple pipelines separately and manage these multiple pipelines to realize the service of the business scenario.
[0004] However, as the number of assembly lines increases exponentially, the management of multiple assembly lines in the same business scenario requires a lot of human resources and increases the complexity of managing and maintaining the assembly lines. Summary of the invention
[0005] Based on this, it is necessary to provide a pipeline deployment method, device, computer equipment, computer-readable storage medium and computer program product to address the above technical problems.
[0006] In a first aspect, the present application provides a pipeline deployment method. The method comprises:
[0007] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0008] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0009] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0010] In one embodiment, the method further comprises:
[0011] If the deployment verification result is that the verification fails, the component deployment process in the pipeline service system is stopped.
[0012] In one embodiment, the method further comprises:
[0013] Get the configuration files of the target components belonging to the same business scenario;
[0014] According to the business logic relationship between the target components, a process system framework including configuration files of the target components is constructed;
[0015] In the process system framework, when the target component has an adjacent next target component, a second component is added between the target component and the adjacent next target component to obtain a pipeline service system including each of the target components and the second component.
[0016] In one embodiment, the adding of a second component between the target component and the next adjacent target component to obtain a pipeline service system including each of the target components and the second component includes:
[0017] Divide each of the target components contained in the process system framework and the next target component adjacent to the target component into a target component pair;
[0018] Determining a second component of a target type corresponding to the target component pair according to a logical relationship between each of the target component pairs;
[0019] A second component of the corresponding target type is added between two target components of the target component pair to obtain a pipeline service system including each of the target components and the second component.
[0020] In one embodiment, the second component is a delay type component, and if the deployment verification result is verification passed, triggering a start condition in the second component includes:
[0021] If the deployment verification result is verification passed, then determining the deployment start time of the component of the next business type in the pipeline service system according to the timestamp information of the start time of the second component and the delay time preset in the second component;
[0022] When the deployment start time is reached, the startup process in the second component is triggered.
[0023] In one embodiment, the second component is a pause type component, and if the deployment verification result is verification passed, triggering a start condition in the second component includes:
[0024] If the deployment verification result is verification passed, the verification passed result is output and displayed;
[0025] In response to the start request triggered by the verification pass result, a start process in the second component is triggered.
[0026] In a second aspect, the present application also provides a pipeline deployment device. The device comprises:
[0027] A reading module, used to read configuration parameter information of a first component in the pipeline service system, and deploy the first component; the first component is a current component to be deployed determined according to a deployment order in the pipeline service system;
[0028] A pause module, used to call the second component in the pipeline service system and verify the deployment result of the first component to obtain a deployment verification result; the second component is a component used to pause the deployment process in the pipeline service system;
[0029] A startup module is used to trigger the startup process in the second component if the deployment verification result is verified to be passed, execute the steps of reading the configuration parameter information of the first component in the pipeline service system, and deploying the first component until all components to be deployed in the pipeline service system are deployed.
[0030] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:
[0031] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0032] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0033] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0034] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:
[0035] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0036] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0037] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0038] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:
[0039] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0040] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0041] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0042] The above-mentioned pipeline deployment method, device, computer equipment, storage medium and computer program product, the computer equipment reads the configuration parameter information of the first component in the pipeline service system and deploys the first component; wherein the first component is the current component to be deployed determined according to the deployment order in the pipeline service system. After the first component is deployed, the computer equipment calls the second component in the pipeline service system and verifies the deployment result of the first component to obtain a deployment verification result. wherein the second component is a component used to suspend the deployment process in the pipeline service system. if the deployment verification result is a verification pass, the computer equipment triggers the startup process in the second component, executes the steps of reading the configuration parameter information of the first component in the pipeline service system, and deploying the first component until all components to be deployed in the pipeline service system are deployed. adopting this method, setting the second component, and constructing each business type component and the second component belonging to the same business scenario into a pipeline service system, so as to realize that after the deployment of each business type component is completed, the deployment result is suspended and verified, the number of pipeline settings is reduced, and the efficiency of component deployment management is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] Figure 1 A schematic diagram of a flow chart of a pipeline deployment method in an embodiment;
[0044] Figure 2 A schematic diagram of a flow chart of steps for creating a pipeline service system in an embodiment;
[0045] Figure 3 A schematic diagram of a flow chart of adding a second component step in an embodiment;
[0046] Figure 4 A schematic diagram of a flow chart of a delay component triggering start step in one embodiment;
[0047] Figure 5 A schematic diagram of a flow chart of a pause component triggering a start step in one embodiment;
[0048] Figure 6 A schematic diagram of a specific example flow of a pipeline deployment method in an embodiment;
[0049] Figure 7 is a structural block diagram of a pipeline deployment device in one embodiment;
[0050] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0052] In one embodiment, Figure 1 As shown, a pipeline deployment method is provided. This embodiment uses the method applied to a terminal (collectively referred to as a computer device) as an example. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:
[0053] Step 102, read the configuration parameter information of the first component in the pipeline service system, and deploy the first component.
[0054] Among them, the first component is the current component to be deployed determined according to the deployment order in the pipeline service system.
[0055] In implementation, in order to facilitate the management of the pipeline, the business components belonging to the same business scenario are created as a complete pipeline service system (also referred to as pipeline for short), and component application deployment is performed according to the organizational structure between the components in the pipeline service system, so that a pipeline application process can be realized. Therefore, the computer device triggers Jenkins to perform continuous integration and deployment according to the deployment order between the components included in the pipeline service system, that is, reads the configuration parameter information of the first component in the pipeline service system, and deploys the first component, which is the current component to be deployed in the pipeline service system determined based on the deployment order.
[0056] Step 104, calling the second component in the pipeline service system, and verifying the deployment result of the first component to obtain a deployment verification result.
[0057] The second component is used to suspend the deployment process in the pipeline service system.
[0058] During implementation, in the pipeline service system of continuous integration deployment, after the deployment of the first component is completed, the deployment status of the first component needs to be verified. At this time, the execution method of the pipeline continuous deployment process of the pipeline cannot directly suspend the deployment process of the pipeline. Therefore, the computer device calls the second component (also called the pause component) in the pipeline service system to suspend the deployment of the pipeline. While the pipeline deployment is suspended, the deployment result of the first component is verified to obtain the deployment verification result.
[0059] Step 106, if the deployment verification result is verification passed, the startup process in the second component is triggered, and the configuration parameter information of the first component in the pipeline service system is read and the steps of deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0060] During implementation, if the deployment verification result of the component is passed, the computer device triggers the startup process in the second component and continues the component deployment process in the pipeline service system, that is, continues to execute step 102, and deploys the next adjacent component of the currently deployed component in the pipeline service system (the adjacent relationship refers to the adjacent relationship between business processing logics, not simply the distance adjacent) until all components to be deployed in the pipeline service system are deployed.
[0061] In the above-mentioned pipeline deployment method, the computer device reads the configuration parameter information of the first component in the pipeline service system and deploys the first component; wherein the first component is the current component to be deployed determined according to the deployment order in the pipeline service system. After the first component is deployed, the computer device calls the second component in the pipeline service system and verifies the deployment result of the first component to obtain a deployment verification result. Wherein, the second component is a component used to suspend the deployment process in the pipeline service system. If the deployment verification result is a verification pass, the computer device triggers the startup process in the second component, executes the steps of reading the configuration parameter information of the first component in the pipeline service system, and deploying the first component until all components to be deployed in the pipeline service system are deployed. Using this method, the second component is set, and the components of each business type and the second component belonging to the same business scenario are constructed into a pipeline service system, so that after the deployment of the components of each business type is completed, the deployment result is suspended and verified, the number of pipeline settings is reduced, and the efficiency of component deployment management is improved.
[0062] In one embodiment, the application deployment of a pipeline service system requires the post-deployment configuration parameter verification of each deployed component. Only after all components in the pipeline have passed the deployment verification, the pipeline can be applied. Therefore, after the deployment result is verified and the deployment verification result is obtained, the method further includes the following steps:
[0063] If the deployment verification result is verification failure, the component deployment process in the pipeline service system is stopped.
[0064] In implementation, if the deployment verification result of the currently deployed component is verification failure, the computer device triggers the stop process in the second component to completely stop the component deployment process in the pipeline service system.
[0065] Optionally, the reason for stopping the pipeline service system is analyzed, and a prompt message of the error reason (for example, component deployment verification fails) is generated and output for display to prompt the user that the pipeline cannot complete automatic deployment.
[0066] In this embodiment, the deployment process of the pipeline service system is paused by setting the second component, thereby realizing the deployment verification of the first component. When the deployment verification of the first component fails, the deployment of the entire pipeline is stopped and the cause of the error is reported, thereby avoiding invalid and erroneous deployment of the pipeline service system due to the inability to pause.
[0067] In one embodiment, if Figure 2 As shown, before deploying an application for a complete pipeline service system, it is first necessary to build the pipeline service system for each component under the same business scenario. The pipeline service system is different from the current pipeline. Currently, a pipeline can only contain one component. The pipeline service system contains all components required for the same business scenario. Therefore, the method also includes:
[0068] Step 202: Obtain configuration files of target components belonging to the same business scenario.
[0069] In implementation, the computer device obtains configuration files of target components in the same business scenario. Each service business in the same business scenario corresponds to at least one target component. For example, in a business scenario, three types of services need to be provided, and the target components corresponding to each type of service are component A, component B, and component C. At the same time, the business scenario needs to be applied in Beijing and Shanghai respectively. For Shanghai and Beijing, a total of two sets of configuration files corresponding to component A, component B, and component C need to be obtained in a pipeline service system.
[0070] Step 204: construct a process system framework including configuration files of each target component according to the business logic relationship between each target component.
[0071] In the implementation, the computer equipment builds the process system framework between each target component according to the business logic relationship between each target component. Specifically, in a pipeline service system, cross-regional distributed deployment of business scenarios can be realized. Therefore, firstly, the target components and configuration files are divided based on the service areas involved in the business scenarios. Then, in each service area, based on the corresponding components (i.e., service types) determined in the service area, the process system framework between each target component is built according to the logical processing relationship between each component. For example, if in the Shanghai service area, the logical execution relationship between service type 1 (corresponding to target component A), service type 2 (corresponding to target component B) and service type 3 (corresponding to target component C) is: service type 1 and service type 3 are in a same-level (parallel) processing relationship, that is, service type 1 and service type 3 are different service options provided to users at the same time. After service type 1 or service type 3 is executed, service type 2 has a superior-subordinate flow relationship with service type 1 and service type 3 respectively, that is, service type 1 or service type 3 will eventually be aggregated into the service of service type 2. Therefore, based on the logical execution relationship between the three service types, a process system framework is created between target components A, B and C: target component A and target component C are integrated into two branch nodes in the pipeline, and the next nodes of these two branch nodes are connected to the node integrated with target component B. Similarly, for another service area, for example, the Beijing service area, the logical execution relationship between service type 1 (corresponding to target component A), service type 2 (corresponding to target component B) and service type 3 (corresponding to target component C) is parallel processing, that is, these three services are different options provided to users at the same time. Therefore, the configuration files corresponding to target components A, B and C are integrated into nodes of the same processing level, and a parallel processing pipeline framework is established. Then, according to the execution order of the business scenario between the two regions, the process system frameworks of different service areas are combined to obtain a complete distributed process system framework.
[0072] Step 206, in the process system framework, when the target component has an adjacent next target component, a second component is added between the target component and the adjacent next target component to obtain a pipeline service system including each target component and the second component.
[0073] In implementation, based on the created process system framework, the framework position of each target component is identified. When a target component has an adjacent (the adjacent relationship here refers to the adjacent relationship between business processing logics, not simply the adjacent distance) next target component, the target component is characterized as a non-end component in the process system framework. A second component is added between each target component (intermediate component) of the process system framework and the adjacent next target component to obtain a pipeline service system including each target component and the second component.
[0074] The second component added to the process system framework is a non-business type component, and its purpose is to suspend the deployment process of the assembly line service system.
[0075] In one embodiment, if Figure 3 As shown, after the process system framework is constructed, a second component needs to be added to the non-end component in the framework to meet the verification requirements of the non-end component after deployment. The specific processing process of adding the second component between the target component and the next adjacent target component in step 206 includes:
[0076] Step 302: divide each target component included in the process system framework and the next target component adjacent to the target component into target component pairs.
[0077] In implementation, the computer device divides each target component included in the process system framework and the next target component adjacent to the target component into a target component pair. For example, in the created process system framework, if target component A has an adjacent next target component B, then target component A and target component B are a set of target component pairs, and if target component B also has an adjacent next target component E, then target component B and target component E are also a set of target component pairs. Furthermore, in the process system framework, each target component and the corresponding next target component are divided to obtain multiple target component pairs.
[0078] Step 304: Determine a second component of the target type corresponding to the target component pair according to the logical relationship between each target component pair.
[0079] In implementation, the computer device determines the second component of the target type required by the target component pair according to the logical relationship between each target component pair (including the execution order and the deployment time relationship). Specifically, there is an upper and lower hierarchical relationship of the execution order and a deployment time interval relationship in the target component pair. Therefore, if the deployment start time of the target component of the next level cannot be determined after the deployment of the target component of the previous level is completed, it is determined that the paired target components of the group correspond to the manually triggered second component, that is, the second component needs to be manually triggered after the pipeline deployment process is suspended to realize the subsequent process of the pipeline deployment service system. If the next target component needs to be deployed within a certain determinable time period after the deployment of the target component of the previous level is completed, it is determined that the target component pair of the group can correspond to the delayed pause second component.
[0080] Step 306, adding a second component of the corresponding target type between two target components of the target component pair, to obtain a pipeline service system including each target component and the second component.
[0081] In implementation, the computer device adds the second component of the target type between the two components of each corresponding set of target component pairs to obtain a pipeline service system including each target component and the second component of the target type.
[0082] In one embodiment, a second component of a corresponding type is added between each pair of components in the pipeline service system to ensure the orderly execution of the deployment process between the paired components. Therefore, when the added second component is a delay type component, such as Figure 4 As shown, if the deployment verification result in step 106 is verification passed, the specific processing process of triggering the startup condition in the second component includes the following steps:
[0083] Step 402, if the deployment verification result is verification passed, then determine the deployment start time of the component of the next business type in the pipeline service system according to the timestamp information of the start time of the second component and the delay duration preset in the second component.
[0084] In implementation, if the deployment verification result of the first component (i.e., the previous component) is verified to be passed, the start time of the component of the next business type in the pipeline service system is determined according to the timestamp information of the start time of calling the second component and the delay duration preset in the second component. For example, the start time of calling the second component is 2021-10-29-8:44 in the morning, and the delay duration set in the second component is 2 hours. Then, the start time of deploying the component of the next business type in the pipeline service system is 2021-10-29-10:44 in the morning. Among them, the formats of the various timestamp information involved in this application all adopt the format of yyyy-MM-dd HH:mm:ss, wherein "yyyy" represents the year, "MM" represents the month, "dd" represents the date, "HH" represents the number of hours, "MM" represents the number of minutes, and "ss" represents the number of seconds.
[0085] Step 404: When the deployment start time is reached, the startup process in the second component is triggered.
[0086] In implementation, when the delayed target deployment start time is reached, the computer device triggers the startup process in the second component to trigger the pipeline service system to continue to start the deployment of the next pipeline.
[0087] In this embodiment, by setting the second component of the delay type, the deployment interval between two components in a hierarchical relationship in the pipeline service system is guaranteed, and the overall deployment process is carried out in order.
[0088] In one embodiment, the pipeline service system adds a second component of the corresponding type between each pair of components to ensure the orderly execution of the deployment process between the paired components. Therefore, when the added second component is a pause type component, such as Figure 5 As shown, if the deployment verification result in step 106 is verification passed, the specific processing process of triggering the startup condition in the second component includes the following steps:
[0089] Step 502: If the deployment verification result is verification passed, the verification passed result is output and displayed.
[0090] In implementation, if the deployment verification result of the first component (ie, the previous component) is verification passed, a display data packet containing verification pass information is generated, and the display data packet is read and output for display to prompt the user of the current deployment progress.
[0091] Step 504: In response to the start request triggered by the verification pass result, trigger the start process in the second component.
[0092] In implementation, the user inputs a start request for continued deployment based on the displayed verification pass information, and the computer device responds to the start request and triggers the start process in the second component to trigger the deployment of the next pipeline in the pipeline service system.
[0093] In one embodiment, the type of the second component may also include a timed trigger type. Specifically, if the deployment verification result is verification passed in step 106, the specific processing process of triggering the start condition in the second component includes the following steps:
[0094] Step 1: If the deployment verification result is verification passed, read the startup timestamp information preset in the second component, and determine the startup timestamp information as the deployment start time.
[0095] Step 2: When the deployment start time is reached, trigger the startup process in the second component.
[0096] During implementation, if the next component to be deployed has a clear deployment start time, the computer device uses this time as the timing time, determines the start timestamp information in the second component based on the timing time, and when the timing time is reached, triggers the startup process in the second component to continue the deployment process in the pipeline service system.
[0097] In one embodiment, Figure 6 As shown, an example of a pipeline deployment method is provided, including the following steps:
[0098] Step 601, according to the hierarchical architecture between the components in the created pipeline service system, read the configuration parameter information of the first component A and the first component C to be deployed in the first level of the pipeline service system, and deploy the first component A and the first component C;
[0099] Step 602, call the second component of the delay type, suspend the subsequent deployment process of the first component A in the pipeline service system, verify the deployment result of the first component A, and obtain the deployment verification result; call the second component of the timing type, suspend the subsequent deployment process of the first component C in the pipeline service system, verify the deployment result of the first component C, and obtain the deployment verification result.
[0100] Step 603, if the deployment verification result is verification passed, when the deployment start time corresponding to the delay or the deployment start time corresponding to the timing is reached, the second component triggers the deployment start process, reads the configuration parameter information of the first component B, and deploys the first component B.
[0101] Step 604, calling the second component of the pause type, suspending the subsequent deployment process of the first component B in the pipeline service system, verifying the deployment result of the first component B, obtaining the deployment verification result, and outputting and displaying the deployment verification result.
[0102] Step 605, if the deployment verification result is verification passed, in response to the deployment start request triggered by the user, the pause type second component triggers the deployment start process, reads the configuration parameter information of the first component A', the first component B' and the first component C' to be deployed at the same level, deploys the first component A', the first component B' and the first component C', and verifies their deployment results, and the deployment of the pipeline service system is completed.
[0103] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0104] Based on the same inventive concept, the embodiment of the present application also provides a pipeline deployment device for implementing the above-mentioned pipeline deployment method. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above-mentioned method, so the specific limitations of one or more pipeline deployment device embodiments provided below can refer to the limitations of the pipeline deployment method above, and will not be repeated here.
[0105] In one embodiment, Figure 7 As shown, a pipeline deployment device 700 is provided, including: a reading module 710, a pause module 720 and a start module 730, wherein:
[0106] The reading module 710 is used to read the configuration parameter information of the first component in the pipeline service system and deploy the first component; the first component is the current component to be deployed determined according to the deployment order in the pipeline service system;
[0107] The pause module 720 is used to call the second component in the pipeline service system and verify the deployment result of the first component to obtain a deployment verification result; the second component is a component used to pause the deployment process in the pipeline service system;
[0108] The startup module 730 is used to trigger the startup process in the second component if the deployment verification result is verification passed, execute the steps of reading the configuration parameter information of the first component in the pipeline service system, and deploying the first component until all components to be deployed in the pipeline service system are deployed.
[0109] In one embodiment, the apparatus 700 further includes:
[0110] The stop module is used to stop the component deployment process in the pipeline service system if the deployment verification result is verification failure.
[0111] In one embodiment, the apparatus 700 further includes:
[0112] The acquisition module is used to obtain the configuration files of the target components belonging to the same business scenario;
[0113] A construction module is used to construct a process system framework including configuration files of each target component according to the business logic relationship between each target component;
[0114] The generation module is used to add a second component between the target component and the adjacent next target component in the process system framework when the target component has an adjacent next target component, so as to obtain a pipeline service system including each target component and the second component.
[0115] In one embodiment, a generating module is used to divide each target component included in the process system framework and the next target component adjacent to the target component into target component pairs;
[0116] Determine, according to the logical relationship between each pair of target components, a second component of the target type corresponding to the target component pair;
[0117] A second component of the corresponding target type is added between two target components of the target component pair to obtain a pipeline service system including each target component and the second component.
[0118] In one embodiment, the second component is a delay type component, and the startup module 730 is specifically used to determine the deployment start time of the next business type component in the pipeline service system according to the timestamp information of the start time of the second component and the delay time preset in the second component if the deployment verification result is verification passed;
[0119] When the deployment start time is reached, the startup process in the second component is triggered.
[0120] In one embodiment, the second component is a pause type component, and the startup module 730 is specifically used to output and display the verification result if the deployment verification result is verification passed;
[0121] In response to the start request triggered by the verification pass result, a start process in the second component is triggered.
[0122] Each module in the above-mentioned pipeline deployment device 700 can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.
[0123] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 8As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a pipeline deployment method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.
[0124] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0125] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:
[0126] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0127] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0128] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0129] In one embodiment, when the processor executes the computer program, the following steps are also implemented:
[0130] If the deployment verification result is that the verification fails, the component deployment process in the pipeline service system is stopped.
[0131] In one embodiment, when the processor executes the computer program, the following steps are also implemented:
[0132] Get the configuration files of the target components belonging to the same business scenario;
[0133] According to the business logic relationship between the target components, a process system framework including configuration files of the target components is constructed;
[0134] In the process system framework, when the target component has an adjacent next target component, a second component is added between the target component and the adjacent next target component to obtain a pipeline service system including each of the target components and the second component.
[0135] In one embodiment, when the processor executes the computer program, the following steps are also implemented:
[0136] Divide each of the target components contained in the process system framework and the next target component adjacent to the target component into a target component pair;
[0137] Determining a second component of a target type corresponding to the target component pair according to a logical relationship between each of the target component pairs;
[0138] A second component of the corresponding target type is added between two target components of the target component pair to obtain a pipeline service system including each of the target components and the second component.
[0139] In one embodiment, when the processor executes the computer program, the following steps are also implemented:
[0140] If the deployment verification result is verification passed, then determining the deployment start time of the component of the next business type in the pipeline service system according to the timestamp information of the start time of the second component and the delay time preset in the second component;
[0141] When the deployment start time is reached, the startup process in the second component is triggered.
[0142] In one embodiment, when the processor executes the computer program, the following steps are also implemented:
[0143] If the deployment verification result is verification passed, the verification passed result is output and displayed;
[0144] In response to the start request triggered by the verification pass result, a start process in the second component is triggered.
[0145] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0146] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0147] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0148] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0149] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0150] If the deployment verification result is that the verification fails, the component deployment process in the pipeline service system is stopped.
[0151] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0152] Get the configuration files of the target components belonging to the same business scenario;
[0153] According to the business logic relationship between the target components, a process system framework including configuration files of the target components is constructed;
[0154] In the process system framework, when the target component has an adjacent next target component, a second component is added between the target component and the adjacent next target component to obtain a pipeline service system including each of the target components and the second component.
[0155] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0156] Divide each of the target components contained in the process system framework and the next target component adjacent to the target component into a target component pair;
[0157] Determining a second component of a target type corresponding to the target component pair according to a logical relationship between each of the target component pairs;
[0158] A second component of the corresponding target type is added between two target components of the target component pair to obtain a pipeline service system including each of the target components and the second component.
[0159] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0160] If the deployment verification result is verification passed, then determining the deployment start time of the component of the next business type in the pipeline service system according to the timestamp information of the start time of the second component and the delay time preset in the second component;
[0161] When the deployment start time is reached, the startup process in the second component is triggered.
[0162] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0163] If the deployment verification result is verification passed, the verification passed result is output and displayed;
[0164] In response to the start request triggered by the verification pass result, a start process in the second component is triggered.
[0165] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:
[0166] Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system;
[0167] Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system;
[0168] If the deployment verification result is verification passed, the startup process in the second component is triggered, and the steps of reading the configuration parameter information of the first component in the pipeline service system and deploying the first component are executed until all components to be deployed in the pipeline service system are deployed.
[0169] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0170] If the deployment verification result is that the verification fails, the component deployment process in the pipeline service system is stopped.
[0171] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0172] Get the configuration files of the target components belonging to the same business scenario;
[0173] According to the business logic relationship between the target components, a process system framework including configuration files of the target components is constructed;
[0174] In the process system framework, when the target component has an adjacent next target component, a second component is added between the target component and the adjacent next target component to obtain a pipeline service system including each of the target components and the second component.
[0175] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0176] Divide each of the target components contained in the process system framework and the next target component adjacent to the target component into a target component pair;
[0177] Determining a second component of a target type corresponding to the target component pair according to a logical relationship between each of the target component pairs;
[0178] A second component of the corresponding target type is added between two target components of the target component pair to obtain a pipeline service system including each of the target components and the second component.
[0179] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0180] If the deployment verification result is verification passed, then determining the deployment start time of the component of the next business type in the pipeline service system according to the timestamp information of the start time of the second component and the delay time preset in the second component;
[0181] When the deployment start time is reached, the startup process in the second component is triggered.
[0182] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0183] If the deployment verification result is verification passed, the verification passed result is output and displayed;
[0184] In response to the start request triggered by the verification pass result, a start process in the second component is triggered.
[0185] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.
[0186] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0187] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A pipeline deployment method, characterized in that: The method comprises: Get the configuration files of the target components belonging to the same business scenario; According to the business logic relationship between the target components, a process system framework including configuration files of the target components is constructed; In the process system framework, when the target component has an adjacent next target component, a second component is added between the target component and the adjacent next target component to obtain a pipeline service system including each of the target components and the second component; Reading configuration parameter information of a first component in the pipeline service system, and deploying the first component; the first component is a component to be currently deployed determined according to a deployment order in the pipeline service system; Calling a second component in the pipeline service system and verifying the deployment result of the first component to obtain a deployment verification result; the second component is a component used to suspend the deployment process in the pipeline service system; If the deployment verification result is verification passed, triggering the startup process in the second component, executing the steps of reading the configuration parameter information of the first component in the pipeline service system, and deploying the first component, until all components to be deployed in the pipeline service system are deployed; The process system framework including the configuration files of each target component is constructed according to the business logic relationship between each target component, including: Dividing the target components and the configuration files according to the service areas involved in the business scenario; For each of the service areas, a process system framework between the target components is constructed according to the logical processing relationship between the target components.
2. The method according to claim 1, characterized in that: The method further comprises: If the deployment verification result is that the verification fails, the component deployment process in the pipeline service system is stopped.
3. The method according to claim 1, characterized in that The step of adding a second component between the target component and the next adjacent target component to obtain a pipeline service system including each of the target components and the second component includes: Divide each of the target components contained in the process system framework and the next target component adjacent to the target component into a target component pair; Determining a second component of a target type corresponding to the target component pair according to a logical relationship between each of the target component pairs; A second component of the corresponding target type is added between two target components of the target component pair to obtain a pipeline service system including each of the target components and the second component.
4. The method according to claim 1, characterized in that: The second component is a delay type component. If the deployment verification result is verification passed, triggering a start condition in the second component includes: If the deployment verification result is verification passed, then determining the deployment start time of the component of the next business type in the pipeline service system according to the timestamp information of the start time of the second component and the delay time preset in the second component; When the deployment start time is reached, the startup process in the second component is triggered.
5. The method according to claim 1, characterized in that The second component is a pause type component. If the deployment verification result is verification passed, triggering a start condition in the second component includes: If the deployment verification result is verification passed, the verification passed result is output and displayed; In response to the start request triggered by the verification pass result, a start process in the second component is triggered.
6. The method according to claim 1, characterized in that The second component is a timing type component. If the deployment verification result is verification passed, triggering a start condition in the second component includes: If the deployment verification result is verification passed, read the startup timestamp information preset in the second component, and determine the startup timestamp information as the deployment start time; When the deployment start time is reached, the startup process in the second component is triggered.
7. A pipeline deployment device, characterized in that: The device comprises: The acquisition module is used to obtain the configuration files of the target components belonging to the same business scenario; A construction module, used to construct a process system framework including configuration files of each target component according to the business logic relationship between each target component; A generation module, used for adding a second component between the target component and the adjacent next target component in the process system framework, when the target component has an adjacent next target component, to obtain a pipeline service system including each of the target components and the second component; A reading module, used to read configuration parameter information of a first component in the pipeline service system, and deploy the first component; the first component is a current component to be deployed determined according to a deployment order in the pipeline service system; A pause module, used to call the second component in the pipeline service system and verify the deployment result of the first component to obtain a deployment verification result; the second component is a component used to pause the deployment process in the pipeline service system; A startup module, configured to trigger a startup process in the second component if the deployment verification result is verification passed, execute the steps of reading the configuration parameter information of the first component in the pipeline service system, and deploying the first component, until all components to be deployed in the pipeline service system are deployed; The construction module is specifically used to divide the target components and the configuration files according to the service areas involved in the business scenario; for each of the service areas, a process system framework between the target components is constructed according to the logical processing relationship between the target components.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
Citation Information
Patent Citations
Application deployment method and system
CN106469068A
Application program deployment method, device, computer equipment and storage medium
CN110609732A
Distributed job service scheduling method, distributed server and service terminal
CN112799813A
Assembly line method and device for cross-cluster deployment of container cloud applications
CN113609019A
Application program publishing method and device, equipment, storage medium and program product
CN115080060A
