Method and System for Constructing a Pipeline Package

Abstract

The present invention provides a method and system for constructing a pipeline package. By solidifying a pre-constructed pipeline, a first definition template is obtained; the technology stack and application information required for the system to be generated are acquired, and the pipeline template for the system to be generated is determined based on the technology stack and application information; a second definition template is obtained from the first definition template based on the pipeline template of the system to be generated; a pipeline package corresponding to the system to be generated is generated based on the second definition template, the technology stack, and the application information, and is published. In this solution, a first definition template for establishing the standard for constructing a pipeline package is established in advance. According to the information required for the system for which the pipeline package needs to be constructed, a second definition template that meets the information requirements of the system is obtained from the first definition template, and a pipeline package corresponding to the system is generated according to the second definition template, thereby realizing automatic configuration, unifying the pipeline package standard, and facilitating management.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular, to a method and system for constructing a pipeline package. Background Art

[0002] In the process of software development, developers perform tasks such as development, testing, environment configuration, data script writing, and bug fixing in TFS based on specific requirements. After a series of builds, integrations, and quality checks, mature various artifacts are delivered and deployed to the production environment for production release.

[0003] Due to differences in the technology stacks, branch models, dependent environments, quality inspection tools, deployment methods, etc. of each software product, in order to achieve the automated flow of each link such as continuous integration, continuous testing, and continuous delivery, each system needs to configure multiple pipelines that meet its own needs according to its own situation.

[0004] However, for systems with many similar situations, the current pipeline configuration method cannot achieve the goal of sharing a pipeline package configuration for multiple similar systems at one time. Moreover, when each system configures the pipeline package separately, there may be significant differences in the pipeline trigger timing, quality inspection content, and quality gate setting standards, and the goal of unified management requirements for the R & D processes of each system cannot be achieved.

[0005] It can be seen that the existing pipeline configuration method is a manual method, which requires frequent pipeline configuration operations, and the pipeline package standards for similar systems are not unified, which is not conducive to management. Summary of the Invention

[0006] In view of this, embodiments of the present invention provide a method and system for constructing a pipeline package to achieve the purposes of automated configuration, unified pipeline package standards, and convenient management.

[0007] To achieve the above object, embodiments of the present invention provide the following technical solutions:

[0008] A first aspect of an embodiment of the present invention discloses a method for constructing a pipeline package, which is applied to Team Foundation Server (TFS). The method includes:

[0009] Solidify a pre-constructed pipeline to obtain a first definition template;

[0010] Obtain the technology stack and application information required for the system to be generated, and determine the pipeline template of the system to be generated based on the technology stack and application information;

[0011] Obtain a second definition template from the first definition template based on the pipeline template of the system to be generated;

[0012] Generate a pipeline package corresponding to the to-be-generated system based on the second definition template, the technology stack, and the application information, and publish it.

[0013] Optionally, solidifying the pre-built pipeline to obtain a first definition template includes:

[0014] Obtain the definition type of the pipeline, where the definition type at least includes trigger timing, branch model type, technology stack type, and application scenario;

[0015] Based on the definition type, obtain pipeline templates for different definition types;

[0016] Solidify the pipeline templates for different definition types to obtain corresponding first definition templates.

[0017] Optionally, the technology stack and application information at least include branch model name, development language, and deployment method. Obtaining the technology stack and application information required for the to-be-generated system and determining the pipeline template for the to-be-generated system based on the technology stack and application information includes:

[0018] Obtain the branch model name, development language, and deployment method required for the to-be-generated system;

[0019] Determine the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template for the to-be-generated system according to the branch model name, the development language, and the deployment method.

[0020] Optionally, obtaining the second definition template from the first definition template based on the pipeline template of the to-be-generated system includes:

[0021] According to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template of the to-be-generated system, search for and obtain the second definition templates corresponding to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template in the first definition template.

[0022] Optionally, generating a pipeline package corresponding to the to-be-generated system based on the second definition template, the technology stack, and the application information, and publishing it includes:

[0023] Generate a pipeline package corresponding to the to-be-generated system based on the second definition templates respectively corresponding to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template, as well as the technology stack and the application information, and publish it.

[0024] A second aspect of an embodiment of the present invention discloses a system for building a pipeline package, which is applied to a team foundation server TFS. The system includes:

[0025] A curing module, used for curing the pre-built pipeline to obtain a first definition template;

[0026] A determination module, used to obtain the technology stack and application information required by the system to be generated, and determine the pipeline template of the system to be generated based on the technology stack and application information;

[0027] An acquisition module, configured to acquire a second definition template from the first definition template based on the pipeline template of the system to be generated;

[0028] A generation module is used to generate and publish a pipeline package corresponding to the system to be generated based on the second definition template, the technology stack and the application information.

[0029] Optionally, the curing module includes:

[0030] An acquisition unit, used to acquire a definition type of the pipeline, wherein the definition type at least includes a triggering timing, a branch model type, a technology stack type, and an application scenario;

[0031] An obtaining unit, used for obtaining pipeline templates of different definition types based on the definition type;

[0032] The solidification unit is used to solidify the pipeline templates of different definition types to obtain corresponding first definition templates.

[0033] Optionally, the technology stack and application information include at least a branch model name, a development language, and a deployment method, and the determination module includes:

[0034] An acquisition unit is used to obtain the branch model name, development language and deployment method required by the system to be generated;

[0035] A determination unit is used to determine the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template and application scenario pipeline template of the system to be generated according to the branch model name, the development language and the deployment method.

[0036] Optionally, the acquisition module is specifically used for:

[0037] According to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template of the to-be-generated system, search for the second definition templates corresponding to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template in the first definition template, and obtain them.

[0038] Optionally, the generating module is specifically configured to:

[0039] Based on the second definition templates corresponding to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template respectively, and the technology stack and the application information, generate a pipeline package corresponding to the to-be-generated system, and publish it.

[0040] Based on the method and system for constructing a pipeline package provided in the above embodiments of the present invention, the method includes: solidifying a pre-constructed pipeline to obtain a first definition template; obtaining the technology stack and application information required by the to-be-generated system, and determining the pipeline template of the to-be-generated system based on the technology stack and application information; obtaining a second definition template from the first definition template based on the pipeline template of the to-be-generated system; generating a pipeline package corresponding to the to-be-generated system based on the second definition template, the technology stack, and the application information, and publishing it. In this solution, a first definition template for establishing the standard for constructing a pipeline package is established in advance, a second definition template that conforms to the information required by the system is obtained from the first definition template according to the information required by the system for which the pipeline package needs to be constructed, and a pipeline package corresponding to the system is generated according to the second definition template, thereby realizing automatic configuration, unifying the pipeline package standard, and facilitating management. Description of the Drawings

[0041] 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 required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0042] Figure 1 It is a schematic flowchart of a method for constructing a pipeline package provided in an embodiment of the present invention;

[0043] Figure 2 It is a schematic flowchart of a method for obtaining a first definition template provided in an embodiment of the present invention;

[0044] Figure 3A schematic flowchart of a process for determining a pipeline template of a system to be generated provided by an embodiment of the present invention;

[0045] Figure 4 A schematic structural diagram of a system for constructing a pipeline package provided by an embodiment of the present invention. Detailed implementation manners

[0046] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0047] In this application, the terms "including", "comprising" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0048] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments described here can be implemented in an order other than that illustrated or described here.

[0049] For the convenience of understanding the technical solutions of the present invention, the technical terms appearing in the present invention are explained as follows:

[0050] Pipeline: It is the core mode of continuous integration and continuous delivery, a visual presentation method of the software delivery process, showing the entire process from code submission, construction, deployment, testing to release, and continuously executing related tasks in sequence according to a certain route and task links.

[0051] Pipeline package: Combining multiple pipelines in each stage and each scenario to finally realize the complete end-to-end continuous delivery process of software products, that is, including continuous integration, continuous testing, continuous delivery and deployment, and also a combination of multiple pipelines generated according to different delivered products.

[0052] Continuous Integration: A software practice where integration is performed at least once a day during the software development process and verified through automated builds and tests to detect integration errors as early as possible.

[0053] As can be seen from the background art, the existing pipeline configuration method is a manual method, which requires frequent pipeline configuration operations, and the pipeline package standards for similar systems are not unified, which is not conducive to management.

[0054] Therefore, the embodiments of the present invention provide a method and system for constructing a pipeline package. In this solution, a first definition template for constructing a pipeline package standard is established in advance, a second definition template that meets the information required by the system for which the pipeline package needs to be constructed is obtained from the first definition template according to the information required by the system, and a pipeline package corresponding to the system is generated according to the second definition template, thereby realizing automated configuration, unified pipeline package standards, and facilitating management. This will be described in detail through the following embodiments.

[0055] As Figure 1 shown, it is a schematic flowchart of a method for constructing a pipeline package provided by an embodiment of the present invention. This method for constructing a pipeline package is applied to TFS (Team Foundation Server).

[0056] It should be noted that TFS is a professional collaborative software development tool that can be integrated with existing IDEs (Integrated Development Environments) or editors.

[0057] This method mainly includes the following steps:

[0058] Step S101: Solidify the pre-constructed pipeline to obtain a first definition template.

[0059] In the specific implementation of step S101, a pipeline is constructed, the constructed pipeline is obtained, and the obtained pipeline is solidified to obtain a first definition template.

[0060] Optionally, the way to construct a pipeline can be: create a pipeline based on different branches, and specifically configure it through the build definition function of TFS. Among them, the build definition contains at least information such as trigger timing, trigger method, quality inspection content, invoking the quality inspection tool plugin, and quality gate setting.

[0061] It should be noted that the method for constructing a pipeline is not limited to the method disclosed above in the present invention, and can also be set by technicians based on technical requirements.

[0062] Optionally, the process of executing step S101 to solidify the pre-constructed pipeline to obtain a first definition template is as Figure 2As shown in the figure, it is a schematic flowchart of a process for obtaining a first definition template provided by an embodiment of the present invention, mainly including the following steps:

[0063] Step S201: Obtain the definition type of the pipeline.

[0064] In step S201, the definition type at least includes trigger timing, branch model type, technology stack type, and application scenario.

[0065] In the specific process of implementing step S201, obtain the definition type of the constructed pipeline, specifically: obtain the trigger timing, branch model type, technology stack type, and application scenario of the constructed pipeline.

[0066] Step S202: Based on the definition type, obtain pipeline templates of different definition types.

[0067] In the specific process of implementing step S202, based on definition types such as the trigger timing, branch model type, technology stack type, and application scenario of the pipeline, obtain pipeline templates corresponding to the definition types of trigger timing, branch model type, technology stack type, and application scenario, respectively, namely: trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template.

[0068] Step S203: Solidify the pipeline templates of different definition types to obtain the corresponding first definition template.

[0069] In the specific process of implementing step S203, solidify the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template respectively to obtain the corresponding first definition template.

[0070] Step S102: Obtain the technology stack and application information required for the system to be generated, and determine the pipeline template of the system to be generated based on the technology stack and application information.

[0071] In step S102, the technology stack and application information at least include the branch model name, development language, and deployment method, but are not limited thereto.

[0072] In the specific process of implementing step S102, obtain the system that needs to build a pipeline package, that is, the technology stack and application information required for the system to be generated, and determine the pipeline template of the system to be generated according to the obtained technology stack and application information required for the system to be generated.

[0073] Optionally, when the technology stack and application information at least include the branch model name, development language, and deployment method, perform step S102 to obtain the technology stack and application information required for the system to be generated, and determine the pipeline template of the system to be generated based on the technology stack and application information. As Figure 3 shown, it is a schematic flowchart of a process for determining the pipeline template of a system to be generated provided by an embodiment of the present invention, mainly including the following steps:

[0074] Step S301: Obtain the branch model name, development language, and deployment method required for the system to be generated.

[0075] In the specific implementation of step S301, obtain the system for which the pipeline package needs to be constructed, that is, the branch model name, development language, and deployment method required for the system to be generated.

[0076] Step S302: Determine the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated according to the branch model name, development language, and deployment method.

[0077] In the specific implementation of step S302, determine the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated according to the obtained branch model name, development language, and deployment method required for the system to be generated.

[0078] Step S103: Obtain the second definition template from the first definition template based on the pipeline template of the system to be generated.

[0079] In the specific implementation of step S103, based on the already determined pipeline template of the system to be generated, obtain the second definition template from the first definition template.

[0080] Preferably, according to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated, search for and obtain the second definition templates corresponding to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template in the first definition template respectively.

[0081] Step S104: Generate and publish the pipeline package corresponding to the system to be generated based on the second definition template, technology stack, and application information.

[0082] In step S104, the pipeline package includes, but is not limited to, the build, development, and test environment deployment pipeline package, the production deployment pipeline package, the self-developed component pipeline package, and the data change pipeline package.

[0083] In the process of specifically implementing step S104, according to the obtained second definition template, technology stack, and application information, a pipeline package corresponding to the system to be generated is generated, and the pipeline package of the system to be generated is published.

[0084] It should be noted that the generated pipeline package can be published by using the build definition and publishing functions of TFS.

[0085] Preferably, based on the second definition template corresponding to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template respectively, as well as the technology stack and application information, a pipeline package corresponding to the system to be generated is generated and published.

[0086] Based on a method for constructing a pipeline package provided by an embodiment of the present invention, a first definition template is obtained by solidifying a pre-constructed pipeline; the technology stack and application information required for the system to be generated are obtained, and the pipeline template of the system to be generated is determined based on the technology stack and application information; a second definition template is obtained from the first definition template based on the pipeline template of the system to be generated; a pipeline package corresponding to the system to be generated is generated based on the second definition template, the technology stack, and the application information, and is published. In this solution, a first definition template for establishing the standard for constructing a pipeline package is established in advance, a second definition template that conforms to the information required by the system is obtained from the first definition template according to the information required by the system for which the pipeline package needs to be constructed, and a pipeline package corresponding to the system is generated according to the second definition template, thereby realizing automatic configuration, unifying the pipeline package standard, and facilitating management.

[0087] To better understand the method for constructing a pipeline package provided by the above embodiment of the present invention, an example is given below for detailed description.

[0088] Taking the construction of the "production deployment pipeline package" as an example, it is as follows:

[0089] Construct a pipeline, obtain the constructed pipeline, and solidify the obtained pipeline to obtain a first definition template.

[0090] Obtain the technology stack and application information required for the system to be generated for constructing the "production deployment pipeline package", and determine the pipeline template of the system to be generated according to the obtained technology stack and application information required for the system to be generated, that is, determine the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated according to the obtained branch model name, development language, and deployment method required for the system to be generated.

[0091] According to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated, search for the second definition templates corresponding to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template in the first definition template, and obtain them.

[0092] Based on the second definition templates corresponding to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template respectively, as well as the technology stack and application information, generate a pipeline package corresponding to the system to be generated, that is, generate the "production deployment pipeline package" corresponding to the system to be generated, and publish the "production deployment pipeline package".

[0093] It should be noted that the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated are the specific pipeline template data information of the system to be generated, while the second definition template is the standard template corresponding to the above pipeline template data information. Subsequently, the corresponding pipeline template data information will be added to the second definition template to finally generate the pipeline template of the system to be generated.

[0094] Based on a method for constructing a pipeline package provided by an embodiment of the present invention, by solidifying a pre-constructed pipeline, a first definition template is obtained; the technology stack and application information required for the system to be generated are obtained, and the pipeline template of the system to be generated is determined based on the technology stack and application information; the second definition template is obtained from the first definition template based on the pipeline template of the system to be generated; a pipeline package corresponding to the system to be generated is generated based on the second definition template, the technology stack, and the application information, and is published. In this solution, a first definition template for constructing a pipeline package standard is established in advance, a second definition template that conforms to the information required by the system for which the pipeline package needs to be constructed is obtained from the first definition template according to the information required by the system, and a pipeline package corresponding to the system is generated according to the second definition template, thereby realizing automatic configuration, unifying the pipeline package standard, and facilitating management.

[0095] Corresponding to a method for constructing a pipeline package shown in an embodiment of the present invention above, an embodiment of the present invention also correspondingly provides a system for constructing a pipeline package. This system for constructing a pipeline package is applied to a Team Foundation Server (TFS), such as Figure 4 As shown, this system for constructing a pipeline package includes: a solidification module 41, a determination module 42, an acquisition module 43, and a generation module 44.

[0096] The solidification module 41 is used to solidify a pre-constructed pipeline to obtain a first definition template.

[0097] A determination module 42, configured to obtain the technology stack and application information required for the system to be generated, and determine a pipeline template for the system to be generated based on the technology stack and application information.

[0098] An acquisition module 43, configured to obtain a second definition template from the first definition template based on the pipeline template of the system to be generated.

[0099] A generation module 44, configured to generate a pipeline package corresponding to the system to be generated based on the second definition template, the technology stack, and the application information, and publish it.

[0100] It should be noted that the specific principles and execution processes of each module or unit in the system for constructing a pipeline package disclosed in the above embodiments of the present invention are the same as those of the method for constructing a pipeline package in the above embodiments of the present invention. For corresponding parts, reference can be made to the method for constructing a pipeline package disclosed in the above embodiments of the present invention, and details will not be elaborated here.

[0101] Based on a system for constructing a pipeline package provided by an embodiment of the present invention, a first definition template is obtained by solidifying a pre-constructed pipeline; the technology stack and application information required for the system to be generated are obtained, and a pipeline template for the system to be generated is determined based on the technology stack and application information; a second definition template is obtained from the first definition template based on the pipeline template of the system to be generated; a pipeline package corresponding to the system to be generated is generated based on the second definition template, the technology stack, and the application information, and published. In this solution, a first definition template for constructing a pipeline package standard is established in advance, a second definition template that meets the information requirements of the system is obtained from the first definition template according to the information required for the system for which a pipeline package needs to be constructed, and a pipeline package corresponding to the system is generated according to the second definition template, thereby realizing automatic configuration, unifying the pipeline package standard, and facilitating management.

[0102] Optionally, based on the above Figure 4 The shown solidification module 41 further includes: an acquisition unit, a obtaining unit, and a solidification unit.

[0103] The acquisition unit is configured to acquire the definition types of the pipeline, and the definition types at least include trigger timing, branch model type, technology stack type, and application scenario.

[0104] The obtaining unit is configured to obtain pipeline templates of different definition types based on the definition types.

[0105] The solidification unit is configured to solidify the pipeline templates of different definition types to obtain corresponding first definition templates.

[0106] A system for constructing a pipeline package provided by an embodiment of the present invention solidifies pipeline templates of different definition types to obtain corresponding first definition templates, thereby providing template data for subsequent generation of pipeline packages, and realizing automated configuration, unifying pipeline package standards, and facilitating management.

[0107] Optionally, based on the above Figure 4 The acquisition and determination module 42 shown, the technology stack and application information at least include a branch model name, a development language, and a deployment method, and the determination module 42 includes:

[0108] An acquisition unit for acquiring the branch model name, development language, and deployment method required for the system to be generated.

[0109] A determination unit for determining a trigger timing pipeline template, a branch model type pipeline template, a technology stack type pipeline template, and an application scenario pipeline template of the system to be generated according to the branch model name, development language, and deployment method.

[0110] A system for constructing a pipeline package provided by an embodiment of the present invention determines the pipeline template of the system to be generated according to the branch model name, development language, and deployment method required for the system to be generated, so as to accurately generate a pipeline package suitable for the system to be generated, and realize automated configuration, unify pipeline package standards, and facilitate management.

[0111] Optionally, based on the above Figure 4 The acquisition module 43 shown, the acquisition module 43 specifically is used for:

[0112] According to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template of the system to be generated, search for the second definition templates corresponding to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template in the first definition template, and acquire them.

[0113] A system for constructing a pipeline package provided by an embodiment of the present invention searches for and acquires the second definition template corresponding to the pipeline template of the system to be generated in the first definition template through the determined pipeline template of the system to be generated, so as to accurately generate a pipeline package suitable for the system to be generated, and realize automated configuration, unify pipeline package standards, and facilitate management.

[0114] Optionally, based on the above Figure 4 The generation module 44 shown, the generation module 44 specifically is used for:

[0115] Generate a pipeline package corresponding to the system to be generated based on the second definition templates corresponding to the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template, as well as the technology stack and application information, and publish it.

[0116] Based on a system for constructing a pipeline package provided by an embodiment of the present invention, by generating a pipeline package corresponding to the system to be generated according to the second definition template, technology stack, and application information, automated configuration, unified pipeline package standards, and convenient management are achieved.

[0117] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for a system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative labor.

[0118] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0119] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be obvious to those skilled in the art. The general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but will be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for constructing a pipeline package, characterized in that, Applied to Team Foundation Server (TFS), the method includes: Solidify a pre-built pipeline to obtain a first definition template, which includes: obtaining the definition types of the pipeline, where the definition types at least include trigger timing, branch model type, technology stack type, and application scenario; based on the definition types, obtain pipeline templates for different definition types; solidify the pipeline templates for different definition types to obtain corresponding first definition templates; Obtain the technology stack and application information required for the system to be generated, and determine the pipeline template for the system to be generated based on the technology stack and application information; Obtain a second definition template from the first definition template based on the pipeline template of the system to be generated; Generate a pipeline package corresponding to the system to be generated based on the second definition template, the technology stack, and the application information, and publish it; Wherein, the technology stack and application information at least include branch model name, development language, and deployment method. The step of obtaining the technology stack and application information required for the system to be generated and determining the pipeline template for the system to be generated based on the technology stack and application information includes: Obtain the branch model name, development language, and deployment method required for the system to be generated; Determine the trigger timing pipeline template, branch model type pipeline template, technology stack type pipeline template, and application scenario pipeline template for the system to be generated according to the branch model name, the development language, and the deployment method.

2. The method according to claim 1, wherein The step of obtaining a second definition template from the first definition template based on the pipeline template of the system to be generated includes: According to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template of the system to be generated, search for and obtain the second definition templates in the first definition template that respectively correspond to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template.

3. The method according to claim 2, wherein The step of generating a pipeline package corresponding to the system to be generated based on the second definition template, the technology stack, and the application information and publishing it includes: Generate a pipeline package corresponding to the system to be generated based on the second definition templates respectively corresponding to the trigger timing pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template, as well as the technology stack and the application information, and publish it.

4. A system for constructing a pipeline package, characterized in that, Applied to Team Foundation Server (TFS), the system includes: A solidification module, configured to solidify a pre-built pipeline to obtain a first definition template; A determination module, configured to obtain the technology stack and application information required for the system to be generated, and determine the pipeline template for the system to be generated based on the technology stack and application information; An acquisition module, configured to obtain a second definition template from the first definition template based on the pipeline template of the system to be generated; A generation module, configured to generate a pipeline package corresponding to the system to be generated based on the second definition template, the technology stack, and the application information, and publish it; Among them, the curing module includes: An obtaining unit, configured to obtain the definition type of the pipeline, where the definition type at least includes a triggering opportunity, a branch model type, a technology stack type, and an application scenario; A obtaining unit, configured to obtain pipeline templates of different definition types based on the definition type; A curing unit, configured to cure the pipeline templates of different definition types to obtain corresponding first definition templates; Among them, the technology stack and application information at least include a branch model name, a development language, and a deployment method, and the determining module includes: An obtaining unit, configured to obtain the branch model name, the development language, and the deployment method required for the system to be generated; A determining unit, configured to determine a triggering opportunity pipeline template, a branch model type pipeline template, a technology stack type pipeline template, and an application scenario pipeline template of the system to be generated according to the branch model name, the development language, and the deployment method.

5. The system according to claim 4, wherein The obtaining module is specifically configured to: According to the triggering opportunity pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template of the system to be generated, search for and obtain second definition templates corresponding to the triggering opportunity pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template in the first definition template.

6. The system according to claim 5, wherein The generating module is specifically configured to: Based on the second definition templates corresponding to the triggering opportunity pipeline template, the branch model type pipeline template, the technology stack type pipeline template, and the application scenario pipeline template, as well as the technology stack and the application information, generate a pipeline package corresponding to the system to be generated and publish it.

Images