Deployment methods, devices, electronic equipment, and storage media for production lines
By splitting static functional templates into basic logical units and generating dynamic functional templates, the problem of excessively long deployment times in traditional programs is solved, achieving more efficient program deployment, which is suitable for server integration deployment scenarios.
Patent Information
- Application Number
- CN202211542914.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-02
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-12-02
AI Technical Summary
Traditional program deployment methods are too time-consuming and inefficient, and cannot meet the needs of modern software development.
By breaking down static functional templates into basic logic units, determining the target basic logic units and their arrangement order based on the functional groups and logic execution nodes of the target application, generating dynamic functional templates using different connection methods, and deploying basic logic units in parallel or serially to improve efficiency.
It enables the transformation from static pipeline deployment to dynamic pipeline deployment. The diversified connection methods improve program deployment efficiency, reduce deployment workload, and enhance software development efficiency.
Smart Images

Figure CN115934109B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and more specifically, to a pipeline deployment method, apparatus, electronic device, and storage medium. Background Technology
[0002] With the continuous development of information technology, the demand for software development is also increasing, making it particularly important to improve software development efficiency.
[0003] In the software development process, it is usually necessary to deploy the programs written by developers to a server for execution. Traditional program deployment requires deploying each program on the server in a static deployment order according to the order of program function groups and the execution logic order of each program in the function group.
[0004] However, this approach may result in excessively long deployment times and low efficiency. Summary of the Invention
[0005] The purpose of this application is to address the shortcomings of the prior art by providing a pipeline deployment method, apparatus, electronic device, and storage medium to improve the efficiency of program deployment.
[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:
[0007] In a first aspect, embodiments of this application provide a method for deploying a pipeline, including:
[0008] Obtain the basic logic units derived from the static functional template;
[0009] Based on the logic execution nodes in each functional group corresponding to the target application, determine the target basic logic units corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit;
[0010] According to the arrangement order, the target basic logic units are interconnected through different connection methods to generate target function templates corresponding to the function groups;
[0011] Based on the arrangement order of the basic logic units in the target function template, the functional groups corresponding to the target application are deployed.
[0012] Optionally, determining the target basic logic unit corresponding to each functional group and the arrangement order of the target basic logic units from each basic logic unit according to each logical execution node in each functional group corresponding to the target application includes:
[0013] Based on each execution node in the execution logic of the target application, determine at least one functional group corresponding to the target application;
[0014] Based on the logical execution nodes in each functional group and the version information of each functional group, the target basic logic unit corresponding to each functional group under each version and the arrangement order of each target basic logic unit are determined from each basic logic unit. The basic logic unit is used to execute the steps of the corresponding program; the arrangement order includes serial and parallel.
[0015] Optionally, the step of connecting each target basic logic unit to the others through different connection methods according to the arrangement order to generate target function templates corresponding to the function groups includes:
[0016] In response to the drag-and-drop operation of the target basic logic unit control corresponding to each functional group in each version, which is entered through the visual interface, the target basic logic units are connected to each other according to the arrangement order of each functional group in each version, and the functional templates corresponding to each functional group in each version are generated.
[0017] Store the identifiers of each functional group, the version identifiers of each functional group, and the functional templates for each version of each functional group in the functional template library.
[0018] Optionally, storing the identifier of each functional group, the version identifier corresponding to each functional group, and the functional templates for each version corresponding to each functional group into the functional template library includes:
[0019] Test the execution of the functional templates for each version of each functional group. Based on the results, correct the parameter information of each basic logic unit in the functional templates for each version of each functional group, or correct the basic logic units and their arrangement order in the functional templates for each version of each functional group.
[0020] Optionally, before generating the target function template corresponding to the function group by interconnecting the target basic logic units with different connection methods according to the arrangement order, the following steps are included:
[0021] Receive an application deployment request, the application deployment request including: each functional group corresponding to the target application, and the version identifier corresponding to each functional group;
[0022] Based on the functional groups corresponding to the target application in the application deployment request and the version identifiers corresponding to each functional group, each target functional template matching each functional group is determined from the functional template library, so as to deploy each functional group corresponding to the target application in the application deployment request according to each target functional template.
[0023] Optionally, the step of deploying the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template includes:
[0024] Based on the arrangement order of the basic logic units in the target function template, a number of basic logic units that can be deployed in parallel are determined. When deploying the function group, the number of basic logic units that can be deployed in parallel are deployed in parallel, and the logic units other than the number of basic logic units that can be deployed in parallel are deployed serially according to the arrangement order.
[0025] Optionally, the step of deploying the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template includes:
[0026] Store the functional groups corresponding to the target application into the storage directory corresponding to the target application;
[0027] Based on the arrangement order of the basic logic units in the target function template, each function group is read from the storage directory corresponding to the target application and deployed.
[0028] Secondly, embodiments of this application also provide a deployment apparatus for a pipeline, including: an acquisition module, a determination module, a generation module, and a deployment module;
[0029] The acquisition module is used to acquire each basic logic unit obtained from the static functional template.
[0030] The determining module is used to determine the target basic logic unit corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit according to each logical execution node in each functional group corresponding to the target application.
[0031] The generation module is used to connect each target basic logic unit to each other through different connection methods according to the arrangement order, and generate target function templates corresponding to the function groups.
[0032] The deployment module is used to deploy the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template.
[0033] Optionally, the determining module is specifically used to determine at least one functional group corresponding to the target application based on each execution node in the execution logic of the target application;
[0034] Based on the logical execution nodes in each functional group and the version information of each functional group, the target basic logic unit corresponding to each functional group under each version and the arrangement order of each target basic logic unit are determined from each basic logic unit. The basic logic unit is used to execute the steps of the corresponding program; the arrangement order includes serial and parallel.
[0035] The generation module is specifically used to respond to the drag operation of the target basic logic unit control corresponding to each functional group in each version, which is input through the visual interface, and to connect the target basic logic units to each other according to the arrangement order of each target basic logic unit in each version of each functional group, so as to generate the functional template corresponding to each version of each functional group.
[0036] Store the identifiers of each functional group, the version identifiers of each functional group, and the functional templates for each version of each functional group in the functional template library.
[0037] The generation module is specifically used to test and execute the functional templates of each version corresponding to each functional group. Based on the running results, it corrects the parameter information of each basic logic unit in the functional template of each version corresponding to each functional group, or corrects the basic logic units contained in the functional template of each version corresponding to each functional group and the arrangement order of the basic logic units.
[0038] Optionally, the device further includes: a receiving module;
[0039] The receiving module is used to receive an application deployment request, which includes: each functional group corresponding to the target application, and the version identifier corresponding to each functional group;
[0040] The determining module is further configured to determine each target function template matching each function group from the function template library based on each function group corresponding to the target application in the application deployment request and the version identifier corresponding to each function group, so as to deploy each function group corresponding to the target application in the application deployment request according to each target function template.
[0041] Optionally, the deployment module is specifically used to determine multiple basic logical units that can be deployed in parallel according to the arrangement order of each basic logical unit in the target function template, and when deploying the function group, to deploy the multiple basic logical units that can be deployed in parallel in parallel, and to deploy the logical units other than the multiple basic logical units that can be deployed in parallel in serial order according to the arrangement order.
[0042] Optionally, the deployment module is specifically used to store the functional groups corresponding to the target application into the storage directory corresponding to the target application;
[0043] Based on the arrangement order of the basic logic units in the target function template, each function group is read from the storage directory corresponding to the target application and deployed.
[0044] Thirdly, embodiments of this application provide an electronic device, including: a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the pipeline deployment method provided in the first aspect.
[0045] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the pipeline deployment method provided in the first aspect.
[0046] The beneficial effects of this application are:
[0047] This application provides a pipeline deployment method, apparatus, electronic device, and storage medium. The method involves decomposing a static pipeline functional template to obtain basic logic units. Based on the logic execution nodes in the functional groups of the target application, the target basic logic units corresponding to the functional groups and the arrangement order of each basic logic unit are determined from the decomposed basic logic units. Then, based on the determined arrangement order, different connection methods are used to dynamically reassemble the connection order of each basic logic unit, generating a dynamic functional template. This breaks the problem of the single connection method of basic logic units in traditional static pipeline deployment, making the connection methods of basic logic units more diverse. This achieves the transformation from static pipeline deployment to dynamic pipeline deployment. When pipeline deployment is based on dynamic functional templates, due to the diversified connection methods of each basic logic unit, each basic logic unit does not need to wait for execution sequentially; execution can be achieved through other connection methods, thereby effectively improving deployment efficiency. Attached Figure Description
[0048] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0049] Figure 1 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 1 ;
[0050] Figure 2 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 2 ;
[0051] Figure 3 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 3 ;
[0052] Figure 4 A schematic diagram of a functional template provided in an embodiment of this application;
[0053] Figure 5 This is a schematic diagram of a first interface provided for an embodiment of this application;
[0054] Figure 6 This is a second interface diagram provided for an embodiment of this application;
[0055] Figure 7 A schematic diagram of another functional template provided in an embodiment of this application;
[0056] Figure 8 This is a schematic diagram of a third interface provided in an embodiment of this application;
[0057] Figure 9 This is a schematic diagram of a fourth interface provided in an embodiment of this application;
[0058] Figure 10 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 4 ;
[0059] Figure 11 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 5 ;
[0060] Figure 12 A schematic diagram of a deployment device for an assembly line provided in an embodiment of this application;
[0061] Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0062] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.
[0063] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0064] To enable those skilled in the art to use the content of this application, the following implementation methods are provided in conjunction with the specific application scenario of "server integrated deployment". Those skilled in the art can apply the general principles defined herein to other embodiments and application scenarios without departing from the spirit and scope of this application.
[0065] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.
[0066] Figure 1 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 1 The execution subject of this method can be a server, such as... Figure 1 As shown, the method may include:
[0067] S101. Obtain the basic logic units obtained from the static function template.
[0068] Typically, software goes through multiple stages from development to official release and operation. These stages include: developers writing the program, compiling and packaging the program, testing, releasing the program after successful testing, and finally, operations and maintenance personnel deploying the program to the server. Once the program is running on the server, the developed software application is provided to users for normal use.
[0069] Regarding the program deployment phase, each functional program is deployed using the conventional static pipeline deployment method. When there are many programs to be deployed, this may result in a large workload. This solution provides a dynamic and diversified deployment method to reduce the workload during the program deployment process.
[0070] Multiple basic logic units can be obtained by first splitting from the static function template. The static function template can refer to the existing function template in which each basic logic unit is connected in a serial manner. The arrangement of each basic logic unit in the static function template is fixed, single, and immutable. When pipeline deployment is carried out based on the static function template, it is deployed in a single deployment manner.
[0071] S102. Based on the logic execution nodes in each functional group corresponding to the target application, determine the target basic logic unit corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit.
[0072] Optionally, a functional group can refer to a functional module or a functional unit within a complete application software. Here, the target application can refer to a complete software, and the functional groups corresponding to the target application can refer to the functions to be developed within the software. For example, if the target application is website A, the development of website A may include the development of the front-end webpage and the back-end development. In this case, front-end development and back-end development can each be considered as a functional group corresponding to the target application.
[0073] Based on the determined functional groups, the target basic logic units corresponding to the functional groups can be determined from the multiple basic logic units obtained from the decomposition, according to the logical execution nodes contained in each functional group.
[0074] Taking the front-end functional group as an example, the front-end development process may include multiple logical execution nodes such as compilation, retrieval, and packaging. Therefore, compilation, retrieval, and packaging can all be regarded as a logical execution node of the functional group. Thus, based on the program steps executed by each basic logical unit, the target basic logical units corresponding to the functional group can be determined from each basic logical unit.
[0075] Optionally, based on the execution logic order of each logical execution node in the functional group, the arrangement order of each target basic logic unit can also be determined. The arrangement order refers to the connection order. For each logical execution node that can be executed in parallel, the parallel arrangement order between the basic logic units corresponding to each logical execution node can be determined. For each logical execution node that cannot be executed in parallel, the serial arrangement order between the basic logic units corresponding to each logical execution node can be determined. Based on the determined parallel and serial arrangement order of each basic logic unit, the target basic logic units corresponding to the functional group can be connected to generate the target functional template corresponding to the functional group.
[0076] S103. According to the arrangement order, connect the basic logic units of each target through different connection methods to generate the target function templates corresponding to the function groups.
[0077] Optionally, based on the target basic units corresponding to the determined functional groups and the arrangement order of the target basic units, the target basic units can be connected in the arrangement order to generate the target functional templates corresponding to the functional groups.
[0078] Because the orchestration of the target basic logic units is no longer limited to a single method, but is flexibly determined based on the logical execution nodes of the target application's functional groups, the deployment of the pipeline becomes more diverse. This diverse deployment allows for different connection methods for the basic logic units, resulting in a wider coverage of the pipeline deployment. Compared to the single connection method of each basic logic unit in traditional static pipeline templates, this naturally improves deployment efficiency.
[0079] S104. Deploy the functional groups corresponding to the target application according to the arrangement order of each basic logic unit in the target function template.
[0080] Each functional group may include one or more basic logic units. Each functional group and each basic logic unit can be understood as a program. The basic logic unit can be understood as a subroutine in the functional group. Deploying the functional groups corresponding to the target application is actually deploying the programs of each functional group.
[0081] Optionally, each functional group can be deployed based on the arrangement order of each basic logical unit in the target functional template. Since each basic logical unit is no longer limited to a serial connection method, programs that can be deployed in parallel can be deployed to the server in parallel as much as possible, breaking the conventional serial deployment method, thereby reducing the workload of program deployment to a certain extent and improving deployment efficiency.
[0082] In summary, the pipeline deployment method provided in this embodiment decomposes a static pipeline functional template to obtain basic logic units. Based on the logic execution nodes in the functional groups of the target application, the target basic logic units corresponding to the functional groups and the arrangement order of each basic logic unit are determined from the decomposed basic logic units. Therefore, based on the determined arrangement order, different connection methods can be used to dynamically reassemble the connection order of each basic logic unit to generate a dynamic functional template. This breaks the problem of the single connection method of basic logic units in traditional static pipeline deployment, making the connection methods of basic logic units more diversified. This achieves the transformation from static pipeline deployment to dynamic pipeline deployment. When pipeline deployment is based on dynamic functional templates, due to the diversified connection methods of each basic logic unit, each basic logic unit does not need to wait for execution sequentially; it can be executed through other connection methods, thereby effectively improving deployment efficiency.
[0083] Figure 2 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 2 In step S102, based on the logical execution nodes in each functional group corresponding to the target application, the target basic logic units corresponding to each functional group and the arrangement order of each target basic logic unit are determined from each basic logic unit. This may include:
[0084] S201. Based on each execution node in the execution logic of the target application, determine at least one functional group corresponding to the target application.
[0085] The target application can be any possible application. For different target applications, at least one functional group can be determined. It should be explained that the execution logic of each target application is different, and the functions to be deployed are also different. Different functions correspond to different functional groups, so the number of functional groups corresponding to each target application is also different. For example, target application 1 may need to perform both front-end development and back-end development, so target application 1 may include 2 functional groups, while target application 2 only needs to perform back-end development, so target application 2 may include 1 functional group.
[0086] The target basic logical units corresponding to each functional group of the target application can also be different. For example, functional group 1 of target application 1 may include three target logical units: compilation, packaging, and environment configuration, while functional group 2 of target application 1 may include three target logical units: compilation, packaging, and code retrieval. When the target application is determined, the corresponding functional groups and the target basic logical units contained within those functional groups are also determined. It is worth noting that a basic logical unit can refer to a piece of program, and since a program is designed to implement specific steps or functions, the basic logical unit can be used to execute the steps of the program indicated by the basic logical unit.
[0087] S202. Based on the logic execution nodes in each functional group and the version information of each functional group, determine the target basic logic unit corresponding to each functional group under each version and the arrangement order of each target basic logic unit from each basic logic unit. The basic logic unit is used to execute the steps of the corresponding program; the arrangement order includes serial and parallel.
[0088] Different applications have different execution nodes for their execution logic when they are developed and put into use. For example, some applications only provide users with browsing functionality and only have front-end execution nodes, while others not only have browsing functionality but also interactive operation functionality, and have both front-end and back-end execution nodes. Different logical execution nodes can correspond to a functional group. For example, if the target application only includes front-end development, then its execution logic execution nodes only include front-end development nodes, and the corresponding functional group for the target application can be the front-end development functional group. However, if the target application includes both front-end and back-end development, then its execution logic execution nodes include both front-end and back-end development nodes, and the corresponding functional groups for the target application can include both front-end development functional groups and back-end development functional groups.
[0089] The same functional group may have different versions, similar to some application software that is constantly updated. Each version update is based on code updates. The basic logic units and the connection order of the basic logic units may change in different versions of the same functional group. For example, functional group 1 in version 1 may be composed of basic logic unit 1 and basic logic unit 2, while functional group 1 in version 2 may be composed of basic logic unit 1, basic logic unit 2, and basic logic unit 3, etc.
[0090] Therefore, based on the version information of the functional groups, the target basic logic unit corresponding to the functional groups in different versions can be determined.
[0091] Figure 3A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 3 In step S103, according to the arrangement order, the target basic logic units are interconnected through different connection methods to generate the target function templates corresponding to the function groups, including:
[0092] S301. In response to the drag-and-drop operation of the target basic logic unit control corresponding to each functional group in each version, input through the visual interface, the target basic logic units are connected to each other according to the arrangement order of each functional group in each version, and the functional templates corresponding to each functional group in each version are generated.
[0093] Optionally, dynamic deployment can be achieved by dragging and dropping to adjust the deployment steps, simplifying the operation process by making complex deployments easier by dragging and dropping blocks.
[0094] In one feasible approach, this method can be implemented based on a visual interface, which may include all basic logic unit controls. Each basic logic unit control may be generated based on the basic parameter information of each basic logic unit obtained after splitting the serial static deployment process.
[0095] Optionally, the static deployment process can be stored in a text file. The various programs in the static deployment process can be broken down in the text file to obtain each basic logic unit and its parameter information. Based on the parameter information of each basic logic unit, the controls of each basic logic unit can be generated.
[0096] The parameter information of each basic logic unit can be the default value, or it can be modified according to the requirements, or the parameter information of some basic logic units can be added.
[0097] Optionally, the arrangement order of each target basic logic unit corresponding to each functional group can be determined according to the functional attributes of each functional group. The arrangement order refers to the connection order. Based on the determined connection order of each target basic logic unit, each target basic logic unit can be connected to generate the functional template of the functional group.
[0098] Figure 4 This is a schematic diagram of a functional template provided in an embodiment of this application. For example... Figure 4 As shown, this functional template includes basic logic units with parallel connections as well as basic logic units with serial connections.
[0099] It is worth noting here that Figure 4The functional template shown is a functional template generated based on functions. When splitting the static deployment process file as described above, the basic logical units can be separated from the file according to the functions of each program.
[0100] Figure 5 The first interface diagram provided in this application embodiment shows that after separating each basic logic unit from the static deployment process file, the parameters of each basic logic unit can be saved first, such as... Figure 5 As shown, the basic logic units are assumed to include: general code operations, xhb code - no parameters, xhb code - looping based on host, and xhb code - obtaining with parameters. The left half of the interface corresponds to the name of each basic logic unit and the script type of each basic logic unit, while the right half is the user editing area. Users can modify, delete, or save the parameters of each basic logic unit through the editing controls corresponding to each basic logic unit in the right half.
[0101] Figure 6 This is a second interface diagram provided in an embodiment of this application. When a user... Figure 5 After the editor controls in the interface input parameters to modify the basic logic unit, the results can be displayed as follows: Figure 6 The image shown can be viewed Figure 6 The parameter list shown allows you to select or add parameters from the underlying logic unit whose parameters need to be modified, such as... Figure 6 Only a few possible parameters, such as parameter name, parameter type, and parameter type, are listed as examples.
[0102] Figure 7 This is a schematic diagram of another functional template provided in an embodiment of this application. Figure 7 The functional template shown is a functional template generated based on the process. When splitting the static deployment process file as described above, the functional template generated based on the process can be split into process units from the file according to the execution flow corresponding to each program.
[0103] In the process-based functional template, each process unit may contain one or more of the above-mentioned basic logical units. That is, the program in the process unit is not a minimal, indivisible program, but may be a combination of multiple programs.
[0104] When selecting a function template, you can also determine whether to select a function-based template or a process-based template based on deployment requirements.
[0105] S302. Store the identifier of each functional group, the version identifier of each functional group, and the functional templates of each version of each functional group into the functional template library.
[0106] Therefore, each functional group can generate a corresponding functional template in each version, thus obtaining the functional templates for each functional group in each version.
[0107] Optionally, in step S203, based on the generated function templates for each version of the function group, the identifier of each function group, the version identifier corresponding to each function group, and the function templates for each version of each function group can be stored in the function template library. This allows the function template corresponding to a function group to be searched in the function template library according to the function group's identifier and version identifier.
[0108] Figure 8 This is a schematic diagram of a third interface provided for an embodiment of this application. For example... Figure 8 As shown, the process of generating functional groups is also the process of creating functional groups, which can be done in... Figure 8 The system allows you to edit relevant information about functional groups to generate functional groups. For example, you can edit the name, group type, and deployment base data of a functional group. The deployment base data can be the parameter information of each basic logical unit included in the functional group.
[0109] In some embodiments, the identifier of the function group, the version identifier of the function group, and the function templates under each version of the function group can be stored in the function template library, so that the corresponding function template can be uniquely retrieved from the function template library based on the identifier of the function group and the version identifier of the function group.
[0110] Figure 9 This is a fourth interface diagram provided in an embodiment of this application. For the created functional groups, it can be accessed through... Figure 9 The interface shown presents information about the functional groups to the user, so that the user can check the accuracy of the generated functional group information in a timely manner. This may include the display of the names of each basic logical unit in the functional group, the display of the functional group version identifier, and may also include a user operation area where the user can add, delete, query, and modify the information of the functional group. Figure 9 The image only shows a portion of the information in the functional groups as an example.
[0111] Optionally, in step S302, storing the identifier of each functional group, the version identifier corresponding to each functional group, and the functional templates under each version corresponding to each functional group into the functional template library may include: testing and executing the functional templates under each version corresponding to each functional group, and correcting the parameter information of each basic logic unit in the functional templates under each version corresponding to each functional group based on the running results, or correcting the basic logic units contained in the functional templates under each version corresponding to each functional group and the arrangement order of the basic logic units.
[0112] In one feasible approach, after creating the functional templates corresponding to each functional group, the created functional templates can be tested before being stored in the functional template library. Any problematic functional templates can be corrected before storage, thus ensuring the accuracy of each functional template stored in the functional template library.
[0113] Optionally, for each functional template, the execution of the functional template can be initiated by clicking the execution control. During the execution of the functional template, the basic logic units in the functional template will be executed sequentially according to their serial and parallel connections.
[0114] Continue with Figure 4 Taking the functional template in the example, when it runs to basic logic unit 1, an error occurs and the functional template stops executing. This indicates that there may be a problem with basic logic unit 1. You can check the execution log corresponding to basic logic unit 1 to determine the problem. It may be that the parameter information is incorrect or there are other problems.
[0115] For problematic basic logic units, you can click on the basic logic unit control and modify the erroneous parameters in the pop-up information configuration box. After modification, you can re-execute the function template until it is successfully executed. The modified function template is then stored in the function template library as the function template corresponding to the function group.
[0116] Figure 10 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 4 Optionally, in step S103, before connecting the target basic logic units to each other using different connection methods according to the arrangement order to generate the target function template corresponding to the function group, the following may be included:
[0117] S1001. Receive application deployment request. The application deployment request includes: each functional group corresponding to the target application, and the version identifier corresponding to each functional group.
[0118] Optionally, the application deployment request can be initiated by the developer, and the application deployment request can include the functional group corresponding to the target application to be deployed and the version identifier corresponding to the functional group.
[0119] S1002. Based on the functional groups corresponding to the target application in the application deployment request and the version identifiers corresponding to each functional group, determine the target functional templates that match each functional group from the functional template library, and deploy each functional group corresponding to the target application in the application deployment request according to each target functional template.
[0120] Optionally, based on the functional groups corresponding to the target application contained in the application deployment request, the identifier of each functional group can be determined, and based on the identifier of the functional group and the version identifier corresponding to the functional group, the target functional template matched by each functional group can be uniquely determined.
[0121] It is worth noting that the version identifiers of the same function group are all unique. Therefore, by combining the function group identifier and the function group version identifier, the target function template matched by the function group can be uniquely determined.
[0122] The function template library contains multiple pre-configured function templates. For each function group, different versions will correspond to a function template. The function template is composed of multiple interconnected basic logic units. The basic logic unit can refer to the smallest indivisible program. Multiple basic logic units are connected in a preset arrangement order. Some basic logic units can be connected in parallel, and some basic logic units can be connected in serial order.
[0123] Once the target application's corresponding functional groups are matched with their respective target function templates, then each functional group of the target application can be deployed based on its respective target function template.
[0124] Optionally, in step S104, deploying the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template may include: determining multiple basic logical units that can be deployed in parallel according to the arrangement order of the basic logical units in the target functional template; deploying the multiple basic logical units that can be deployed in parallel when deploying the functional groups; and deploying the logical units other than the multiple basic logical units that can be deployed in parallel in sequence according to the arrangement order.
[0125] In some embodiments, parallel deployment and serial deployment can be performed based on the target function template matched from the function template library and according to the arrangement order of the basic logic units in the target function template.
[0126] In this process, the basic logic units connected in parallel within the functional template can be deployed in parallel, while the basic logic units connected in series are deployed in series, thereby completing the deployment of the functional group. The deployment of the functional group is actually the deployment of the program of the functional group.
[0127] Figure 11 A flowchart illustrating the pipeline deployment method provided in this application embodiment. Figure 5 Optionally, in step S104, deploying the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template may include:
[0128] S1101. Store the functional groups corresponding to the target application in the storage directory corresponding to the target application.
[0129] In some embodiments, when generating the functional template of the functional group, each functional group corresponding to the application to be deployed can be created first according to the application to be deployed. Here, creation can be understood as creating the identifier, version information, and the correspondence between the parameter information of each basic logical unit in the functional group and the functional group. The information of each functional group that has been created can be stored in the storage directory corresponding to the application to be deployed.
[0130] S1102. Based on the arrangement order of each basic logic unit in the target function template, read and deploy each function group from the storage directory corresponding to the target application.
[0131] Alternatively, when deploying functional groups, each basic logic unit can be executed sequentially according to the arrangement order of each basic logic unit in the target functional template.
[0132] Optionally, developers can write the relevant programs of the parts they are responsible for developing into the storage directory of the target application, and store the correspondence between programs and functional groups or basic logic units. When executing each basic logic unit according to the arrangement order of each basic logic unit in the functional template, the parameter information of each basic logic unit can be called from the storage target corresponding to the target application. At the same time, according to the correspondence between basic logic units and programs, the relevant programs of each basic logic unit under the functional group are loaded onto the service.
[0133] When a developer is independently responsible for a feature group, they can directly load the corresponding program for the feature group onto the server from the storage directory of the target application, based on the correspondence between the feature group and the program.
[0134] When a developer is responsible for a basic logic unit within a functional group, they can load the corresponding programs for each basic logic unit in the functional group onto the server from the storage directory corresponding to the target application, based on the correspondence between the basic logic unit and the program.
[0135] Optionally, once the program is loaded, its deployment is complete. Based on the deployed program, users can click to run it, which will install the target application. Users can then log in and use the target application through the front-end interactive interface displayed on the terminal.
[0136] Furthermore, it should be noted that the parallel deployment of this method can be reflected in two aspects: firstly, the parallel deployment of each basic logic unit within a functional group; and secondly, the deployment of different functional groups. This embodiment mainly uses the parallel deployment of each basic logic unit within a functional group as an example for illustration. However, for the deployment of different functional groups, it can be achieved by simultaneously receiving program deployment requests initiated by different users to process the deployment of functional groups from different users in parallel.
[0137] In summary, the pipeline deployment method provided in this embodiment decomposes a static pipeline functional template to obtain basic logic units. Based on the logic execution nodes in the functional groups of the target application, the target basic logic units corresponding to the functional groups and the arrangement order of each basic logic unit are determined from the decomposed basic logic units. Therefore, based on the determined arrangement order, different connection methods can be used to dynamically reassemble the connection order of each basic logic unit to generate a dynamic functional template. This breaks the problem of the single connection method of basic logic units in traditional static pipeline deployment, making the connection methods of basic logic units more diversified. This achieves the transformation from static pipeline deployment to dynamic pipeline deployment. When pipeline deployment is based on dynamic functional templates, due to the diversified connection methods of each basic logic unit, each basic logic unit does not need to wait for execution sequentially; it can be executed through other connection methods, thereby effectively improving deployment efficiency.
[0138] The following describes the apparatus, equipment, and storage medium used to implement the pipeline deployment method provided in this application. The specific implementation process and technical effects are described above and will not be repeated below.
[0139] Figure 12 This is a schematic diagram of a pipeline deployment device provided in an embodiment of this application. The functions implemented by this pipeline deployment device correspond to the steps performed by the method described above. This device can be understood as the aforementioned server, or the server's processor, or as a component that implements the functions of this application under server control, independent of the aforementioned server or processor, such as... Figure 12 As shown, the device may include: an acquisition module 1130, a determination module 1131, a generation module 1132, and a deployment module 1133;
[0140] The module 1130 is used to acquire the basic logic units obtained from the static function template.
[0141] The determination module 1131 is used to determine the target basic logic unit corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit according to each logic execution node in each functional group corresponding to the target application.
[0142] The generation module 1132 is used to connect the target basic logic units to each other in different connection methods according to the arrangement order, and generate the target function templates corresponding to the function groups.
[0143] Deployment module 1133 is used to deploy the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template.
[0144] Optionally, the determining module 1131 is specifically used to determine at least one functional group corresponding to the target application based on each execution node in the execution logic of the target application;
[0145] Based on the logic execution nodes in each functional group and the version information of each functional group, the target basic logic unit corresponding to each functional group under each version and the arrangement order of each target basic logic unit are determined from each basic logic unit. The basic logic unit is used to execute the steps of the corresponding program; the arrangement order includes serial and parallel.
[0146] The generation module 1132 is specifically used to respond to the drag operation of the target basic logic unit control corresponding to each functional group in each version, which is input through the visual interface, and to connect the target basic logic units to each other according to the arrangement order of each functional group in each version, so as to generate the functional template corresponding to each functional group in each version.
[0147] Store the identifiers of each functional group, the version identifiers of each functional group, and the functional templates for each version of each functional group in the functional template library.
[0148] The generation module 1132 is specifically used to test and execute the functional templates of each version corresponding to each functional group. Based on the running results, it corrects the parameter information of each basic logic unit in the functional templates of each version corresponding to each functional group, or corrects the basic logic units contained in the functional templates of each version corresponding to each functional group and the arrangement order of the basic logic units.
[0149] Optionally, the device further includes: a receiving module;
[0150] The receiving module is used to receive application deployment requests. The application deployment requests include: the functional groups corresponding to the target application, and the version identifiers corresponding to each functional group.
[0151] The determination module 1131 is further configured to determine each target function template matching each function group from the function template library based on each function group corresponding to the target application in the application deployment request and the version identifier corresponding to each function group, so as to deploy each function group corresponding to the target application in the application deployment request according to each target function template.
[0152] Optionally, the deployment module 1133 is specifically used to determine multiple basic logical units that can be deployed in parallel according to the arrangement order of each basic logical unit in the target function template, and to deploy the multiple basic logical units that can be deployed in parallel in parallel when deploying the function group, and to deploy the logical units other than the multiple basic logical units that can be deployed in parallel in sequence according to the arrangement order.
[0153] Optionally, the deployment module 1133 is specifically used to store the functional groups corresponding to the target application to the storage directory corresponding to the target application;
[0154] Based on the arrangement order of the basic logical units in the target function template, each function group is read from the storage directory corresponding to the target application and deployed.
[0155] The above-described device is used to execute the method provided in the foregoing embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.
[0156] These modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).
[0157] The modules described above can be connected or communicate with each other via wired or wireless connections. Wired connections can include metal cables, optical fibers, hybrid cables, or any combination thereof. Wireless connections can include connections via LAN, WAN, Bluetooth, ZigBee, or NFC, or any combination thereof. Two or more modules can be combined into a single module, and any module can be divided into two or more units. Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here.
[0158] Figure 13This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The terminal can be a server or a computing device with data processing capabilities.
[0159] The device may include: a processor 801 and a storage medium 802.
[0160] Storage medium 802 is used to store programs, and processor 801 calls the programs stored in storage medium 802 to execute the above method embodiments. The specific implementation and technical effects are similar, and will not be described in detail here.
[0161] The storage medium 802 stores program code, which, when executed by the processor 801, causes the processor 801 to perform various steps in the pipeline deployment method according to various exemplary embodiments of this application described in the "Exemplary Methods" section above.
[0162] The processor 801 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.
[0163] Storage medium 802, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The storage medium can include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type storage medium, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage medium, magnetic disk, optical disk, etc. The storage medium is any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, storage medium 802 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.
[0164] Optionally, this application also provides a program product, such as a computer-readable storage medium, including a program that, when executed by a processor, performs the above-described method embodiments.
[0165] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0166] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0167] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.
[0168] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A method of deploying a pipeline, characterized by, include: Obtain the basic logic units obtained from the static function template; the static function template is a function template in which the existing basic logic units are connected in a serial manner, and the arrangement of the basic logic units in the static function template is fixed and singular; Based on the logic execution nodes in each functional group corresponding to the target application, determine the target basic logic units corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit; According to the arrangement order, the target basic logic units are interconnected through different connection methods to generate target function templates corresponding to the function groups; Based on the arrangement order of each basic logic unit in the target function template, the functional groups corresponding to the target application are deployed. The step of determining the target basic logic units corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit based on each logical execution node in each functional group corresponding to the target application includes: Based on each execution node in the execution logic of the target application, determine at least one functional group corresponding to the target application; Based on the logical execution nodes in each functional group and the version information of each functional group, the target basic logic unit corresponding to each functional group under each version and the arrangement order of each target basic logic unit are determined from each basic logic unit. The basic logic unit is used to execute the steps of the corresponding program; the arrangement order includes serial and parallel.
2. The method of claim 1, wherein, The step of connecting each target basic logic unit to each other through different connection methods according to the arrangement order to generate target function templates corresponding to function groups includes: In response to the drag-and-drop operation of the target basic logic unit control corresponding to each functional group in each version, which is entered through the visual interface, the target basic logic units are connected to each other according to the arrangement order of each functional group in each version, and the functional templates corresponding to each functional group in each version are generated. Store the identifiers of each functional group, the version identifiers of each functional group, and the functional templates for each version of each functional group in the functional template library.
3. The method of claim 2, wherein, The step of storing the identifier of each functional group, the version identifier corresponding to each functional group, and the functional templates for each version of each functional group into the functional template library includes: Test the execution of the functional templates for each version of each functional group. Based on the results, correct the parameter information of each basic logic unit in the functional templates for each version of each functional group, or correct the basic logic units and their arrangement order in the functional templates for each version of each functional group.
4. The method of claim 2, wherein, Before generating the target function template corresponding to the function group by connecting the target basic logic units to each other through different connection methods according to the arrangement order, the process includes: Receive an application deployment request, the application deployment request including: each functional group corresponding to the target application, and the version identifier corresponding to each functional group; Based on the functional groups corresponding to the target application in the application deployment request and the version identifiers corresponding to each functional group, each target functional template matching each functional group is determined from the functional template library, so as to deploy each functional group corresponding to the target application in the application deployment request according to each target functional template.
5. The method of claim 1, wherein, The step of deploying the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template includes: Based on the arrangement order of the basic logic units in the target function template, a number of basic logic units that can be deployed in parallel are determined. When deploying the function group, the number of basic logic units that can be deployed in parallel are deployed in parallel, and the logic units other than the number of basic logic units that can be deployed in parallel are deployed serially according to the arrangement order.
6. The method of claim 1, wherein, The step of deploying the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template includes: Store the functional groups corresponding to the target application into the storage directory corresponding to the target application; Based on the arrangement order of the basic logic units in the target function template, each function group is read from the storage directory corresponding to the target application and deployed.
7. An apparatus for deploying a pipeline, characterized by include: Get module, determine module, generate module, deploy module; The acquisition module is used to acquire each basic logic unit obtained from the static function template; the static function template is an existing function template in which each basic logic unit is connected in a serial manner, and the arrangement of each basic logic unit in the static function template is fixed and singular. The determining module is used to determine the target basic logic unit corresponding to each functional group and the arrangement order of each target basic logic unit from each basic logic unit according to each logical execution node in each functional group corresponding to the target application. The generation module is used to connect each target basic logic unit to each other through different connection methods according to the arrangement order, and generate target function templates corresponding to the function groups. The deployment module is used to deploy the functional groups corresponding to the target application according to the arrangement order of the basic logical units in the target functional template. The determining module is specifically used to determine at least one functional group corresponding to the target application based on each execution node in the execution logic of the target application. Based on the logical execution nodes in each functional group and the version information of each functional group, the target basic logic unit corresponding to each functional group under each version and the arrangement order of each target basic logic unit are determined from each basic logic unit. The basic logic unit is used to execute the steps of the corresponding program; the arrangement order includes serial and parallel.
8. An electronic device, comprising: include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores program instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the program instructions to perform the steps of the pipeline deployment method as described in any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that, The storage medium has stored thereon a computer program, which, when executed by a processor, performs the steps of the pipeline deployment method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Method, system and medium for generating pipeline
CN113127368A
