CN111506304A - Assembly line construction method and system based on parameter configuration - Google Patents
Assembly line construction method and system based on parameter configuration Download PDFInfo
- Publication number
- CN111506304A CN111506304A CN202010317612.9A CN202010317612A CN111506304A CN 111506304 A CN111506304 A CN 111506304A CN 202010317612 A CN202010317612 A CN 202010317612A CN 111506304 A CN111506304 A CN 111506304A
- Authority
- CN
- China
- Prior art keywords
- plug
- project
- pipeline
- parameter configuration
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000010276 construction Methods 0.000 title claims abstract description 48
- 238000000034 method Methods 0.000 claims abstract description 27
- 230000008569 process Effects 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 7
- 230000000007 visual effect Effects 0.000 claims description 4
- 238000013515 script Methods 0.000 abstract description 16
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000004519 manufacturing process Methods 0.000 abstract description 7
- 238000012827 research and development Methods 0.000 abstract description 4
- 238000011161 development Methods 0.000 abstract description 3
- 238000012360 testing method Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 6
- 230000010354 integration Effects 0.000 description 4
- 238000010367 cloning Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
Abstract
The invention discloses a method and a system for constructing a production line based on parameter configuration, which belong to the technical field of computer software and comprise the following steps: s1: compiling a plug-in project; s2: configuring a plug-in project; s3: editing the flow; s4: selecting a plug-in; s5: a single step of construction; s6: all steps are constructed. The invention can edit a CI & CD assembly line without learning and compiling shell scripts, thereby saving the learning cost and time for users, reducing the threshold of the users and enlarging the range of the users; all personnel in a research and development team can participate in the continuous construction/deployment work, and can be used by non-operation and maintenance personnel, so that better cooperation between development and operation and maintenance is realized; the plug-in project is zero-coupled with other codes of the whole platform, and users can develop the plug-in project by themselves to finish the work they want to do; and the contents displayed in the log are filtered and processed, so that the contents of the log in the hybrid system become concise and direct.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a method and a system for constructing a production line based on parameter configuration.
Background
CI (Continuous integration) is a software development practice, the working principle of CI is shown IN FIG. 1, and after a developer submits new code (CHECK-IN IN FIG. 1) to a code management repository (SOURCEREPOSITY IN FIG. 1), the CI server immediately performs build (BUI L D), (Unit) TEST (TEST), and according to the TEST result (RESU L T), it can be determined whether the new code and the original code can be correctly integrated together.
The CD (Continuous Delivery) deploys the integrated code into a more real-running environment (class production environment) on the basis of Continuous integration. The general operating mode of the CI & CD is shown in fig. 2. In the example of FIG. 2, the CD is just after the unit test of the CI, and the code can be deployed to the Staging environment connected to the database for further testing. If the code has no problems, manual deployment to the production environment can continue.
In order to realize the working mode of the CI & CD, a set of CI & CD pipeline configuration tools cannot be left. Many software and internet vendors have their own products and solutions, some of which are limited to their use within the company and some of which choose to be open source or commercial.
For example, amazon provides a set of flexible services on a cloud platform, and a user can select services by self through functions required by continuous construction of each link, so that a set of CI & CD tools are selected by self; the Baidu efficiency cloud provides a DevOps toolchain, which comprises code management, code scanning, interface testing, containerization compiling, a cloud native micro-service platform and the like, and the core of the DevOps toolchain is also a solution for realizing a set of CI & CD; the arisco also provides a DevOps enterprise research and development performance (cloud efficiency) platform, which aims at the enterprise-level project demand management, continuous integrated continuous delivery platform architecture, deep integration with middleware and container service and promotion of delivery value.
There are many larger products such as the above, but the most widely spread and used CI tool belongs to Jenkins. Jenkins is an open-source continuous integration tool providing friendly operation interface, originated from Hudson (Hudson is a commercial tool), and is mainly used for continuously and automatically building/testing software projects and monitoring the running of external tasks. Jenkins are written in Java language, and can run in popular servlet containers such as Tomcat and the like and can also run independently. Typically used in conjunction with a version management tool (SCM), build tool. Common version control tools comprise SVN and GIT, and construction tools comprise Maven, Ant and Gradle.
The compiling of the shell script cannot be carried out no matter the tool provided by the cloud platform of the large factory or the pipeline configuration of Jenkins. For example, the "build" process in Jenkins configuration tasks, requires the input of shell scripts, as shown in fig. 3.
Similar functions are realized on other platforms, and shell scripts which are different in size are required to be input, and are not illustrated.
The process of building/testing can be made more flexible by writing shell scripts, but this means that the user needs to have a good understanding of the resources, environment, and components on the server, not to mention the skilled mastering of shell programming. Therefore, a CI & CD tool for writing scripts is needed, which has a certain threshold for entering the door, and after the door is stepped through, the operation condition of the server needs to be known enough during the use process to be used stably and correctly.
The working mode of the CI & CD is essentially to improve the efficiency of construction and deployment, and the value of Jenkins is already embodied, but the premise is that task configuration is correct, and the configuration task cannot leave the shell script. Non-professional operation and maintenance personnel, such as developers who are not well aware of the server environment, have difficulty smoothly using pipelining to do CI & CD work. The above-mentioned problems need to be solved, and therefore, a pipeline construction method based on parameter configuration is proposed.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: how to solve the problems that the configuration task can not leave the shell script and the non-professional operation and maintenance personnel can hardly and smoothly use the pipeline to do CI & CD work in the existing CI & CD working mode, and a visualized pipeline construction method based on parameter configuration is provided.
The invention solves the technical problems through the following technical scheme, and the invention comprises the following steps:
s1: writing plug-in project
Compiling a plug-in project, and integrating the plug-in project into a pipeline project;
s2: configuration plug-in engineering
After the plug-in project is integrated into the assembly line project, configuring relevant parameters and attributes of the plug-in project;
s3: editing process
Editing the flow and the basic information;
s4: selection plug-in
Selecting a corresponding plug-in icon, and performing parameter configuration on the plug-in;
s5: construction of a Single step
Saving the parameter configuration of the plug-in the step S4, and saving the parameter configuration;
s6: all steps of construction
And repeating the steps S1-S5, selecting all the required plug-ins, finishing all the plug-ins selection, and finishing the pipeline construction after all the step configuration is stored.
Furthermore, the operations of steps S2-S6 are all performed on a visual page.
Further, in step S2, the attributes of the plug-in project include a plug-in name, a plug-in path, a plug-in implementation class, a plug-in type, a plug-in version number, a plug-in icon, and the like, and the related parameters of the plug-in project include a parameter name, an input type, a pre-value, a default value, a parameter code, a parameter description, and the like.
Further, in step S3, the basic information includes a pipeline name, an item to which the pipeline belongs, whether the pipeline is default, a trigger mode, and a remark.
Further, in the step S3, the editing of the flow is completed by the illustrated editing mode.
Further, in step S4, the plug-in is configured by selecting or inputting parameters.
Furthermore, after the assembly line is constructed, whether the assembly line is operated or not is selected according to requirements, and after the operation is finished, the log can be checked.
Furthermore, each step in the assembly line is called one by the background assembly line scheduling center in sequence during running, after each calling is finished, the plug-in project returns a step log object, the assembly line scheduling center takes out and stores the log information in the step log object, and finally returns a main log of the assembly line, and the main log can be associated with each step log.
Further, in step S6, each configured step is converted into json format data, and the json format data is sent to the pipeline scheduling center, and the pipeline scheduling center sends the json format data to each plug-in project, and the plug-in project completes the execution of the plug-in by parsing the json format data.
The invention also provides a production line construction system based on parameter configuration, which comprises:
the plug-in project compiling module is used for compiling plug-in projects and integrating the plug-in projects into the pipeline projects;
the plug-in project configuration module is used for configuring relevant parameters and attributes of the plug-in project after the plug-in project is integrated into the assembly line project;
the flow editing module is used for editing the flow and the basic information;
the plug-in project selection module is used for selecting a corresponding plug-in icon and performing parameter configuration on the plug-in;
the single-step construction module is used for storing the parameter configuration of the selected plug-in and storing the step;
the all-step construction module is used for selecting all required plug-ins, finishing all the selection of the plug-ins and finishing the assembly line construction after all the step configurations are stored;
the control processing module is used for controlling each module and executing related instructions;
the plug-in project compiling module, the plug-in project configuration module, the flow editing module, the plug-in project selecting module, the single-step building module and the all-step building module are connected with the control processing module.
Compared with the prior art, the invention has the following advantages: according to the streamline construction method based on parameter configuration, a CI & CD streamline can be edited without learning and compiling shell scripts, so that the learning cost and time are saved for a user, the threshold of the user is reduced, and the user range is expanded; because the shell script is removed, namely, the user is allowed to have no knowledge about the server environment, the server is transparent to the user, all personnel in a research and development team can participate in the continuous construction/deployment work, and can be used by non-operation and maintenance personnel, so that better cooperation between development and operation and maintenance is realized; the plug-in project is zero-coupled with other codes of the whole platform, and users can develop the plug-in project by themselves to finish the work they want to do; and the contents displayed in the log are filtered and processed, so that the contents of the log in the hybrid system become concise and direct, and users can directly see the contents which are most concerned by the users.
Drawings
FIG. 1 is a schematic diagram of the operation of a CI according to the prior art;
FIG. 2 is a schematic diagram of the operation mode of a CI & CD in the prior art;
FIG. 3 is a diagram of an operation interface for inputting shell scripts in the prior art;
FIG. 4 is a schematic overall flowchart of a pipeline construction method according to an embodiment of the present invention;
FIG. 5 is an overall architecture diagram of a CI & CD solution based on parameter configuration according to a second embodiment of the present invention;
FIG. 6 is an interface diagram of the operation performed by the user when configuring the docker plug-in the second embodiment of the present invention;
FIG. 7 is a flow chart of a complete CI & CD plus test in the second embodiment of the present invention;
FIG. 8 is an interface diagram of the step of configuring git according to the second embodiment of the present invention;
FIG. 9 is a schematic diagram of an engineering structure of a pipeline engineering according to a second embodiment of the present invention;
FIG. 10 is a diagram of a pipeline log viewing interface in accordance with a second embodiment of the present invention;
FIG. 11 is a diagram of a configuration operation interface of the Git plug-in project in the third embodiment of the present invention;
FIG. 12 is a diagram of an operation interface of a new step in the pipeline according to a third embodiment of the present invention;
fig. 13 is a view of a parameter configuration operation interface of the gitlab plug-in at the front end in the third embodiment of the present invention;
FIG. 14 is a schematic diagram of a complete CI & CD pipeline with test functions according to a third embodiment of the present invention;
FIG. 15 is a cross-sectional view of an automatic log page pop-up according to a third embodiment of the present invention;
fig. 16 is a view of a pipeline log viewing interface in the third embodiment of the present invention.
Detailed Description
The following examples are given for the detailed implementation and specific operation of the present invention, but the scope of the present invention is not limited to the following examples.
As shown in fig. 4, the present embodiment provides a technical solution: a pipeline construction method based on parameter configuration comprises the following steps:
s1: writing plug-in project
Compiling a plug-in project, and integrating the plug-in project into a pipeline project;
s2: configuration plug-in engineering
After the plug-in project is integrated into the assembly line project, configuring relevant parameters and attributes of the plug-in project;
s3: editing process
Editing the flow and the basic information;
s4: selection plug-in
Selecting a corresponding plug-in icon, and performing parameter configuration on the plug-in;
s5: construction of a Single step
Saving the parameter configuration of the plug-in the step S4, and saving the parameter configuration;
s6: all steps of construction
And repeating the steps S1-S5, selecting all the required plug-ins, finishing all the plug-ins selection, and finishing the pipeline construction after all the step configuration is stored.
The operations of the steps S2-S6 are all performed on a visual page.
In step S2, the attributes of the plug-in project include a plug-in name, a plug-in path, a plug-in implementation class, a plug-in type, a plug-in version number, a plug-in icon, and the like, and the related parameters of the plug-in project include a parameter name, an input type, a pre-value, a default value, a parameter code, a parameter description, and the like.
In step S3, the basic information includes the pipeline name, the item to which the pipeline belongs, whether the pipeline is default, the trigger mode, and the remark.
In step S3, the editing of the flow is completed by the illustrated editing mode.
In step S4, the parameter configuration of the plug-in is performed by selecting or inputting parameters.
After the assembly line is constructed, whether the assembly line is operated or not is selected according to requirements, and after the operation is finished, the log can be checked.
Each step in the assembly line is called one by the background assembly line scheduling center in sequence during running, after each calling is finished, the plug-in project returns a step log object, the assembly line scheduling center takes out and stores the log information in the step log object, and finally returns a main log of the assembly line, and the main log can be associated with each step log.
In step S6, each configured step is converted into json-format data, and the json-format data is sent to the pipeline scheduling center, and the pipeline scheduling center sends the data to each plug-in project, and the plug-in project completes the execution of the plug-ins by analyzing the data.
The embodiment also provides a pipeline construction system based on parameter configuration, which includes:
the plug-in project compiling module is used for compiling plug-in projects and integrating the plug-in projects into the pipeline projects;
the plug-in project configuration module is used for configuring relevant parameters and attributes of the plug-in project after the plug-in project is integrated into the assembly line project;
the flow editing module is used for editing the flow and the basic information;
the plug-in project selection module is used for selecting a corresponding plug-in icon and performing parameter configuration on the plug-in;
the single-step construction module is used for storing the parameter configuration of the selected plug-in and storing the step;
the all-step construction module is used for selecting all required plug-ins, finishing all the selection of the plug-ins and finishing the assembly line construction after all the step configurations are stored;
the control processing module is used for controlling each module and executing related instructions;
the plug-in project compiling module, the plug-in project configuration module, the flow editing module, the plug-in project selecting module, the single-step building module and the all-step building module are connected with the control processing module.
Example two
Based on the problems in the background art and the prior art, the present embodiment provides a CI & CD solution based on parameter configuration, and the overall architecture of the solution is shown in fig. 5: and a visual friendly page is provided for the user, so that the user can edit the CI & CD pipeline. In the editing process, the user does not need to input any script language or command, and only needs to simply fill in or select the parameters of the selected plug-in. The operation of the pipeline sends the request of the front end to the pipeline project of the back end. The assembly line dispatching center in the assembly line engineering can analyze the content in the assembly line and call the plug-in engineering one by one according to the step sequence, thereby finishing the execution of the assembly line. And finally, generating and storing the log, and automatically popping up the log on the page for the user to view.
The following explains the core technical points in the solution:
firstly, a pipeline editing process based on parameter configuration:
a set of CI & CD/test assembly line can be completed only by filling in/selecting related parameters without compiling shell scripts, and the core of the solution is provided. Taking Jenkins as an example for constructing a mirror image, in the process of constructing the mirror image, a user needs to copy a packet which is well printed in the compiling process to a specified position through a shell command, and then starts the packet through a script command, and before this, the process may need to be killed, so that the normal starting of a jar packet can be ensured.
In the pipeline editing process of the solution, no shell command needs to be written, only some parameters wait for the user to configure on the page, and many parameters have given default values, so that the user experience is very good. As shown in fig. 6, the parameters are required to be filled in when the user configures the docker plug-in.
Compared with the commands in the row of fig. 3, fig. 6 only needs to fill in parameters and select commands, is more user-friendly, and achieves zero technical threshold. In addition, the solution also simplifies a large number of unusual configurations, and makes the technical requirements of pipeline editing continuously subside, as shown in fig. 7, a complete CI & CD additional test pipeline can clearly see the whole context on a simple page, and the detailed configuration can be seen by clicking each step. The detailed configuration is also very simple, and is the configuration of git step as shown in fig. 8.
Secondly, a background implementation scheme capable of being developed secondarily:
from the overall solution, it can be seen that the CI & CD pipeline solution has a core in the background implementation, namely the pipeline scheduling center. And executing each plug-in project according to the steps and the configuration after the request reaches the pipeline scheduling center.
The plug-in project is actually an individual project, and a user can write a new plug-in project by himself to realize the personalized plug-in, and the plug-in project can be used in a page after being integrated into a pipeline project. The shell code cannot be seen on the page, the complex and tedious steps are packaged in the code after the package of the plug-in project is actually carried out, and the code is provided for the user to operate and is the most easily understood part.
Thirdly, a plug-in project scheduling implementation scheme:
each step of front-end configuration is converted into data in json format, the data is sent to a production line dispatching center from a front-end project (namely a page project), the data is sent to a plug-in project through the production line dispatching center, and the plug-in project completes the execution of the plug-in by analyzing the data.
The configuration information of each plug-in can be configured on a front-end page, the full path name of an implementation class of a certain plug-in a plug-in project needs to be configured into a corresponding plug-in plug-in management, the so-called plug-in implementation class is a java class, the method in the class realizes the operation of the certain plug-in by calling API (application programming interface) by java, for example, the implementation class of git, and the class realizes the operation of pulling/cloning codes from a git server, so that a pipeline scheduling center can create an object of the class according to the full path name of the class through a reflection mechanism of java, each implementation class of the plug-in inherits the same class, and the pipeline scheduling center can realize different plug-ins by calling the same method through an upward modeling mechanism of java. As shown in fig. 9, the engineering structure of the whole pipeline engineering is shown.
Fourthly, a convenient log checking process:
and performing personalized processing on the log after the execution of the pipeline is finished. Compared with the existing platform or the existing assembly line function in the open source project in the market, the log displayed after the execution is finished is different, unnecessary contents in the log are eliminated, and the most ideal things for a user to see are reserved.
The method comprises the steps of configuring a front end, calling one by a background pipeline scheduling center in sequence, returning a step log object after each calling is finished, taking out log information in the step log object by the pipeline scheduling center and storing the log information in a database to form a database record, wherein a field in the step log record is associated with a pipeline ID, so that when the log needs to be checked, all the step logs of a pipeline can be taken out through the pipeline ID, and finally, a main log of the pipeline is returned, and the log can be associated with each step log.
The log can be viewed through a log button after each record of the pipeline list page, and can also be viewed through a log button of the editing page. The pipeline can automatically pop up a log page after the execution is finished. The content of the log display takes the log after the execution of the docker plug-in as an example, and as shown in fig. 10, the log displays the address of the mirror repository and the access mode.
EXAMPLE III
The embodiment provides a pipeline construction method based on parameter configuration, which comprises the following specific implementation processes:
step 1:
writing plug-in engineering, generally, a plug-in engineering is only a simple java engineering, and the engineering may include one or more classes, but at least one class needs to inherit a plug-in engineering parent class, where the name of the parent class is MyTask, where two abstract methods need to be implemented, which are a run method and a checkParam method, respectively, where the run method is used to be called by a pipeline scheduling center and return a step log, and the checkParam is used to check whether parameters introduced by the pipeline scheduling center are correct and return yes or no, for example, in this embodiment, a background plug-in engineering of a gtiab plug-in is written, the plug-in engineering depends on a jar package of a jti, and an API of the git is called in java code to implement an operation of pulling code from a gtiab repository.
Step 2:
after the Git plug-in project is integrated into the pipeline project, relevant parameters and attribute configuration are needed to be carried out on the page for use. The detailed configuration is shown in fig. 11, taking git as an example. The parameter configuration here is to configure which parameters of a plug-in, and the parameter configuration of step 4 is to configure the specific parameter values of a plug-in. For example, the git insert has three parameters: the code base address, the access certificate and the branch are added to a plug-in management page, a plug-in is named git, and relevant information of three parameters of the plug-in is filled in parameter configuration, wherein the relevant information comprises parameter names, parameter codes, pre-values, input types and the like. And the parameter configuration of the step 4 means that if the user selects the git plug-in, the user needs to fill in three parameters of the address of the code base, the access certificate and the branch in the pipeline.
And step 3:
the flow and basic information can be edited in the pipeline editing page: pipeline name, item to which the pipeline belongs, default, triggering mode and remark. The editing of the process fills in the steps of Jenkins in a form, and the steps are simplified into the step editing of legendization. Take the first step, pulling the code as an example. Clicking on the page "add step", pop up step edits the page, as shown in FIG. 12.
And 4, step 4:
clicking the gitlab plug-in icon, popping up a plug-in parameter configuration page, and selecting/inputting the parameters, as shown in fig. 13.
And 5:
clicking the configuration of the 'confirmed' storage parameters on the page, and clicking the step of confirming the storage, thus completing the addition of one pipeline step. Repeating the above process, selecting the required plug-in (currently providing plug-ins such as git, maven, docker, k8s, jmeter, sonarqube, etc.) can edit a pipeline for CI & CD.
Each step belongs to a stage, a plurality of steps can be added to each stage, the order of the steps of the pipeline running can not be influenced by the stages, but the steps can be classified into the stages, so that the pipeline with the steps is more orderly on a page, and the stages can be added between the stages, so that the pipeline is more readable, for example, as shown in fig. 14, a pipeline has five steps, if the steps are all placed in one stage or the concept of the stages does not exist, the pipeline is long and seems to go all the way to the head, the structure can not be seen, but the steps with similar functions or the steps with related functions can be classified into the same stage through the division of the stages, so that the structure and the process of the pipeline are clearer. At present, a complete CI & CD pipeline with test function is shown in FIG. 14.
Step 6:
after the pipeline editing is finished, clicking 'save' on the page to save the pipeline. Clicking "run" will start running the pipeline. After waiting for the completion of the operation, the log page will automatically pop up, as shown in fig. 15.
And 7:
clicking on the "log details" on the page can view the complete pipeline log record, as shown in FIG. 16.
It should be noted that the plug-in is abstract, for example, git is a plug-in which can pull/clone code, and git can download the installation package from the internet, install it on the computer separately, or integrate it into java code. The plug-in project is specifically a section of java code, the section of java code is used for realizing the plug-in, for example, the git plug-in project writes a section of code by java, and the section of code can realize the operation of pulling/cloning the code.
To sum up, the pipeline construction method based on parameter configuration of the above embodiment can edit a CI & CD pipeline without learning to compile shell scripts, thereby saving learning cost and time for users, reducing the threshold of users, and expanding the user range; because the shell script is removed, namely, the user is allowed to have no knowledge about the server environment, the server is transparent to the user, all personnel in a research and development team can participate in the continuous construction/deployment work, and can be used by non-operation and maintenance personnel, so that better cooperation between development and operation and maintenance is realized; the plug-in project is zero-coupled with other codes of the whole platform, and users can develop the plug-in project by themselves to finish the work they want to do; and the contents displayed in the log are filtered and processed, so that the contents of the log in the hybrid system become concise and direct, and users can directly see the contents most concerned by the users, thus being worthy of popularization and application.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. A pipeline construction method based on parameter configuration is characterized by comprising the following steps:
s1: writing plug-in project
Compiling a plug-in project, and integrating the plug-in project into a pipeline project;
s2: configuration plug-in engineering
After the plug-in project is integrated into the assembly line project, configuring relevant parameters and attributes of the plug-in project;
s3: editing process
Editing the flow and the basic information;
s4: selection plug-in
Selecting a corresponding plug-in icon, and performing parameter configuration on the plug-in;
s5: construction of a Single step
Saving the parameter configuration of the plug-in the step S4, and saving the parameter configuration;
s6: all steps of construction
And repeating the steps S1-S5, selecting all the required plug-ins, finishing all the plug-ins selection, and finishing the pipeline construction after all the step configuration is stored.
2. The pipeline construction method based on parameter configuration according to claim 1, wherein: the operations of the steps S2-S6 are all performed on a visual page.
3. The pipeline construction method based on parameter configuration according to claim 1, wherein: in step S2, the attributes of the plug-in project include a plug-in name, a plug-in path, a plug-in implementation class, a plug-in type, a plug-in version number, and a plug-in icon, and the related parameters of the plug-in project include a parameter name, an input type, a pre-value, a default value, a parameter code, and a parameter description.
4. The pipeline construction method based on parameter configuration according to claim 1, wherein: in step S3, the basic information includes the pipeline name, the item to which the pipeline belongs, whether the pipeline is default, the trigger mode, and the remark.
5. The pipeline construction method based on parameter configuration according to claim 1, wherein: in step S3, the editing of the flow is completed by the illustrated editing mode.
6. The pipeline construction method based on parameter configuration according to claim 1, wherein: in step S4, the parameter configuration of the plug-in is performed by selecting or inputting parameters.
7. The pipeline construction method based on parameter configuration according to claim 1, wherein: after the assembly line is constructed, whether the assembly line is operated or not is selected according to requirements, and after the operation is finished, the log can be checked.
8. The pipeline construction method based on parameter configuration according to claim 7, wherein: each step in the assembly line is called one by the background assembly line scheduling center in sequence during running, after each calling is finished, the plug-in project returns a step log object, the assembly line scheduling center takes out and stores the log information in the step log object, and finally returns a main log of the assembly line, and the main log is associated with each step log.
9. The pipeline construction method based on parameter configuration according to claim 1, wherein: in step S6, each configured step is converted into json-format data, and the json-format data is sent to the pipeline scheduling center, and the pipeline scheduling center sends the data to each plug-in project, and the plug-in project completes the execution of the plug-ins by analyzing the data.
10. A pipeline construction system based on parameter configuration, wherein the pipeline construction work is performed by the construction method according to any one of claims 1 to 9, and the method comprises the following steps:
the plug-in project compiling module is used for compiling plug-in projects and integrating the plug-in projects into the pipeline projects;
the plug-in project configuration module is used for configuring relevant parameters and attributes of the plug-in project after the plug-in project is integrated into the assembly line project;
the flow editing module is used for editing the flow and the basic information;
the plug-in project selection module is used for selecting a corresponding plug-in icon and performing parameter configuration on the plug-in;
the single-step construction module is used for storing the parameter configuration of the selected plug-in and storing the step;
the all-step construction module is used for selecting all required plug-ins, finishing all the selection of the plug-ins and finishing the assembly line construction after all the step configurations are stored;
the control processing module is used for controlling each module and executing related instructions;
the plug-in project compiling module, the plug-in project configuration module, the flow editing module, the plug-in project selecting module, the single-step building module and the all-step building module are connected with the control processing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010317612.9A CN111506304A (en) | 2020-04-21 | 2020-04-21 | Assembly line construction method and system based on parameter configuration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010317612.9A CN111506304A (en) | 2020-04-21 | 2020-04-21 | Assembly line construction method and system based on parameter configuration |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111506304A true CN111506304A (en) | 2020-08-07 |
Family
ID=71876272
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010317612.9A Pending CN111506304A (en) | 2020-04-21 | 2020-04-21 | Assembly line construction method and system based on parameter configuration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111506304A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112114813A (en) * | 2020-09-17 | 2020-12-22 | 四川长虹电器股份有限公司 | Automatic generation method of yaml script based on production line |
| CN112181366A (en) * | 2020-09-28 | 2021-01-05 | 科大国创云网科技有限公司 | Mobile application development framework based on cross-platform interaction |
| CN112328229A (en) * | 2020-11-06 | 2021-02-05 | 无锡江南计算技术研究所 | Method for quickly creating Jenkins assembly line |
| CN112882938A (en) * | 2021-02-25 | 2021-06-01 | 重庆紫光华山智安科技有限公司 | Scene data testing method, system, electronic device and medium |
| CN114253630A (en) * | 2021-12-23 | 2022-03-29 | 上海新炬网络信息技术股份有限公司 | Method for realizing log storage by modifying Form change information based on Java section |
| TWI774469B (en) * | 2021-07-12 | 2022-08-11 | 瑞昱半導體股份有限公司 | Management system for program compilation and method for operating the system |
| CN115421847A (en) * | 2022-11-03 | 2022-12-02 | 江苏博云科技股份有限公司 | Management method and equipment for research, development, operation and maintenance platform and CICD (common information carrier) assembly line supporting multiple engines |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090089128A1 (en) * | 2007-09-27 | 2009-04-02 | Microsoft Corporation | Service-oriented pipeline based architecture |
| US20180046455A1 (en) * | 2016-08-10 | 2018-02-15 | Fmr Llc | System and Method of Configuring A Data Store For Tracking And Auditing Real-Time Events Across Different Software Development Tools In Agile Development Environments |
| US20180364985A1 (en) * | 2017-06-14 | 2018-12-20 | International Business Machines Corporation | Congnitive development of devops pipeline |
| CN110262806A (en) * | 2019-06-20 | 2019-09-20 | 杭州泰然鲸数云计算有限公司 | A kind of DevOps system for supporting automation services layout |
| US20190294531A1 (en) * | 2018-03-26 | 2019-09-26 | Ca, Inc. | Automated software deployment and testing based on code modification and test failure correlation |
| US10585656B1 (en) * | 2017-12-18 | 2020-03-10 | Cerner Innovation, Inc. | Event manager for software deployment |
-
2020
- 2020-04-21 CN CN202010317612.9A patent/CN111506304A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090089128A1 (en) * | 2007-09-27 | 2009-04-02 | Microsoft Corporation | Service-oriented pipeline based architecture |
| US20180046455A1 (en) * | 2016-08-10 | 2018-02-15 | Fmr Llc | System and Method of Configuring A Data Store For Tracking And Auditing Real-Time Events Across Different Software Development Tools In Agile Development Environments |
| US20180364985A1 (en) * | 2017-06-14 | 2018-12-20 | International Business Machines Corporation | Congnitive development of devops pipeline |
| US10585656B1 (en) * | 2017-12-18 | 2020-03-10 | Cerner Innovation, Inc. | Event manager for software deployment |
| US20190294531A1 (en) * | 2018-03-26 | 2019-09-26 | Ca, Inc. | Automated software deployment and testing based on code modification and test failure correlation |
| CN110262806A (en) * | 2019-06-20 | 2019-09-20 | 杭州泰然鲸数云计算有限公司 | A kind of DevOps system for supporting automation services layout |
Non-Patent Citations (1)
| Title |
|---|
| 丘晖: "基于容器的持续集成和部署方法研究", 《广东通信技术》 * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112114813A (en) * | 2020-09-17 | 2020-12-22 | 四川长虹电器股份有限公司 | Automatic generation method of yaml script based on production line |
| CN112181366A (en) * | 2020-09-28 | 2021-01-05 | 科大国创云网科技有限公司 | Mobile application development framework based on cross-platform interaction |
| CN112181366B (en) * | 2020-09-28 | 2023-01-24 | 科大国创云网科技有限公司 | Mobile application development framework based on cross-platform interaction |
| CN112328229A (en) * | 2020-11-06 | 2021-02-05 | 无锡江南计算技术研究所 | Method for quickly creating Jenkins assembly line |
| CN112882938A (en) * | 2021-02-25 | 2021-06-01 | 重庆紫光华山智安科技有限公司 | Scene data testing method, system, electronic device and medium |
| CN112882938B (en) * | 2021-02-25 | 2023-03-14 | 重庆紫光华山智安科技有限公司 | Scene data testing method, system, electronic equipment and medium |
| TWI774469B (en) * | 2021-07-12 | 2022-08-11 | 瑞昱半導體股份有限公司 | Management system for program compilation and method for operating the system |
| CN114253630A (en) * | 2021-12-23 | 2022-03-29 | 上海新炬网络信息技术股份有限公司 | Method for realizing log storage by modifying Form change information based on Java section |
| CN114253630B (en) * | 2021-12-23 | 2023-07-25 | 上海新炬网络信息技术股份有限公司 | Method for realizing log storage based on Java section modification Form change information |
| CN115421847A (en) * | 2022-11-03 | 2022-12-02 | 江苏博云科技股份有限公司 | Management method and equipment for research, development, operation and maintenance platform and CICD (common information carrier) assembly line supporting multiple engines |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111506304A (en) | Assembly line construction method and system based on parameter configuration | |
| US7448024B2 (en) | System and method for software application development in a portal environment | |
| CN101777004B (en) | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment | |
| US8296665B2 (en) | Developing and executing applications with configurable patterns | |
| US7913231B2 (en) | Testing pattern-based applications | |
| US9916134B2 (en) | Methods and systems for accessing distributed computing components through the internet | |
| US7761865B2 (en) | Upgrading pattern configurations | |
| US7953767B2 (en) | Developing applications using configurable patterns | |
| US8347214B2 (en) | Automated interface-specification generation for enterprise architectures | |
| US9286037B2 (en) | Platform for distributed applications | |
| US20040205691A1 (en) | Interactive agent for a topological multi-tier business application composer | |
| US9442699B2 (en) | Model elements in software tools as automatons in a software customization system and method | |
| US20100153150A1 (en) | Software for business adaptation catalog modeling | |
| EP2378415A1 (en) | Service integration modeling and execution framework | |
| US20160170719A1 (en) | Software database system and process of building and operating the same | |
| JP2015504186A (en) | System and method for mobile application development | |
| US20110185294A1 (en) | Pattern-based user interfaces | |
| US20050267913A1 (en) | Detecting and handling changes to back-end systems | |
| US20120060141A1 (en) | Integrated environment for software design and implementation | |
| US20060047723A1 (en) | Custom database system and method of building the same | |
| JP2006512670A (en) | Method and apparatus for an integrated process modeler | |
| CN115480810A (en) | Low-code platform based on cloud protogenesis | |
| WO2023004806A1 (en) | Device deployment method for ai model, system, and storage medium | |
| EP1577762A2 (en) | Address support for resources in common-language runtime languages | |
| US20100011018A1 (en) | Custom database system and method of building the same |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200807 |
|
| RJ01 | Rejection of invention patent application after publication |