CN115545375A - Continuous integration system and operation method thereof - Google Patents

Abstract

The invention provides a continuous integration system and an operation method thereof, which are characterized in that product demand information is obtained, the product demand information is converted into a work order of a corresponding work order type based on an OTRS platform and is operated, when the work order operation is monitored to be finished, an OTRS Webservice interface is used for sending an automation request to trigger an automation program, and the automation process is executed, so that an automation deployment assembly line is obtained. In the scheme, the work order is determined by the OTRS platform, and the OTRS Webservice interface is used for triggering the automatic flow, so that the arrangement of the product assembly line is automatically completed, the labor cost is reduced, the work complexity is reduced, and the efficiency of constructing the product assembly line is improved.

Description

A continuous integration system and its operation method

technical field

The present invention relates to the field of computer technology, in particular to a continuous integration system and an operation method thereof.

Background technique

At present, in the product development process, the usual product development and delivery process is as follows: According to the traditional technical organization structure, each technical department builds its own tool platform, and cooperates to complete product development and delivery through product.

Using the above method for product development and delivery, various technical departments need to cooperate with each other to complete product development and delivery. In the process of collaboration between multiple tool platforms, duplication of work and communication problems may occur, thus increasing system development and The labor cost and work complexity in the delivery process will reduce work efficiency.

Contents of the invention

In view of this, the embodiment of the present invention provides a continuous integration system and its operation method to solve the problems of high labor cost, high work complexity and low work efficiency in the existing product development process.

In order to achieve the above purpose, embodiments of the present invention provide the following technical solutions:

On the one hand, the embodiment of the present invention discloses an operation method of a continuous integration system, the operation method comprising:

Obtain product demand information, convert the product demand information into work orders of corresponding work order types based on the OTRS platform, and run them. The work order types include access work orders and execution work orders, and each work order Include at least one workflow information;

After monitoring that the work order is completed, use the OTRS Webservice interface to send an automation request to trigger the automation program, and execute the automation process to obtain an automated deployment pipeline, wherein the automation request includes the work order;

The automated processes include:

Analyzing the work order, obtaining corresponding workflow information, and storing it;

Match each workflow information with the pre-set jenkins pipeline template to get the code needed to build the pipeline;

Build the pipeline corresponding to the product based on the jenkins platform and the code.

Optionally, also include:

Real-time acquisition of intermediate data generated during the process of building the pipeline corresponding to the product;

A product test report is generated based on the intermediate data.

Optionally, when it is detected that the work order is completed, it includes:

Each work order event generated when the state of the work order changes is monitored in real time until the work order event indicates that the state of the work order is completed, and it is determined that the operation of the work order is completed.

Optionally, the parsing of the work order to obtain and store corresponding workflow information includes:

determining a work order type of said work order contained in said automation request;

If there are access work orders and execution work orders at the same time, or there are only access work orders or execution work orders, the workflow sequence and each The node information of the workflow is stored in the python-jenkins library.

Optionally, match each workflow information with the pre-set jenkins pipeline template to obtain the code required to build the pipeline, including:

Match the node information of each workflow with the preset jenkins pipeline template, and confirm the jenkins pipeline template corresponding to the node information of each workflow;

Obtain the codes corresponding to the jenkins pipeline template, sort the codes based on the workflow order, and obtain the codes required to build the pipeline.

Optionally, if the code required to build the pipeline only includes the unique pipeline code, it also includes:

Get the general pipeline code needed to build the pipeline;

Construct the pipeline corresponding to the product based on the jenkins platform, the unique pipeline code and the general pipeline code.

On the other hand, the embodiment of the present invention discloses a continuous integration system, including:

The acquisition module is used to obtain the user's product demand information, convert the product demand information into a work order of the corresponding work order type based on the OTRS platform, and run it, and when the operation of the work order is monitored, use the OTRS Webservice interface to The automation module sends an automation request to trigger the automation program, the work order type includes an access work order and an execution work order, and each work order includes at least one workflow information, and the automation request includes the work order;

The automation module is configured to use the Devops platform to analyze the work order, obtain corresponding workflow information, and store it, and match each workflow information with a pre-set jenkins pipeline template to obtain the code required to build the pipeline , and build the pipeline corresponding to the product based on the jenkins platform and the code.

Optionally, the acquisition module that monitors the operation of the work order is specifically used for:

Each work order event generated when the state of the work order changes is monitored in real time until the work order event indicates that the state of the work order is completed, and it is determined that the operation of the work order is completed.

Optionally, the automation module that uses the Devops platform to parse the work order to obtain and store the work order information is specifically used for:

Determine the work order type of the work order contained in the automation request; if there are both access work orders and execution work orders, or only access work orders or execution work orders, based on the work order The work order types of the order are analyzed separately, and the obtained workflow sequence and node information of each workflow are stored in the python-jenkins library.

Optionally, each workflow information is matched with a pre-set jenkins pipeline template to obtain the automation module of the code required to build the pipeline, specifically for:

Match the node information of each workflow with the preset jenkins pipeline template, confirm the jenkins pipeline template corresponding to the node information of each workflow; obtain the code corresponding to the jenkins pipeline template, and compare the code based on the workflow sequence Sort to get the code needed to build the pipeline.

Based on the continuous integration system and its operating method provided by the above-mentioned embodiments of the present invention, by obtaining product demand information, the product demand information is converted into a work order of the corresponding work order type based on the OTRS platform, and the operation is performed. After the work order is run, use the OTRS Webservice interface to send an automation request to trigger the automation program, and execute the automation process to obtain an automated deployment pipeline. The automation request includes the work order; the automation process includes: parsing Describe the work order, get the corresponding workflow information, and store it; match each workflow information with the pre-set jenkins pipeline template to get the code needed to build the pipeline; build the pipeline corresponding to the product based on the jenkins platform and the code . In this solution, the OTRS platform is used to determine the work order, and then the OTRS Webservice interface is used to trigger the automated process, thereby automatically completing the deployment of the product pipeline, which not only reduces labor costs, but also reduces work complexity and improves the efficiency of building product pipelines.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

FIG. 1 is a schematic diagram of an operating framework of a continuous integration system disclosed in an embodiment of the present invention;

Fig. 2 is a schematic flow chart of an operating method of a continuous integration system disclosed in an embodiment of the present invention;

FIG. 3 is a schematic flowchart of another continuous integration system operating method disclosed in an embodiment of the present invention;

Fig. 4 is a schematic structural diagram of a continuous integration system disclosed by an embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

In this application, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes none. other elements specifically listed, or also include elements inherent in such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

It can be seen from the background art that in the existing product development and delivery method, each technical department builds a tool platform and cooperates to complete the product development and delivery through the product. In the process of collaboration among multiple tool platforms, duplication of work and communication problems may occur, which increases labor costs and work complexity in the system development and delivery process, thereby reducing work efficiency.

Therefore, the embodiment of the present invention discloses a continuous integration system and its operation method. The OTRS platform is used to determine the work order, and then the OTRS Webservice interface is used to trigger the automation process, thereby automatically completing the deployment of the product pipeline, which not only reduces labor costs, but also The work complexity is reduced, and the efficiency of building product pipelines is improved. Specifically, it will be described in detail through the following examples.

As shown in FIG. 1 , it is a schematic diagram of an operating architecture of a continuous integration system disclosed in an embodiment of the present invention, mainly including: OTRS, oh-my-devops and jenkins.

Among them, OTRS is an open source website application installed on a server and can be accessed through a browser. The main module of OTRS is the OTRS framework, which mainly contains all the core functions of the application and ticket system. In the embodiment of the present invention, the work order module of OTRS is mainly used as an interface for customers and service personnel. And use the custom process work order of the work order module of OTRS and the function of recording work order status flow.

OTRS integrates internal and external communication using tickets. Tickets are organized in queues. Tickets can be modified in many ways, such as replying, forwarding, bouncing, switching to another queue, updating attributes (status, priority, etc.), locking and counting hours. It is also possible to modify multiple work orders in batches, that is, batch operations.

All changes to a ticket are recorded through the ticket history.

In addition, the search function of OTRS supports complex and full-text searches for tickets.

In a specific implementation, firstly, the user's product demand information is obtained, and the product demand information is converted into a work order of a corresponding work order type based on the OTRS platform, and executed. Work order types include access work orders and execution work orders, and each work order includes at least one piece of workflow information.

Then, check the work order flow status in the system, that is, view the queue, status, upgrade status, etc., and you can also view the detailed information of the work order according to the level (simple/basic/preview). When it is checked that the work order transfer is completed, that is, after the work order has been run, use the Webservice interface of OTRS to send an automation request to trigger the automation program.

The automation program is implemented based on oh-my-devops and jenkins.

Among them, the oh-my-devops platform combines OTRS and jenkins, and transforms the compilation and deployment of the pipeline into automation. And all kinds of data generated in the process of automatically establishing the pipeline are stored in the database to ensure the reliability and effectiveness of operation and maintenance management.

Jenkins is an open source software product, which can be customized according to the needs of each system, including functions such as continuous and regular compilation, report generation, and sending to emails.

In the specific implementation, firstly, according to different types of work orders, different work orders are parsed on the oh-my-devops platform, and the corresponding workflow information is obtained and stored. Specifically, the oh-my-devops platform includes an access module and an execution module.

Then, match each workflow information with the pre-set Jenkins pipeline template to obtain the code needed to build the pipeline.

Finally, build the pipeline corresponding to the product based on the jenkins platform and the code.

At the same time, in the process of building the pipeline corresponding to the product based on the jenkins platform, the product can also be tested based on the test module of the jenkins platform and a product test report can be generated.

Based on the operating framework of the continuous integration system disclosed in the above-mentioned embodiments of the present invention, the OTRS platform is used to determine the work order, and then the OTRS Webservice interface is used to trigger the automation process, thereby automatically completing the deployment of the product pipeline, which not only reduces labor costs, but also reduces work costs. Complexity, improving the efficiency of building product pipelines.

Based on the operating framework of the continuous integration system disclosed in the above-mentioned embodiments of the present invention, the embodiment of the present invention also discloses an operating method of the continuous integration system, as shown in FIG. 2 , which mainly includes the following steps:

S201: Obtain product demand information, convert the product demand information into a work order of a corresponding work order type based on the OTRS platform, and execute the operation.

In S201, the work order types include access work orders and execution work orders, and each work order includes at least one piece of workflow information.

Access tickets contain workflows that connect or relate to the entire product.

Execution work orders include workflows that are specifically executed to obtain a certain execution result.

S202: Monitor whether the work order is completed, if it is completed, execute S203, if not, continue to execute S202.

During the specific execution of S202, monitor each work order event generated when the state of the work order changes in real time, until the work order event indicates that the work order status is a completed state, and determine that the work order is completed.

The change of the work order status here is equivalent to the work order flow status involved in the above-mentioned embodiments.

S203: Using the OTRS Webservice interface to send an automation request to trigger the execution of S204 to S206.

In S203, the automation request includes the work order.

In the process of implementing S203, a perl script is used to send an automation request using the OTRS Webservice interface to trigger the execution of S204 to S206.

Wherein, S204 to S206 are automation programs, and the automatic deployment pipeline can be obtained by executing the automation process.

The automated processes include:

S204: Analyze the work order to obtain corresponding workflow information and store it.

In the process of implementing S204, based on determining the work order type of the work order included in the automation request.

If there are access work orders and execution work orders at the same time, analyze the access work orders and execution work orders respectively to obtain their corresponding workflows, and follow the sequence of workflows and the nodes of each workflow Information is stored in the python-jenkins library.

If there are only access work orders, analyze the access work orders, and store the obtained workflows in the python-jenkins library according to the workflow sequence and the node information of each workflow.

If there are only execution work orders, analyze the execution work orders, and store the obtained workflows in the python-jenkins library according to the workflow sequence and the node information of each workflow.

S205: Match each workflow information with the pre-set jenkins pipeline template to obtain the code required to build the pipeline.

In S205, the jenkins pipeline template is used to generate a pipeline configuration closely related to the product, including all parameters required for compiling, building and deploying the application.

In the process of implementing S205, firstly, the node information of each workflow is matched with the preset jenkins pipeline template, and the jenkins pipeline template corresponding to the node information of each workflow is confirmed.

Secondly, the code corresponding to the jenkins pipeline template is obtained, and the codes are sorted based on the sequence of the workflow to obtain the code required for building the pipeline.

S206: Build a pipeline corresponding to the product based on the jenkins platform and the code.

It should be noted that if the code required to build the pipeline only includes the unique pipeline code, you need to obtain the general pipeline code required to build the pipeline; build products based on the jenkins platform, the unique pipeline code and the general pipeline code corresponding pipeline.

The unique pipeline code refers to the product-specific pipeline code, and the general pipeline code refers to the parameters required for the compilation pipeline provided in the initial access work order.

Table 1 below shows some parameters involved in the compilation task when building the pipeline. Table 2 shows some parameters involved in the release/rollback task when building the pipeline.

Table 1:

Table 2:

Based on the operating method of the continuous integration system disclosed in the above-mentioned embodiments of the present invention, the OTRS platform is used to determine the work order, and then the OTRS Webservice interface is used to trigger the automation process, thereby automatically completing the deployment of the product pipeline. This process integrates the continuous integration and deployment process into A complete automated process makes the collaboration between the development and operation and maintenance teams more efficient, and at the same time reduces the requirements for the professional knowledge of operators. That is to say, the process of automatically deploying the pipeline through the operating method of the continuous integration system disclosed in the embodiment of the present invention not only reduces labor costs, but also reduces work complexity and improves the efficiency of building product pipelines.

Based on the operating method of a continuous integration system disclosed in the above-mentioned embodiments of the present invention, as shown in FIG. 3 , the embodiment of the present invention also discloses another operating method of the continuous integration system, which mainly includes the following steps:

S301: Obtain product demand information, convert the product demand information into a work order of a corresponding work order type based on the OTRS platform, and execute the operation.

S302: Monitor whether the work order is completed, if it is completed, execute S303, if not, continue to execute S302.

S303: Using the OTRS Webservice interface to send an automation request to trigger the execution of S304 to S308.

S304: Analyze the work order, obtain corresponding workflow information, and store it;

S305: Match each workflow information with the preset jenkins pipeline template to obtain the code required to build the pipeline;

S306: Build a pipeline corresponding to the product based on the jenkins platform and the code.

The execution principles and processes of S301 to S306 above are the same as the execution principles and processes of S201 to S206 disclosed in FIG. 2 , and will not be repeated here.

S307: Obtain in real time the intermediate data generated during the process of building the pipeline corresponding to the product.

S308: Generate a product test report based on the intermediate data.

In the process of implementing S308, a product test report can be generated through the obtained intermediate data, and based on the product test report, it can be determined whether there is a problem in each stage of the product development. If there is a problem, make corrections in time according to the product test report.

Based on the operating method of the continuous integration system disclosed in the above-mentioned embodiments of the present invention, the OTRS platform is used to determine the work order, and then the OTRS Webservice interface is used to trigger the automation process, thereby automatically completing the deployment of the product pipeline. This process integrates the continuous integration and deployment process into A complete automated process makes the collaboration between the development and operation and maintenance teams more efficient, and at the same time reduces the requirements for the professional knowledge of operators. That is to say, the process of automatically deploying the pipeline through the operating method of the continuous integration system disclosed in the embodiment of the present invention not only reduces labor costs, but also reduces work complexity and improves the efficiency of building product pipelines.

Based on the operation method of the continuous integration system disclosed in the above-mentioned embodiments of the present invention, the embodiment of the present invention also discloses a corresponding continuous integration system, as shown in FIG. 4 , which mainly includes:

The acquisition module 401 is used to acquire product demand information, convert the product demand information into a work order of the corresponding work order type based on the OTRS platform, and run it. The module sends an automation request to trigger the automation module 402. The work order type includes an access work order and an execution work order. Each work order includes at least one workflow information, and the automation request includes the work order.

During the process of monitoring the operation of the work order, the acquiring module 401 is specifically used for:

Each work order event generated when the state of the work order changes is monitored in real time until the work order event indicates that the state of the work order is completed, and it is determined that the operation of the work order is completed.

The automation module 402 is configured to use the Devops platform to analyze the work order, obtain the corresponding workflow information, and store it, and match each workflow information with the preset jenkins pipeline template to obtain the code required to build the pipeline, And build the pipeline corresponding to the product based on the jenkins platform and the code.

When the specific implementation utilizes the Devops platform to parse the work order, obtain the work order information and store it, the automation module 402 is specifically used for:

Determine the work order type of the work order contained in the automation request; if there are both access work orders and execution work orders, or only access work orders or execution work orders, based on the work order The work order types of the order are analyzed separately, and the obtained workflow sequence and node information of each workflow are stored in the python-jenkins library.

When matching each workflow information with the preset jenkins pipeline template to obtain the code needed to build the pipeline, the automation module 402 is specifically used for:

Match the node information of each workflow with the preset jenkins pipeline template, confirm the jenkins pipeline template corresponding to the node information of each workflow; obtain the code corresponding to the jenkins pipeline template, and compare the code based on the workflow sequence Sort to get the code needed to build the pipeline.

If the code required to build the pipeline only includes the unique pipeline code, the automation module 402 is also used for:

Obtain the general pipeline code required to build the pipeline; build the pipeline corresponding to the product based on the jenkins platform, the unique pipeline code and the general pipeline code.

Based on the continuous integration system disclosed in the above-mentioned embodiments of the present invention, the OTRS platform is used to determine the work order, and then the OTRS Webservice interface is used to trigger the automation process, thereby automatically completing the deployment of the product pipeline. This process integrates the continuous integration and deployment process into a complete The automated process makes the collaboration between development and operation and maintenance teams more efficient, and at the same time reduces the requirements for the professional knowledge of operators. That is to say, the process of automatically deploying the pipeline through the operating method of the continuous integration system disclosed in the embodiment of the present invention not only reduces labor costs, but also reduces work complexity and improves the efficiency of building product pipelines.

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A running method of a continuous integration system, characterized in that, the running method comprises: Obtain product demand information, convert the product demand information into work orders of corresponding work order types based on the OTRS platform, and run them. The work order types include access work orders and execution work orders, and each work order Include at least one workflow information; After monitoring that the work order is completed, use the OTRS Webservice interface to send an automation request to trigger the automation program, and execute the automation process to obtain an automated deployment pipeline, wherein the automation request includes the work order; The automated processes include: Analyzing the work order, obtaining corresponding workflow information, and storing it; Match each workflow information with the pre-set jenkins pipeline template to get the code needed to build the pipeline; Build the pipeline corresponding to the product based on the jenkins platform and the code. 2. The method according to claim 1, further comprising: Real-time acquisition of intermediate data generated during the process of building the pipeline corresponding to the product; A product test report is generated based on the intermediate data. 3. The method according to claim 1, wherein when it is detected that the work order is completed, it comprises: Each work order event generated when the state of the work order changes is monitored in real time until the work order event indicates that the state of the work order is completed, and it is determined that the operation of the work order is completed. 4. The method according to claim 1, wherein said parsing said work order to obtain corresponding workflow information and store it comprises: determining a work order type of said work order contained in said automation request; If there are access work orders and execution work orders at the same time, or there are only access work orders or execution work orders, the workflow sequence and each The node information of the workflow is stored in the python-jenkins library. 5. The method according to claim 4, wherein said matching each workflow information with a preset jenkins pipeline template to obtain the required code for building the pipeline, including: Match the node information of each workflow with the preset jenkins pipeline template, and confirm the jenkins pipeline template corresponding to the node information of each workflow; Obtain the codes corresponding to the jenkins pipeline template, sort the codes based on the workflow order, and obtain the codes required to build the pipeline. 6. The method according to claim 1, wherein if the code required to obtain the construction pipeline only includes unique pipeline code, it also includes: Get the general pipeline code needed to build the pipeline; Construct the pipeline corresponding to the product based on the jenkins platform, the unique pipeline code and the general pipeline code. 7. A continuous integration system, characterized in that it comprises: The acquisition module is used to obtain the user's product demand information, convert the product demand information into a work order of the corresponding work order type based on the OTRS platform, and run it, and when the operation of the work order is monitored, use the OTRS Webservice interface to The automation module sends an automation request to trigger the automation program, the work order type includes an access work order and an execution work order, and each work order includes at least one workflow information, and the automation request includes the work order; The automation module is configured to use the Devops platform to analyze the work order, obtain corresponding workflow information, and store it, and match each workflow information with a pre-set jenkins pipeline template to obtain the code required to build the pipeline , and build the pipeline corresponding to the product based on the jenkins platform and the code. 8. The system according to claim 7, wherein the acquisition module that monitors the operation of the work order is specifically used for: Each work order event generated when the state of the work order changes is monitored in real time until the work order event indicates that the state of the work order is completed, and it is determined that the operation of the work order is completed. 9. system according to claim 7, is characterized in that, described utilizes Devops platform to analyze described work order, obtains the automation module of work order information and storage, is specifically used for: Determine the work order type of the work order contained in the automation request; if there are both access work orders and execution work orders, or only access work orders or execution work orders, based on the work order The work order types of the order are analyzed separately, and the obtained workflow sequence and node information of each workflow are stored in the python-jenkins library. 10. The system according to claim 9, wherein the automation module for matching each workflow information with the preset jenkins pipeline template to obtain the code required for building the pipeline is specifically used for: Match the node information of each workflow with the preset jenkins pipeline template, confirm the jenkins pipeline template corresponding to the node information of each workflow; obtain the code corresponding to the jenkins pipeline template, and compare the code based on the workflow sequence Sort to get the code needed to build the pipeline.

Images