CN114240369A - Pipeline deployment method and device, computer equipment and storage medium - Google Patents

Pipeline deployment method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN114240369A
CN114240369A CN202111550099.9A CN202111550099A CN114240369A CN 114240369 A CN114240369 A CN 114240369A CN 202111550099 A CN202111550099 A CN 202111550099A CN 114240369 A CN114240369 A CN 114240369A
Authority
CN
China
Prior art keywords
component
deployment
service system
target
pipeline
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111550099.9A
Other languages
Chinese (zh)
Inventor
赵振标
张泳
刘伟
张伟强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
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 Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202111550099.9A priority Critical patent/CN114240369A/en
Publication of CN114240369A publication Critical patent/CN114240369A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Mining & Analysis (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Stored Programmes (AREA)

Abstract

The application relates to a pipeline deployment method, a pipeline deployment device, computer equipment, a storage medium and a computer program product, and relates to the technical field of cloud computing. The method comprises the following steps: reading configuration parameter information of a first assembly in the pipeline service system, and deploying the first assembly, wherein the first assembly is a current assembly to be deployed which is determined according to a deployment sequence in the pipeline service system. And then, calling a second component in the pipeline service system, and verifying the deployment result of the first component to obtain a deployment verification result. And the second component is a component for pausing the deployment process in the pipeline service system. And if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all the assemblies to be deployed in the pipeline service system are deployed. The method improves the management efficiency of component deployment.

Description

Pipeline deployment method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a method and an apparatus for pipeline deployment, a computer device, a storage medium, and a computer program product.
Background
With rapid expansion of a service range and continuous complication of a service scene, enterprises such as banks and the internet face more and more service demands, at present, a micro-service system is adopted, and a plurality of service components are deployed in different areas in a distributed manner to meet the service scene demand in a larger service range.
In traditional micro service system deployment, each service component is constructed as a service pipeline, and each pipeline realizes scanning, compiling, deploying and the like of a program code of the service component. Because each service pipeline adopts a pipeline type flow execution mode to uninterruptedly execute the service components in the pipeline, when the service content of a plurality of service components is related in one service scene, a plurality of pipelines need to be respectively constructed and managed so as to realize the service of the service scene.
However, as the number of pipelines grows by multiples, management among multiple pipelines in the same business scenario can consume significant human resources and increase the complexity of managing and maintaining the pipelines.
Disclosure of Invention
In view of the above, it is necessary to provide a pipeline deployment method, apparatus, computer device, computer readable storage medium and computer program product for solving the above technical problems.
In a first aspect, the present application provides a pipeline deployment method. The method comprises the following steps:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In one embodiment, the method further comprises:
and if the deployment verification result is that the verification is not passed, stopping the component deployment process in the pipeline service system.
In one embodiment, the method further comprises:
acquiring configuration files of target components belonging to the same service scene;
constructing a flow system framework containing configuration files of the target components according to the business logic relationship among the target components;
in the flow 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, so as to obtain a pipeline service system including each target component and the second component.
In one embodiment, the adding a second component between the target component and the next adjacent target component to obtain a pipeline service system including each target component and the second component includes:
dividing each target component and a next target component adjacent to the target component contained in the flow system framework into a target component pair;
determining a second component of a target type corresponding to each target component pair according to the logical relationship between each target component pair;
and adding the corresponding second component of the target type between the two target components of the target component pair to obtain a pipeline service system containing each target component and the second component.
In one embodiment, the second component is a delay type component, and if the deployment verification result is that the deployment verification passes, triggering a starting condition in the second component includes:
if the deployment verification result is that the verification is passed, determining the deployment starting time of the component of the next service type in the pipeline service system according to the timestamp information of the starting time of the second component and the preset delay time in the second component;
and when the deployment starting time is reached, triggering a starting process in the second component.
In one embodiment, the second component is a suspension type component, and if the deployment verification result is that the deployment verification passes, triggering a start condition in the second component includes:
if the deployment verification result is that the verification is passed, outputting and displaying the verification passed result;
and triggering a starting process in the second component in response to a starting request triggered by the verification passing result.
In a second aspect, the application further provides a pipeline deployment device. The device comprises:
the reading module is used for reading configuration parameter information of a first component in a pipeline service system and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence in the pipeline service system;
the suspension module is used for calling a second assembly in the pipeline service system and verifying the deployment result of the first assembly to obtain a deployment verification result; the second component is a component for suspending a deployment process in the pipeline service system;
and the starting module is used for triggering a starting process in the second assembly if the deployment verification result is that the verification is passed, executing the steps of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
According to the pipeline deployment method, the pipeline deployment device, the computer equipment, the storage medium and the 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; the first component is a current component to be deployed determined according to a deployment sequence in the pipeline service system. After the first component is deployed, the computer equipment calls a second component in the pipeline service system, and verifies the deployment result of the first component to obtain a deployment verification result. The second component is a component for suspending a deployment process in the pipeline service system. If the deployment verification result is that the verification is passed, the computer equipment triggers a starting process in the second assembly, executes the steps of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed. By adopting the method, the second component is set, and the components of the service types and the second component which belong to the same service scene are constructed into a pipeline service system, so that the deployment result is subjected to pause verification after the deployment of the components of the service types is completed, the number of pipeline settings is reduced, and the component deployment management efficiency is improved.
Drawings
FIG. 1 is a flow diagram that illustrates a method for pipeline deployment in one embodiment;
FIG. 2 is a schematic flow chart diagram illustrating the steps in one embodiment for creating a pipeline service architecture;
FIG. 3 is a schematic flow chart illustrating the step of adding a second component in one embodiment;
FIG. 4 is a flowchart illustrating the triggering and initiating steps of the delay element in one embodiment;
FIG. 5 is a flow diagram illustrating the triggering of the activation step by the pause component in one embodiment;
FIG. 6 is a flowchart illustrating a specific example of a pipeline deployment method in one embodiment;
FIG. 7 is a block diagram of the architecture of a pipeline deployment apparatus in one embodiment;
FIG. 8 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In an embodiment, as shown in fig. 1, a pipeline deployment method is provided, and this embodiment is illustrated by applying the method to a terminal (collectively referred to as a computer device), it is to be understood that the method may also be applied to a server, and may also be applied to a system including the terminal and the server, and is implemented through interaction between the terminal and the server. In this embodiment, the method includes the steps of:
and 102, reading configuration parameter information of a first component in the pipeline service system, and deploying the first component.
The first component is a current component to be deployed determined according to a deployment sequence in a pipeline service system.
In implementation, in order to facilitate management of a pipeline, business components belonging to the same business scenario are created into a complete pipeline service system (also referred to as a pipeline for short), and component application deployment is performed for an organization architecture among components in the pipeline service system, so that a pipeline application process can be implemented. Therefore, the computer device triggers jenkins to perform continuous integration and deployment according to the deployment sequence among the components in the pipeline service system, that is, reads the configuration parameter information of a first component in the pipeline service system to deploy the first component, wherein the first component is the component to be currently deployed and determined based on the deployment sequence in the pipeline service system.
And 104, calling a second assembly in the pipeline service system, and verifying the deployment result of the first assembly to obtain a deployment verification result.
Wherein the second component is a component for suspending the deployment process in the pipeline service system
In implementation, in the pipeline service system of the continuous integrated deployment, after the first component deployment is completed, the deployment condition of the first component needs to be verified, and at this time, the execution mode of the pipeline type continuous deployment flow cannot directly pause the deployment process of the pipeline, so that the computer device calls a second component (also referred to as a pause component) in the pipeline service system to pause the deployment of the pipeline, and verifies the deployment result of the first component while the pipeline pauses the deployment to obtain the deployment verification result.
And 106, if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In implementation, if the deployment verification result of the component is that the verification is passed, the computer device triggers a start 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 a next adjacent component of the currently deployed component in the pipeline service system (the adjacent relationship refers to an adjacent relationship between the business processing logics, and is not simply adjacent in distance), until all the components to be deployed in the pipeline service system are deployed completely.
In the pipeline deployment method, the computer equipment reads the configuration parameter information of a first component in a pipeline service system and deploys the first component; the first component is a current component to be deployed determined according to a deployment sequence in a pipeline service system. After the first component is deployed, the computer equipment calls a second component in the pipeline service system, and verifies the deployment result of the first component to obtain a deployment verification result. And the second component is a component for pausing the deployment process in the pipeline service system. And if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly by the computer equipment, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all the assemblies to be deployed in the pipeline service system are deployed. By adopting the method, the second component is set, and the components of the service types and the second component which belong to the same service scene are constructed into a pipeline service system, so that the deployment result is subjected to pause verification after the deployment of the components of the service types is completed, the number of pipeline settings is reduced, and the component deployment management efficiency is improved.
In one embodiment, implementing application deployment of a pipeline service architecture requires verification of configuration parameters after deployment of each deployed component, and the pipeline can perform application only after all components in the pipeline pass the deployment verification, so that when the deployment result is verified and the deployment verification result is obtained, the method further includes the following steps:
and if the deployment verification result is that the verification is not passed, stopping the component deployment flow in the pipeline service system.
In implementation, if the deployment verification result of the currently deployed component is that the verification fails, the computer device triggers a stop process in the second component to completely stop the component deployment process in the pipeline service system.
Optionally, the stopping reason of the pipeline service system is analyzed, and a prompt message of an error reason (for example, component deployment verification fails) is generated and output for display, so as to prompt a user that the pipeline cannot complete automatic deployment.
In this embodiment, the deployment verification of the first component is realized by setting the second component to suspend the deployment process of the pipeline service system, and when the deployment verification of the first component fails, the deployment of the whole pipeline is stopped and the error reason is reported, so that invalid and erroneous deployment caused by the pipeline service system being unable to suspend are avoided.
In one embodiment, as shown in fig. 2, before application deployment is performed on a complete pipeline service architecture, the pipeline service architecture needs to be constructed for each component in the same business scenario, where the pipeline service architecture is different from a current pipeline, and a current pipeline only includes one component, and the pipeline service architecture includes all components required by the same business scenario, and therefore, the method further includes:
step 202, obtaining configuration files of target components belonging to the same service scene.
In implementation, a computer device obtains configuration files of target components belonging to the same business scenario. For example, in one service scene, three types of services need to be provided, the target components corresponding to each type of service are respectively component a, component B, and component C, and meanwhile, the service scene needs to be applied to two places of beijing and shanghai, so that configuration files of two groups of corresponding components a, component B, and component C need to be obtained in a pipeline service system for shanghai regions and beijing regions.
And step 204, constructing a flow system framework containing the configuration files of the target components according to the business logic relationship among the target components.
In implementation, the computer device constructs a flow system framework among the target components according to the business logic relationship among the target components. Specifically, in a pipeline service system, cross-regional distributed deployment of a service scene can be realized, so that target components and configuration files are divided based on a service region related to the service scene, and further, in each service region, a flow system framework between the target components is constructed based on the determined corresponding components (i.e., service types) in the service region according to a logical processing relationship between the components. For example, if in the shanghai service area, the logic execution relationship among 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: the service type 1 and the service type 3 are in the same-level (parallel) processing relationship, that is, the service type 1 and the service type 3 are different service choices provided for the user at the same time, after the service type 1 or the service type 3 is executed, the service type 2 is in the upper-level and lower-level circulation relationship with the service type 1 and the service type 3 respectively, that is, the service type 1 or the service type 3 is finally gathered to the service of the service type 2, and therefore, based on the logical execution relationship between the three service types, a flow system framework between the target component A, B and the target component C is created: and integrating the target component A and the target component C into two branch nodes in the pipeline, wherein the next node of the two branch nodes is connected with the node integrated by the target component B. Similarly, for another service area, for example, beijing service area, the logic 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 choices provided for the user at the same time, so the configuration files corresponding to target component A, B and C are integrated into nodes of the same processing level, a parallel processing pipeline framework is established, and then the flow framework of different service areas are combined according to the execution sequence of the service scenario between two areas, so as to obtain a complete distributed flow framework.
And step 206, in the flow system framework, when the target assembly has an adjacent next target assembly, adding a second assembly between the target assembly and the adjacent next target assembly to obtain a flow line service system containing each target assembly and the second assembly.
In implementation, based on the created flow system framework, the framework position of each target component is identified, when the target component has a next target component adjacent to each other (where the adjacent relationship refers to the adjacent relationship between the business processing logics, and is not simply a distance adjacent to each other), the target component is characterized as a non-ending component in the flow system framework, and a second component is added between each target component (intermediate component) of the flow system framework and the next adjacent target component, so as to obtain a pipeline service system including each target component and the second component.
The second component added in the flow system frame is a non-business type component, and the purpose of the second component is to suspend the deployment flow of the pipeline service system.
In one embodiment, as shown in fig. 3, after the framework of the flow system is built, a second component needs to be added to the non-ending component in the framework to meet the verification requirement of the non-ending component after the deployment is completed, and the specific process of adding the second component between the target component and the next adjacent target component in step 206 includes:
step 302, each target component included in the flow system framework and the next target component adjacent to the target component are divided into target component pairs.
In an implementation, a computer device divides each target component included in a flow architecture framework and a next target component adjacent to the target component into a pair of target components. For example, in the created flow system framework, if the target component a has an adjacent next target component B, the target component a and the target component B are a set of target component pairs, and if the target component B also has an adjacent next target component E, the target component B and the target component E are also a set of target component pairs. And further, in the flow system framework, dividing each target assembly and the corresponding next target assembly to obtain a plurality of target assembly pairs.
Step 304, determining a second component of the target type corresponding to the target component pair according to the logical relationship between each target component pair.
In implementation, the computer device determines the second component of the target type required by each target component pair according to the logical relationship (including the execution order and deployment time relationship) between the target component pairs. Specifically, the target component pair has a relationship between an upper level and a lower level of an execution sequence and a deployment time interval relationship, and 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, after the pipeline deployment process is suspended, the second component needs to be manually triggered manually, so as to implement the subsequent process of the pipeline deployment service system. And if the next target component needs to be deployed within a certain determinable time after the target component of the previous level is deployed, determining that the target component pair of the group can correspond to the time-delay suspended second component.
Step 306, adding the second component of the corresponding target type between the two target components of the target component pair to obtain a pipeline service system including each target component and the second component.
In implementation, the computer device adds the second component of the target type between two components of each target component pair corresponding to the second component of the target type, and obtains a pipeline service system containing the target components and the second component of the target type.
In one embodiment, a second component of a corresponding type is added to each paired component in the pipeline service system to ensure that the deployment process between the paired components is executed in order, and therefore, when the added second component is a delay type component, as shown in fig. 4, if the deployment verification result is that the verification is passed in step 106, the specific processing procedure of triggering the start condition in the second component includes the following steps:
and step 402, if the deployment verification result is that the verification is passed, determining the deployment start time of the component of the next service type in the pipeline service system according to the timestamp information of the start time of the second component and the preset delay time in the second component.
In implementation, if the deployment verification result of the first component (i.e., the previous component) is that the verification is passed, the component start time of the next service type in the pipeline service system is determined according to the timestamp information of the start time of calling the second component and the preset delay time in the second component. For example, the starting time of calling the second component is 2021-10-29-8:44 in the morning, the delay time duration set in the second component is 2 hours, and the starting time of starting to deploy the component of the next service type in the pipeline service system is 2021-10-29-10:44 in the morning. The formats of the timestamp information are yyyy-MM-dd HH: MM: ss, wherein the yyyy represents the year, the MM represents the month, the dd represents the date, the HH represents the hours, the MM represents the minutes, and the ss represents the seconds.
Step 404, when the deployment start time is reached, a start process in the second component is triggered.
In implementation, when the delayed target deployment start time is reached, the computer device triggers a start process in the second component to trigger the pipeline service system to continue to start the deployment of the next pipeline.
In this embodiment, by setting the delay type second component, it is ensured that the deployment interval duration between two components having a top-bottom hierarchical relationship in the pipeline service system is long, and the sequential execution of the overall deployment process is realized.
In one embodiment, the pipeline service system adds a second component of a corresponding type to each paired component to ensure the ordered execution of the deployment process between the paired components, and therefore, when the added second component is a pause-type component, as shown in fig. 5, if the deployment verification result is that the verification is passed in step 106, the specific processing procedure of triggering the start condition in the second component includes the following steps:
and 502, if the deployment verification result is that the verification is passed, outputting and displaying the verification passed result.
In implementation, if the deployment verification result of the first component (i.e. the last component) is that the verification is passed, a display data packet containing verification pass information is generated, and the display data packet is read and output for display so as to prompt a user of the current deployment process.
And step 504, responding to the starting request triggered by the verification passing result, and triggering a starting process in the second component.
In implementation, the user inputs a start request for continuing deployment based on the displayed verification passing information, and the computer device triggers a start process in the second component in response to the start request so as to trigger the pipeline service system to continue to start deployment of the next pipeline.
In one embodiment, the type of the second component may further include a timing trigger type, specifically, if the deployment verification result in step 106 is that the verification is passed, the specific processing procedure for triggering the start condition in the second component includes the following steps:
step one, if the deployment verification result is that the verification is passed, reading the preset starting time stamp information in the second assembly, and determining the starting time stamp information as the deployment starting time.
And step two, when the deployment starting time is reached, triggering a starting process in the second assembly.
In implementation, if the next component to be deployed has an explicit deployment start time, the computer device uses the time as a timing time, determines start timestamp information in the second component according to the timing time, and triggers a start process in the second component when the timing time is reached, so as to continue a deployment process in the pipeline service system.
In one embodiment, as shown in FIG. 6, an example of a pipeline deployment method is provided, comprising the steps of:
601, reading configuration parameter information of a first component A and a first component C to be deployed in a first level in the pipeline service system according to a hierarchical architecture among components in the created pipeline service system, and deploying the first component A and the first component C;
step 602, calling a delay type second component, pausing a subsequent deployment process of a first component A in a pipeline service system, and verifying a deployment result of the first component A to obtain a deployment verification result; and calling a timing type second assembly, pausing the subsequent deployment process of the first assembly C in the pipeline service system, and verifying the deployment result of the first assembly C to obtain a deployment verification result.
Step 603, if the deployment verification result is that the verification is 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 a deployment start process, reads the configuration parameter information of the first component B, and deploys the first component B.
And step 604, calling a pause type second component, pausing the subsequent deployment process of the first component B in the pipeline service system, verifying the deployment result of the first component B to obtain a deployment verification result, and outputting and displaying the deployment verification result.
And 605, if the deployment verification result is that the verification is passed, responding to a deployment starting request triggered by a user, triggering a deployment starting process by a second component of a pause type, respectively reading configuration parameter information of a first component A ', a first component B' and a first component C 'to be deployed at the same level, deploying the first component A', the first component B 'and the first component C', verifying the deployment result, and completing the deployment of the pipeline service system.
It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides a pipeline deployment apparatus for implementing the pipeline deployment method mentioned above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so specific limitations in one or more embodiments of the pipeline deployment device provided below may refer to the limitations on the pipeline deployment method in the foregoing, and details are not described here.
In one embodiment, as shown in fig. 7, there is provided a pipeline deployment apparatus 700, comprising: a read module 710, a pause module 720, and a start module 730, wherein:
the reading module 710 is configured to read configuration parameter information of a first component in a pipeline service system, and deploy the first component; the first component is a current component to be deployed which is determined according to a deployment sequence in a pipeline service system;
the suspension module 720 is configured to invoke a 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 for pausing the deployment process in the pipeline service system;
the starting module 730 is configured to trigger a starting process in the second component if the deployment verification result is that the verification is passed, execute the step of reading the configuration parameter information of the first component in the pipeline service system, and deploy the first component until all components to be deployed in the pipeline service system are deployed.
In one embodiment, the apparatus 700 further comprises:
and the stopping module is used for stopping the component deployment process in the pipeline service system if the deployment verification result is that the verification fails.
In one embodiment, the apparatus 700 further comprises:
the acquisition module is used for acquiring configuration files of target components belonging to the same service scene;
the construction module is used for constructing a flow system framework containing the configuration files of the target components according to the business logic relationship among the target components;
and the generating module is used for adding a second assembly between the target assembly and the next adjacent target assembly to obtain a pipeline service system containing each target assembly and the second assembly when the adjacent next target assembly exists in the target assembly in the flow system framework.
In one embodiment, the generation module is configured to divide each target component included in the flow system framework and a next target component adjacent to the target component into a target component pair;
determining a second component of the target type corresponding to the target component pair according to the logical relationship between each target component pair;
and adding the second component of the corresponding target type between the two target components of the target component pair to obtain a pipeline service system containing each target component and the second component.
In one embodiment, the second component is a delay type component, and the starting module 730 is specifically configured to determine, if the deployment verification result is that the verification passes, the deployment start time of the component of the next service type in the pipeline service system according to the timestamp information of the start time of the second component and a preset delay duration in the second component;
when the deployment start time is reached, a start-up procedure in the second component is triggered.
In one embodiment, the second component is a pause type component, and the starting module 730 is specifically configured to output and display a verification passing result if the deployment verification result is that the verification passes;
and triggering the starting process in the second component in response to the starting request triggered by the verification passing result.
The various modules in pipeline deployment apparatus 700 described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 8. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a pipeline deployment method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
and if the deployment verification result is that the verification is not passed, stopping the component deployment process in the pipeline service system.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring configuration files of target components belonging to the same service scene;
constructing a flow system framework containing configuration files of the target components according to the business logic relationship among the target components;
in the flow 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, so as to obtain a pipeline service system including each target component and the second component.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
dividing each target component and a next target component adjacent to the target component contained in the flow system framework into a target component pair;
determining a second component of a target type corresponding to each target component pair according to the logical relationship between each target component pair;
and adding the corresponding second component of the target type between the two target components of the target component pair to obtain a pipeline service system containing each target component and the second component.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
if the deployment verification result is that the verification is passed, determining the deployment starting time of the component of the next service type in the pipeline service system according to the timestamp information of the starting time of the second component and the preset delay time in the second component;
and when the deployment starting time is reached, triggering a starting process in the second component.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
if the deployment verification result is that the verification is passed, outputting and displaying the verification passed result;
and triggering a starting process in the second component in response to a starting request triggered by the verification passing result.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In one embodiment, the computer program when executed by the processor further performs the steps of:
and if the deployment verification result is that the verification is not passed, stopping the component deployment process in the pipeline service system.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring configuration files of target components belonging to the same service scene;
constructing a flow system framework containing configuration files of the target components according to the business logic relationship among the target components;
in the flow 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, so as to obtain a pipeline service system including each target component and the second component.
In one embodiment, the computer program when executed by the processor further performs the steps of:
dividing each target component and a next target component adjacent to the target component contained in the flow system framework into a target component pair;
determining a second component of a target type corresponding to each target component pair according to the logical relationship between each target component pair;
and adding the corresponding second component of the target type between the two target components of the target component pair to obtain a pipeline service system containing each target component and the second component.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the deployment verification result is that the verification is passed, determining the deployment starting time of the component of the next service type in the pipeline service system according to the timestamp information of the starting time of the second component and the preset delay time in the second component;
and when the deployment starting time is reached, triggering a starting process in the second component.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the deployment verification result is that the verification is passed, outputting and displaying the verification passed result;
and triggering a starting process in the second component in response to a starting request triggered by the verification passing result.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
In one embodiment, the computer program when executed by the processor further performs the steps of:
and if the deployment verification result is that the verification is not passed, stopping the component deployment process in the pipeline service system.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring configuration files of target components belonging to the same service scene;
constructing a flow system framework containing configuration files of the target components according to the business logic relationship among the target components;
in the flow 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, so as to obtain a pipeline service system including each target component and the second component.
In one embodiment, the computer program when executed by the processor further performs the steps of:
dividing each target component and a next target component adjacent to the target component contained in the flow system framework into a target component pair;
determining a second component of a target type corresponding to each target component pair according to the logical relationship between each target component pair;
and adding the corresponding second component of the target type between the two target components of the target component pair to obtain a pipeline service system containing each target component and the second component.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the deployment verification result is that the verification is passed, determining the deployment starting time of the component of the next service type in the pipeline service system according to the timestamp information of the starting time of the second component and the preset delay time in the second component;
and when the deployment starting time is reached, triggering a starting process in the second component.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the deployment verification result is that the verification is passed, outputting and displaying the verification passed result;
and triggering a starting process in the second component in response to a starting request triggered by the verification passing result.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims (11)

1. A pipeline deployment method, the method comprising:
reading configuration parameter information of a first component in a pipeline service system, and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence 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 for suspending a deployment process in the pipeline service system;
and if the deployment verification result is that the verification is passed, triggering a starting process in the second assembly, executing the step of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
2. The method of claim 1, further comprising:
and if the deployment verification result is that the verification is not passed, stopping the component deployment process in the pipeline service system.
3. The method of claim 1, further comprising:
acquiring configuration files of target components belonging to the same service scene;
constructing a flow system framework containing configuration files of the target components according to the business logic relationship among the target components;
in the flow 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, so as to obtain a pipeline service system including each target component and the second component.
4. The method of claim 3, wherein adding a second component between the target component and the next adjacent target component results in a pipeline service architecture including each of the target components and the second component, comprising:
dividing each target component and a next target component adjacent to the target component contained in the flow system framework into a target component pair;
determining a second component of a target type corresponding to each target component pair according to the logical relationship between each target component pair;
and adding the corresponding second component of the target type between the two target components of the target component pair to obtain a pipeline service system containing each target component and the second component.
5. The method according to claim 1, wherein the second component is a delay type component, and the triggering a start condition in the second component if the deployment verification result is verification pass comprises:
if the deployment verification result is that the verification is passed, determining the deployment starting time of the component of the next service type in the pipeline service system according to the timestamp information of the starting time of the second component and the preset delay time in the second component;
and when the deployment starting time is reached, triggering a starting process in the second component.
6. The method according to claim 1, wherein the second component is a suspension type component, and the triggering a start condition in the second component if the deployment verification result is verification pass comprises:
if the deployment verification result is that the verification is passed, outputting and displaying the verification passed result;
and triggering a starting process in the second component in response to a starting request triggered by the verification passing result.
7. The method according to claim 1, wherein the second component is a timing type component, and the triggering a start condition in the second component if the deployment verification result is verification pass comprises:
if the deployment verification result is that the deployment verification passes, reading starting timestamp information preset in the second assembly, and determining the starting timestamp information as deployment starting time;
and when the deployment starting time is reached, triggering a starting process in the second component.
8. A pipeline deployment apparatus, the apparatus comprising:
the reading module is used for reading configuration parameter information of a first component in a pipeline service system and deploying the first component; the first component is a current component to be deployed which is determined according to a deployment sequence in the pipeline service system;
the suspension module is used for calling a second assembly in the pipeline service system and verifying the deployment result of the first assembly to obtain a deployment verification result; the second component is a component for suspending a deployment process in the pipeline service system;
and the starting module is used for triggering a starting process in the second assembly if the deployment verification result is that the verification is passed, executing the steps of reading the configuration parameter information of the first assembly in the pipeline service system and deploying the first assembly until all assemblies to be deployed in the pipeline service system are deployed.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
11. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 7 when executed by a processor.
CN202111550099.9A 2021-12-17 2021-12-17 Pipeline deployment method and device, computer equipment and storage medium Pending CN114240369A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111550099.9A CN114240369A (en) 2021-12-17 2021-12-17 Pipeline deployment method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111550099.9A CN114240369A (en) 2021-12-17 2021-12-17 Pipeline deployment method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114240369A true CN114240369A (en) 2022-03-25

Family

ID=80758131

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111550099.9A Pending CN114240369A (en) 2021-12-17 2021-12-17 Pipeline deployment method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114240369A (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140282421A1 (en) * 2013-03-15 2014-09-18 Microsoft Corporation Distributed software validation
CN106469068A (en) * 2015-08-14 2017-03-01 中国移动通信集团安徽有限公司 The dispositions method of application program and system
US20170180459A1 (en) * 2015-12-21 2017-06-22 Amazon Technologies, Inc. Building deployment pipelines for a production computing service using live pipeline templates
WO2017112801A1 (en) * 2015-12-21 2017-06-29 Amazon Technologies, Inc. Live pipeline templates-template creation and extensibility
US20190045360A1 (en) * 2017-08-03 2019-02-07 Salesforce.Com, Inc. Flexible remote server validation
CN110609732A (en) * 2019-08-13 2019-12-24 平安普惠企业管理有限公司 Application program deployment method and device, computer equipment and storage medium
US10678528B1 (en) * 2017-11-21 2020-06-09 Amazon Technologies, Inc. Directory schema deployment with pipelines
US10732962B1 (en) * 2018-04-12 2020-08-04 Amazon Technologies, Inc. End-to-end deployment infrastructure
US10838833B1 (en) * 2018-03-26 2020-11-17 Pure Storage, Inc. Providing for high availability in a data analytics pipeline without replicas
US20210141663A1 (en) * 2019-11-12 2021-05-13 Tata Consultancy Services Limited Systems and methods for automatically creating an image processing pipeline
CN112799813A (en) * 2021-01-28 2021-05-14 中国工商银行股份有限公司 Distributed job service scheduling method, distributed server and service terminal
CN113609019A (en) * 2021-08-09 2021-11-05 山东乾云启创信息科技股份有限公司 Cross-cluster deployment pipeline method and device for container cloud application
CN115080060A (en) * 2022-07-20 2022-09-20 中国工商银行股份有限公司 Application program distribution method, device, equipment, storage medium and program product

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140282421A1 (en) * 2013-03-15 2014-09-18 Microsoft Corporation Distributed software validation
CN106469068A (en) * 2015-08-14 2017-03-01 中国移动通信集团安徽有限公司 The dispositions method of application program and system
US20170180459A1 (en) * 2015-12-21 2017-06-22 Amazon Technologies, Inc. Building deployment pipelines for a production computing service using live pipeline templates
WO2017112801A1 (en) * 2015-12-21 2017-06-29 Amazon Technologies, Inc. Live pipeline templates-template creation and extensibility
US20190045360A1 (en) * 2017-08-03 2019-02-07 Salesforce.Com, Inc. Flexible remote server validation
US10678528B1 (en) * 2017-11-21 2020-06-09 Amazon Technologies, Inc. Directory schema deployment with pipelines
US10838833B1 (en) * 2018-03-26 2020-11-17 Pure Storage, Inc. Providing for high availability in a data analytics pipeline without replicas
US10732962B1 (en) * 2018-04-12 2020-08-04 Amazon Technologies, Inc. End-to-end deployment infrastructure
CN110609732A (en) * 2019-08-13 2019-12-24 平安普惠企业管理有限公司 Application program deployment method and device, computer equipment and storage medium
US20210141663A1 (en) * 2019-11-12 2021-05-13 Tata Consultancy Services Limited Systems and methods for automatically creating an image processing pipeline
CN112799813A (en) * 2021-01-28 2021-05-14 中国工商银行股份有限公司 Distributed job service scheduling method, distributed server and service terminal
CN113609019A (en) * 2021-08-09 2021-11-05 山东乾云启创信息科技股份有限公司 Cross-cluster deployment pipeline method and device for container cloud application
CN115080060A (en) * 2022-07-20 2022-09-20 中国工商银行股份有限公司 Application program distribution method, device, equipment, storage medium and program product

Similar Documents

Publication Publication Date Title
CN109670951B (en) Block chain intelligent contract debugging and publishing method and system
CN112073269B (en) Block chain network testing method, device, server and storage medium
CN106886434A (en) A kind of Distributed Application installation method and device
US20160306656A1 (en) Intelligent application back stack management
CN110795331A (en) Software testing method and device
CN111666138A (en) Timed task processing method, device and system, computer equipment and storage medium
CN118051344A (en) Method and device for distributing hardware resources and hardware resource management system
CN110806935A (en) Application program construction method, device and system
WO2023160418A1 (en) Resource processing method and resource scheduling method
CN117170799A (en) Container migration method, device, computer equipment and storage medium
CN114240369A (en) Pipeline deployment method and device, computer equipment and storage medium
CN113806209A (en) Interface testing method, frame, computer device and storage medium
CN110908644A (en) Configuration method and device of state node, computer equipment and storage medium
CN115134228A (en) Environment link supply and detection method, device, equipment, medium and program product
CN114756293A (en) Service processing method, device, computer equipment and storage medium
CN114020612A (en) Test data construction processing method and device, computer equipment and storage medium
CN108551484B (en) User information synchronization method, device, computer device and storage medium
CN107589978B (en) Method and device for refreshing page in Flash
CN114461443A (en) Display data generation method and device and storage medium
CN113741868A (en) Business calculation task processing method and device, computer equipment and storage medium
CN111258873A (en) Test method and device
RU2816181C1 (en) Method and system for controlling access to software environment resources in geosteering services
CN118018552B (en) Cluster service deployment method and device based on middleware and computer equipment
CN115730016B (en) Data synchronization method, system, device, computer equipment and storage medium
CN116820558A (en) Application program development method, device, equipment, storage medium and program product

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