CN118642746A - Template generation method, device, electronic device and storage medium - Google Patents

Abstract

The present application proposes a template generation method, device, electronic device and storage medium, wherein the method includes: selecting multiple target components from multiple candidate components of predefined component tasks according to continuous delivery requirements; determining the dependencies between the target components, and the execution order and execution conditions of the component tasks corresponding to the target components; generating a continuous delivery pipeline template according to the target components, dependencies, execution order and execution conditions. The present application defines a standardized creation process for selecting the required target components based on continuous delivery requirements and generating a continuous delivery pipeline template based on the target components, and the process is simple and easy to manage.

Description

Template generation method, device, electronic device and storage medium

Technical Field

The present application relates to the field of computer technology, and in particular to a template generation method, device, electronic device and storage medium.

Background Art

In the software development process, continuous delivery is an important method to improve development efficiency and software quality. However, the traditional continuous delivery pipeline orchestration method has problems such as complex process, difficult management and expansion, and lack of standardization.

Summary of the invention

The present application aims to solve one of the technical problems in the related art at least to some extent.

To this end, the first objective of this application is to propose a template generation method.

The second objective of the present application is to provide a template generating device.

The third objective of the present application is to provide an electronic device.

A fourth objective of the present application is to provide a computer-readable storage medium.

A fifth object of the present application is to provide a computer program product.

To achieve the above-mentioned purpose, the first embodiment of the present application proposes a template generation method, comprising:

According to the continuous delivery requirement, multiple target components are selected from the multiple candidate components of the predefined component tasks;

Determine the dependency relationship between the target components, and the execution order and execution conditions of the component tasks corresponding to the target components;

A continuous delivery pipeline template is generated according to the target component, the dependency, the execution order, and the execution condition.

To achieve the above-mentioned purpose, the second embodiment of the present application proposes a template generation device, including:

A component selection module, used for selecting multiple target components from multiple candidate components of predefined component tasks according to continuous delivery requirements;

A determination module, used to determine the dependency relationship between the target components, and the execution order and execution conditions of the component tasks corresponding to the target components;

A template generation module is used to generate a continuous delivery pipeline template according to the target component, the dependency, the execution order and the execution condition.

To achieve the above-mentioned purpose, the third aspect embodiment of the present application proposes an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement a template generation method as described in the first aspect embodiment of the present application.

To achieve the above-mentioned purpose, the fourth aspect embodiment of the present application proposes a computer-readable storage medium, which stores computer execution instructions. When the computer execution instructions are executed by the processor, they are used to implement a template generation method as described in the first aspect embodiment of the present application.

To achieve the above-mentioned purpose, the fifth aspect of the present application proposes a computer program product, including a computer program, which, when executed by a processor, implements a template generation method as described in the first aspect of the embodiment of the present application.

The technical solution provided by this application brings at least the following beneficial effects:

This application executes a first script that matches the continuous delivery requirements, and selects multiple target components from multiple candidate components that predefine component tasks based on component identifiers in the first script; executes a second script that matches the continuous delivery requirements to determine the dependencies between the target components, as well as the execution order and execution conditions of the component tasks corresponding to the target components; generates a continuous delivery pipeline template based on the target components, dependencies, execution order, and execution conditions. This application defines a standardized creation process for selecting the required target components based on continuous delivery requirements and generating a continuous delivery pipeline template based on the target components. The process is simple, easy to manage, and can improve development efficiency and software quality. In addition, the target components are selected through the first script, and the dependencies, execution order, and execution conditions are determined through the second script, which improves the automation level of the continuous delivery pipeline template creation process.

Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

FIG1 is a schematic diagram of a flow chart of a template generation method provided in an embodiment of the present application;

FIG2 is a schematic diagram of a flow chart of a template generation method provided in another embodiment of the present application;

FIG3A is a schematic diagram of a flow chart of a template generation method provided in another embodiment of the present application;

FIG3B is a schematic diagram of a flow chart of executing a second script provided by an embodiment of the present application;

FIG4 is a schematic diagram of a flow chart of a template generation method provided in another embodiment of the present application;

FIG5 is a schematic diagram of the structure of a template generating device provided in an embodiment of the present application;

FIG6 is a block diagram of an electronic device provided in accordance with an embodiment of the present application.

DETAILED DESCRIPTION

The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

A template generation method, device, electronic device, and storage medium according to an embodiment of the present application are described below with reference to the accompanying drawings.

FIG1 is a schematic flow chart of a template generation method provided in an embodiment of the present application, which method can be applied to electronic devices.

As shown in FIG1 , the template generation method includes the following steps:

Step 101 , according to the continuous delivery requirement, multiple target components are selected from multiple candidate components of predefined component tasks.

Before selecting a target component from the candidate components, it is necessary to predefine the component to obtain multiple candidate components, where each candidate component corresponds to one or more component tasks. It should be noted that if a candidate component corresponds to multiple component tasks, the execution order between the multiple component tasks must also be defined when defining the component.

By way of example and not limitation, component tasks include tasks such as compiling code, unit testing, and deploying applications.

Continuous delivery requirements refer to the continuous delivery requirements of a certain software.

The continuous delivery requirements include the expected links involved in the continuous delivery pipeline and the order in which each link is executed, among which each link corresponds to a different link task, and each link task is implemented by one or more components. As an example but not a limitation, the expected continuous delivery pipeline involves code compilation, unit testing, integration testing, and deployment.

Selecting target components from candidate components means selecting components that can achieve the tasks corresponding to each link in the expected continuous delivery pipeline from candidate components. Different continuous delivery requirements require different target components.

In a possible implementation, when the desired target component is not selected from the candidate components, the candidate components can be directly modified to obtain the desired target component, or the template creator can define the components according to the requirements to obtain the desired target component. Based on this, the present application can support flexible component and task definitions to obtain the desired target component.

Step 102, determining the dependency relationship between target components, and the execution order and execution conditions of component tasks corresponding to each target component.

Determining the dependencies between target components, as well as the execution order and conditions of component tasks corresponding to each target component, is to ensure the correct sequence and logic of the continuous delivery pipeline.

The dependency relationship between target components is used to indicate whether the task execution of a certain target component depends on the task execution result of another target component. For example, the output of a certain target component is the input of another target component.

The execution order between the component tasks corresponding to each target component refers to the order in which the component tasks corresponding to each target component are executed. For example, assuming that the component tasks corresponding to the three target components are a, b, and c, respectively, the execution order of the component tasks corresponding to the three target components can be to execute a first, and then execute b and c at the same time, that is, b and c are in a parallel execution relationship.

The execution conditions of the component tasks corresponding to each target component refer to the prerequisites for executing the component tasks corresponding to the target components. For example, the component task of a target component can be executed only after the component task of another target component is successfully executed, or the component task of a target component needs to wait for a set time after the component task of another target component is completed before it can be executed.

Step 103, generating a continuous delivery pipeline template according to the target components, dependencies, execution order, and execution conditions.

After selecting target components, determining the dependencies between target components, and the execution order and execution conditions of component tasks of each target component, a continuous delivery pipeline template can be automatically generated, or generated in response to a template generation instruction.

In a possible implementation, multiple continuous delivery pipeline templates may be established according to the above method.

In a possible implementation, the generated continuous delivery pipeline template may also be modified to obtain a new continuous delivery pipeline template.

In this embodiment, according to the continuous delivery requirements, multiple target components are selected from multiple candidate components of predefined component tasks; the dependencies between the target components, as well as the execution order and execution conditions of the component tasks corresponding to the target components are determined; and a continuous delivery pipeline template is generated according to the target components, dependencies, execution order, and execution conditions. Based on this, this application defines a standardized creation process for selecting the required target components based on the continuous delivery requirements and generating a continuous delivery pipeline template based on the target components. The process is simple, easy to manage, and can improve development efficiency and software quality.

This embodiment provides another template generation method. FIG2 is a flow chart of a template generation method provided in an embodiment of the present application.

As shown in FIG2 , the template generation method may include the following steps:

Step 201: receiving a component dragging instruction or a component selecting instruction triggered by a continuous delivery request, and selecting a target component from a plurality of candidate components based on the component dragging instruction or the component selecting instruction.

The component dragging instruction or the component selecting instruction can be triggered by the template creator according to the continuous delivery requirement, or can be automatically triggered by the electronic device according to the continuous delivery requirement.

The component dragging instruction or component selection instruction triggered by the continuous delivery request is used to instruct the selection of one or more target components from the candidate components.

Step 202: Obtain a first script that matches the continuous delivery requirement.

The first script is used to instruct the selection of a target component required for continuous delivery requirements from a plurality of candidate components. The first script may be written by a template creator or may be automatically generated according to the continuous delivery requirements.

Step 203: execute the first script to extract the target component identifier from the first script based on the first identifier, where the first identifier is used for naming the component identifier.

Identifiers are used to name elements such as variables, constants, and functions during the programming process.

The first identifier is predefined and is used to name the element of the component identification.

According to the first identifier, a component identification array is extracted from the first script, and the component identification in the component identification array is the target component identification.

The component identification refers to information such as the component name or component number that can uniquely identify the component.

Step 204 , selecting a target component corresponding to the target component identifier from a plurality of candidate components based on the correspondence between the component identifier and the components.

The correspondence between component identifiers and components is predefined.

After obtaining the target component identifier, the corresponding target component can be found according to the predefined corresponding relationship.

By selecting a target component from multiple candidate components through the first script, the automation level of the continuous delivery pipeline template creation process can be improved.

Step 202 to step 204 and step 201 are two parallel processes, that is, the target component can be selected through step 201, or the target component can be selected through steps 202 to step 204.

Step 205: Determine the dependency relationship between the target components, and the execution order and execution conditions of the component tasks corresponding to the target components.

Step 206: Generate a continuous delivery pipeline template according to the target components, dependencies, execution order, and execution conditions.

For the relevant contents in step 205 and step 206, reference may be made to the relevant descriptions in step 102 and step 103, which will not be repeated here.

In this embodiment, a component dragging instruction or a component selection instruction triggered by a continuous delivery request is received, and a target component is selected from multiple candidate components based on the component dragging instruction or the component selection instruction; or, a first script matching the continuous delivery requirement is obtained, and the first script is executed to select a target component from multiple candidate components according to a component identifier included in the first script. Two methods for selecting a target component are provided, wherein selecting a target component according to the first script improves the automation level of the continuous delivery pipeline template creation process.

This embodiment provides another template generation method. FIG. 3A is a flow chart of a template generation method provided in an embodiment of the present application.

As shown in FIG3A , the template generation method may include the following steps:

Step 301 , according to the continuous delivery requirement, multiple target components are selected from multiple candidate components of predefined component tasks.

For the relevant contents in step 301, reference may be made to the relevant description in the aforementioned embodiment, which will not be repeated here.

Step 302: Obtain a second script that matches the continuous delivery requirement, and execute the second script to determine the dependency relationship between the target components, and the execution order and execution conditions of the component tasks corresponding to the target components.

The second script may be written by the template creator, or the second script may be automatically generated according to continuous delivery requirements.

Optionally, the first script and the second script correspond to one script document or multiple script documents.

If the first script and the second script correspond to a script document, then the first script and the second script are two scripts in the script document. Based on the script document, the target component can be selected from the candidate components, and the dependency relationship between the target components and the execution order and execution conditions of the component tasks corresponding to the target components can be determined.

3B, the following describes the execution of the second script in step 302 to determine the dependencies between the target components, and the execution order and execution conditions of the component tasks corresponding to the target components. Specifically, the following steps are included:

Step 3021, execute the second script to extract at least one component identification array from the second script based on the second identifier, the second identifier is used to name the dependency, and the component identification array includes component identifications of two target components having a dependency relationship.

The second identifier is predefined and is used to name the element of the dependency relationship between the target components.

As an example, assuming that target component A depends on target component B, the corresponding component identification array can be [B, A]; assuming that target component A depends on target component B, and target component B depends on target component C, the corresponding component identification arrays can be [B, A] and [C, B].

Step 3022: Determine the dependency relationship between target components based on the component identification arrays.

Each component identification array is used to represent the dependency relationship between two target components. By combining all the extracted component identification arrays, it can be determined whether there is a dependency relationship between any two target components.

Step 3023, based on the component identification arrays, sort the component tasks corresponding to the target components to generate an execution order that satisfies the dependency relationship between the target components.

As an optional implementation, the component tasks may be topologically sorted based on the component identification arrays to obtain an execution order that satisfies all dependency relationships.

It should be noted that if there are dependencies between some target components and there are no dependencies between some target components, the execution order of component tasks corresponding to the target components without dependencies is variable. Therefore, the execution order generated in this case is not unique.

Assume that there are four target components, namely target component A, target component B, target component C and target component D. There is no dependency relationship between target component A, target component B and target component C, and target component D depends on target component C. Then the execution order of the generated component tasks can be A->B->C->D or B->A->C->D.

Step 3024: extract the execution conditions of the component tasks corresponding to each target component from the second script based on the third identifier, where the third identifier is used to name the execution conditions.

The third identifier is predefined and is used to name the element of the execution condition of the component task.

Each target component's component task corresponds to one or more execution conditions. As an example, an execution condition array of component tasks corresponding to each target component can be extracted from the second script based on the third identifier, and each execution condition array includes all execution conditions of the component tasks corresponding to the target component.

By determining the dependencies between the target components and the execution order and execution conditions of the component tasks corresponding to the target components based on the second script, the automation level of the continuous delivery pipeline template creation process can be further improved.

Step 303, determining the dependency relationship between the target components according to the first component connection line input in the first interactive interface; or determining the dependency relationship between the target components according to the dependency configuration information input in the second interactive interface.

The first interactive interface refers to the construction interface of the continuous delivery pipeline template, and the target component is displayed in the first interactive interface.

According to whether there is a first component connection line between the two target components, it can be determined whether there is a dependency relationship between the two target components.

The second interactive interface is an interface different from the first interactive interface. For example, the second interactive interface may be a dependency configuration interface that is triggered and displayed by a click event of any target component.

The first component connection line and dependency configuration information are input by the template creator.

Step 304, determining the execution order of component tasks corresponding to each target component according to the second component connection line input in the first interactive interface; or determining the execution order of component tasks corresponding to each target component according to the execution order configuration information input in the third interactive interface.

In order to facilitate relevant personnel to intuitively understand the dependency relationship between target components and the execution tasks of each component task, the line color and line shape of the second component connection line and the first component connection line may be different.

The third interactive interface is an interface different from the first interactive interface. For example, the third interactive interface may be an execution order configuration interface that is triggered and displayed by a click event of any target component.

Among them, the second component connection line and execution order configuration information are input by the template creator.

Step 305: Determine the execution conditions of the component tasks corresponding to each target component according to the execution condition configuration information input in the fourth interactive interface.

The fourth interaction interface is a configuration interface different from the first interaction interface. For example, the fourth interaction interface may be an execution condition configuration interface that is triggered and displayed by a click event of any target component.

The second interaction interface, the third interaction interface and the fourth interaction interface may be the same configuration interface, that is, the dependency relationship, the execution order and the execution conditions of the component tasks may be configured simultaneously through the configuration interface.

Among them, the execution condition configuration information is input by the template creator.

According to the input of each interactive interface, the dependencies between target components and the execution order and execution conditions of component tasks corresponding to each target component are determined, so that template creators can design continuous delivery pipeline templates according to actual continuous delivery needs, which is more flexible. In addition, when the continuous delivery pipeline template needs to be modified, new configuration information can be directly entered in each interactive interface, which is simple to operate.

It should be noted that step 302 and steps 303-305 are in a parallel relationship, that is, the dependency relationship between the target components and the execution order and execution conditions of the component tasks corresponding to the target components can be determined through step 302, and the dependency relationship between the target components and the execution order and execution conditions of the component tasks corresponding to the target components can also be determined through steps 303-305.

Step 306: Generate a continuous delivery pipeline template based on the target components, dependencies, execution order, and execution conditions.

For the relevant contents in step 306, reference may be made to the relevant descriptions in other embodiments, which will not be repeated here.

In this embodiment, multiple methods for determining the dependency between target components, as well as the execution order and execution conditions of component tasks corresponding to each target component are provided. By determining the dependency between target components, as well as the execution order and execution conditions of component tasks corresponding to each target component through a second script, the degree of automation of the continuous delivery pipeline template creation process can be further improved. Determining the dependency between target components, as well as the execution order and execution conditions of component tasks corresponding to each target component based on the input of each interactive interface can enable template creators to design continuous delivery pipeline templates based on actual continuous delivery requirements, with better flexibility.

This embodiment provides another template generation method. FIG4 is a flow chart of a template generation method provided in an embodiment of the present application.

As shown in FIG4 , the template generation method may include the following steps:

Step 401 , according to the continuous delivery requirement, multiple target components are selected from multiple candidate components of predefined component tasks.

Step 402, determining the dependency relationship between target components, and the execution order and execution conditions of component tasks corresponding to each target component.

Step 403: Generate a continuous delivery pipeline template according to the target components, dependencies, execution order, and execution conditions.

For the relevant contents in step 401 to step 403, reference can be made to the relevant descriptions in other embodiments, which will not be repeated here.

Step 404: Receive a template call instruction triggered by the continuous delivery project.

After one or more continuous delivery pipeline templates are created, template call instructions of any one or more continuous delivery pipeline templates may be received.

In an optional embodiment, a pipeline delivery person may click on the continuous delivery pipeline template to trigger a template call instruction.

Step 405: Generate a continuous delivery pipeline instance based on the continuous delivery pipeline template corresponding to the template calling instruction.

Every time a template call instruction is received, a continuous delivery pipeline instance is generated based on the corresponding continuous delivery pipeline template.

Step 406: Receive pipeline parameter configuration information input in the fifth interactive interface according to the continuous delivery project, and perform parameter configuration on the continuous delivery pipeline instance according to the pipeline parameter configuration information.

The fifth interaction interface is different from the first interaction interface, the second interaction interface, the third interaction interface and the fourth interaction interface.

The pipeline parameter configuration information is related to the continuous delivery project. Different continuous delivery projects may have different corresponding pipeline parameter configuration information.

The pipeline parameter configuration information includes the address of the code repository corresponding to the continuous delivery project, the branch name, the version of the build tool, and the test environment.

The parameters in the pipeline parameter configuration information can be divided into common parameters and special parameters, that is, some parameters in the pipeline parameter configuration information are common parameters of the target component, and the other parameters are unique parameters of one or more target components.

By configuring parameters for the continuous delivery pipeline instance, the continuous delivery pipeline template can be flexibly adapted to different project requirements and improve the reusability and adaptability of the continuous delivery pipeline template.

Optionally, the method also includes: obtaining execution information of the continuous delivery pipeline instance by setting a monitoring interface to determine the execution status of the continuous delivery pipeline instance, wherein the execution information includes the completion status, execution time and error information of each component task in the continuous delivery pipeline instance.

Each continuous delivery pipeline instance may correspond to an execution information table for storing execution information. In response to the continuous delivery pipeline instance starting execution, the latest execution information in the execution information table may be read by setting a monitoring interface to monitor the execution status of the continuous delivery pipeline instance in real time.

Real-time monitoring of the execution of continuous delivery pipeline instances can promptly identify and resolve problems in the execution process, ensuring the smooth progress of the continuous delivery pipeline.

After the continuous delivery pipeline instance is executed, the execution results of each target component can be obtained, such as code quality test results, test coverage test results, deployment success rate test results, etc., so that relevant personnel can understand the effect of the continuous delivery pipeline instance through the execution results, provide feedback on improvements, continuously optimize the efficiency and quality of the continuous delivery pipeline, and improve the reliability and stability of delivery.

In this embodiment, according to the continuous delivery requirements, multiple target components are selected from multiple candidate components of predefined component tasks; the dependencies between the target components and the execution order and execution conditions of the component tasks corresponding to the target components are determined; a continuous delivery pipeline template is generated according to the target components, dependencies, execution order and execution conditions; a template call instruction triggered by a continuous delivery project is received; a continuous delivery pipeline instance is generated based on the continuous delivery pipeline template corresponding to the template call instruction; pipeline parameter configuration information input in the fifth interactive interface according to the continuous delivery project is received, and parameters of the continuous delivery pipeline instance are configured according to the pipeline parameter configuration information. Based on this, the continuous delivery pipeline template in this application can flexibly adapt to different project requirements, improving the reusability and adaptability of the continuous delivery pipeline template.

In order to implement the above embodiment, the embodiment of the present application also proposes a template generating device.

FIG5 is a schematic diagram of the structure of a template generating device provided in an embodiment of the present application.

As shown in FIG5 , the template generating device 500 includes:

A component selection module 510 is used to select multiple target components from multiple candidate components of predefined component tasks according to continuous delivery requirements;

A determination module 520 is used to determine the dependency relationship between target components, and the execution order and execution conditions of component tasks corresponding to each target component;

The template generation module 530 is used to generate a continuous delivery pipeline template according to target components, dependencies, execution order, and execution conditions.

Optionally, the component selection module 510 is used to:

Receive a component drag command or a component selection command triggered by a continuous delivery request; select a target component from multiple candidate components based on the component drag command or the component selection command.

Optionally, the component selection module 510 is used to:

Get the first script that matches the continuous delivery requirements;

executing the first script to extract the target component identifier from the first script based on the first identifier, the first identifier being used for naming the component identifier;

According to the correspondence between the component identifier and the components, a target component corresponding to the target component identifier is selected from multiple candidate components.

Optionally, the determination module 520 is used to:

Get a second script that matches the continuous delivery requirements;

The second script is executed to determine the dependency relationship between the target components and the execution order and execution conditions of the component tasks corresponding to the target components.

Optionally, the determination module 520 is used to:

Execute the second script to extract at least one component identification array from the second script based on the second identifier, the second identifier is used to name the dependency relationship, and the component identification array includes component identifications of two target components having the dependency relationship;

Determine the dependency relationship between target components based on the component identification arrays;

Based on the component identification arrays, the component tasks corresponding to the target components are sorted to generate an execution order that satisfies the dependency relationship between the target components.

Based on the third identifier, the execution conditions of the component tasks corresponding to each target component are extracted from the second script, and the third identifier is used to name the execution conditions.

Optionally, the target component is displayed on the first interactive interface, and the determination module 520 is used to:

Determine the dependency relationship between the target components according to the first component connection line input in the first interactive interface; or determine the dependency relationship between the target components according to the dependency configuration information input in the second interactive interface;

Determine the execution order of component tasks corresponding to each target component according to the second component connection line input in the first interactive interface; or determine the execution order of component tasks corresponding to each target component according to the execution order configuration information input in the third interactive interface;

According to the execution condition configuration information input in the fourth interactive interface, the execution conditions of the component tasks corresponding to each target component are determined.

Optionally, the device further comprises:

An instruction receiving module, used to receive template calling instructions triggered by continuous delivery projects;

An instance generation module is used to generate a continuous delivery pipeline instance based on the continuous delivery pipeline template corresponding to the template call instruction;

The parameter configuration module is used to receive the pipeline parameter configuration information input in the fifth interactive interface according to the continuous delivery project, and configure the parameters of the continuous delivery pipeline instance according to the pipeline parameter configuration information.

Optionally, the device further comprises:

The monitoring module is used to obtain the execution information of the continuous delivery pipeline instance by setting the monitoring interface to determine the execution status of the continuous delivery pipeline instance, wherein the execution information includes the completion status, execution time and error information of each component task in the continuous delivery pipeline instance.

It should be noted that the above explanations of the template generation method embodiment are also applicable to the template generation device of this embodiment, and will not be repeated here.

Fig. 6 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Among them, the electronic device 600 in the present embodiment is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and/or required herein.

As shown in FIG6 , the electronic device 600 includes:

The memory 601 and the processor 602, a bus 603 connecting different components (including the memory 601 and the processor 602), the memory 601 stores a computer program, and when the processor 602 executes the program, the template generation method of the embodiment of the present application is implemented.

Bus 603 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

The electronic device 600 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 600, including volatile and non-volatile media, removable and non-removable media.

The memory 601 may also include a computer system readable medium in the form of a volatile memory, such as a random access memory (RAM) 604 and/or a cache memory 605. The electronic device 600 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, the storage system 606 may be used to read and write non-removable, non-volatile magnetic media (not shown in FIG. 6 , commonly referred to as a “hard drive”). Although not shown in FIG. 6 , a disk drive for reading and writing a removable non-volatile disk (such as a “floppy disk”) and an optical disk drive for reading and writing a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM or other optical medium) may be provided. In these cases, each drive may be connected to the bus 603 via one or more data medium interfaces. The memory 601 may include at least one program product having a set (such as at least one) of program modules, which are configured to perform the functions of the various embodiments of the present application.

A program/utility 608 having a set (at least one) of program modules 607 may be stored, for example, in the memory 601, such program modules 607 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 607 generally perform the functions and/or methods of the embodiments described herein.

The electronic device 600 may also communicate with one or more external devices 609 (e.g., keyboard, pointing device, display 611, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 600, and/or communicate with any device that enables the electronic device 600 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input/output (I/O) interface 612. Furthermore, the electronic device 600 may also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and/or public network, such as the Internet) through a network adapter 613. As shown in FIG. 6 , the network adapter 613 communicates with other modules of the electronic device 600 through a bus 603. It should be understood that, although not shown in the figure, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

The processor 602 executes various functional applications and data processing by running the programs stored in the memory 601 .

It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the template generation method of the embodiment of the present application, and will not be repeated here.

In order to implement the above embodiments, the present application also proposes a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the methods provided by the above embodiments.

In order to implement the above embodiments, the present application also proposes a computer program product, including a computer program, which implements the methods provided by the above embodiments when executed by a processor.

The collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this application are in compliance with relevant laws and regulations and do not violate public order and good morals.

It should be noted that personal information from users should be collected for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. In addition, such collection/sharing should be carried out after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement/user notice and sign the agreement/authorization including authorization of relevant user information before the user uses the function. In addition, any necessary steps should be taken to protect and safeguard access to such personal information data and ensure that others who have access to personal information data comply with its privacy policy and procedures.

The present application is expected to provide an implementation scheme for users to selectively block the use or access of personal information data. That is, the present disclosure is expected to provide hardware and/or software to prevent or block access to such personal information data. Once the personal information data is no longer needed, the risk can be minimized by limiting data collection and deleting the data. In addition, when applicable, such personal information is de-identified to protect the privacy of the user.

In the description of the aforementioned embodiments, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

The logic and/or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

The storage medium mentioned above may be a read-only memory, a disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.

Claims (10)

1. A template generation method, characterized by comprising the steps of:

Selecting a plurality of target components from a plurality of candidate components of a predefined component task according to continuous delivery requirements;

Determining the dependency relationship among the target components, and the execution sequence and the execution condition of the component tasks corresponding to the target components;

And generating a continuous delivery pipeline template according to the target component, the dependency relationship, the execution sequence and the execution condition.

2. The method of claim 1, wherein selecting a plurality of target components from a plurality of the candidate components of a predefined component task according to a continuous delivery demand comprises:

Receiving a component dragging instruction or a component selecting instruction triggered according to the continuous delivery request; and selecting the target component from a plurality of candidate components based on the component dragging instruction or the component selecting instruction.

3. The method of claim 1, wherein selecting a plurality of target components from a plurality of the candidate components of a predefined component task according to a continuous delivery demand comprises:

acquiring a first script matched with the continuous delivery demand;

Executing the first script to extract a target component identification from the first script based on a first identifier, the first identifier being used to name the component identification;

And selecting the target component corresponding to the target component identifier from a plurality of candidate components according to the corresponding relation between the component identifier and the components.

4. The method according to claim 1, wherein determining the dependency relationship between the target components and the execution order and execution conditions of the component tasks corresponding to the target components comprises:

acquiring a second script matched with the continuous delivery demand;

And executing the second script to determine the dependency relationship among the target components, and the execution sequence and the execution condition of the component tasks corresponding to the target components.

5. The method of claim 4, wherein executing the second script to determine the dependency relationship between each of the target components, and the execution order and execution conditions of the component tasks corresponding to each of the target components, comprises:

executing the second script to extract at least one component identification array from the second script based on a second identifier, wherein the second identifier is used for naming a dependency relationship, and the component identification array comprises component identifications of two target components with the dependency relationship;

determining a dependency relationship between the target components based on the component identification arrays;

Based on the component identification arrays, sequencing the component tasks corresponding to the target components to generate an execution sequence meeting the dependency relationship among the target components;

and extracting the execution condition of the component task corresponding to each target component from the second script based on a third identifier, wherein the third identifier is used for naming the execution condition.

6. The method according to claim 1, wherein the target components are displayed on a first interactive interface, the determining the dependency relationship between the target components, and the execution sequence and execution condition of the component tasks corresponding to the target components, includes at least one of:

Determining the dependency relationship among the target components according to a first component connecting line input in the first interactive interface; or determining the dependency relationship between the target components according to the dependency relationship configuration information input in the second interactive interface;

Determining the execution sequence of the component tasks corresponding to the target components according to the second component connecting lines input in the first interactive interface; or determining the execution sequence of the component tasks corresponding to the target components according to the execution sequence configuration information input in the third interactive interface;

and determining the execution conditions of the component tasks corresponding to the target components according to the execution condition configuration information input in the fourth interactive interface.

7. The method according to any one of claims 1-6, further comprising:

Receiving a template calling instruction triggered according to a continuous delivery project;

Generating a continuous delivery pipeline instance based on a continuous delivery pipeline template corresponding to the template calling instruction;

And receiving pipeline parameter configuration information input at the fifth interactive interface according to the continuous delivery project, and carrying out parameter configuration on the continuous delivery pipeline instance according to the pipeline parameter configuration information.

8. The method of claim 7, wherein the method further comprises:

and acquiring the execution information of the continuous delivery pipeline instance through a set monitoring interface to determine the execution state of the continuous delivery pipeline instance, wherein the execution information comprises the completion state, the execution time and the error information of each component task in the continuous delivery pipeline instance.

9. A template generating apparatus, comprising:

the component selecting module is used for selecting a plurality of target components from a plurality of candidate components of a predefined component task according to the continuous delivery requirement;

the determining module is used for determining the dependency relationship among the target components, and the execution sequence and the execution condition of the component tasks corresponding to the target components;

And the template generation module is used for generating a continuous delivery pipeline template according to the target component, the dependency relationship, the execution sequence and the execution condition.

10. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-8.