Method, device and medium for queuing machine resources in pipeline concurrent execution
Through the dynamic management and load balancing strategy of the DevOps continuous integration platform, the problem of limited resources of the builder in the CI pipeline is solved, efficient resource allocation and priority task processing are achieved, and software R&D efficiency and user experience are improved.
Patent Information
- Application Number
- CN202411147278.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-21
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2044-08-21
AI Technical Summary
In the CI pipeline, due to the limited resources of the builder, tasks are waiting, which affects the efficiency of software R&D. The existing resource management methods cannot ensure the timely acquisition of high-priority tasks, resulting in delays in project progress and waste of resources.
Through the dynamic management and load balancing strategy of the DevOps continuous integration platform, the rational allocation and scheduling of builder resources is realized, and the pipeline queuing mechanism and concurrent number configuration items are adopted to ensure that high-priority tasks are given priority to obtain resources, and improve through real-time monitoring and display modules User experience.
It improves the concurrent execution efficiency of construction tasks, optimizes resource utilization, reduces task waiting time and system congestion, ensures timely processing of high-priority tasks, and improves user experience and system performance.
Smart Images

Figure CN118656222B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of software development management, and is mainly used in traditional industries with high business security factors and strict process control, such as banking, insurance, securities and automobile manufacturing, and in particular relates to methods, devices and media for structuring machine resource queuing in concurrent execution of pipelines. Background Art
[0002] In the DevOps software development methodology, one of its core concepts is automation. To achieve engineering automation in the DevOps continuous integration platform, it is necessary to use the CI pipeline to automatically complete a series of highly repetitive and low-value technical actions, such as compilation and construction after the developer submits the code, code scanning, product promotion, unit testing, and deployment and release. The CI pipeline makes the entire software development process as smooth as an industrial assembly line, reducing a large number of manual operations, improving software development efficiency, and reducing the risk of manual errors.
[0003] In the existing CI (continuous integration) pipeline technology architecture, there are some obvious technical problems that need to be solved. One of the main problems is that when a large number of tasks are executed concurrently, due to the limited resources of the build machine, some tasks often have to wait before obtaining idle build machine resources, which greatly reduces the overall execution efficiency and affects the progress of software development.
[0004] In addition, we noticed that most of the existing build machine resource management and scheduling methods use a first-come, first-served model for resource allocation. This approach is indeed simple and convenient to a certain extent, but it obviously cannot guarantee the priority use of resources. In other words, in complex actual operations, it is very likely that important tasks with high priority will be "blocked" by secondary tasks with low priority because they cannot obtain the required build machine resources in time, which will undoubtedly cause delays in project progress and waste of resources.
[0005] Therefore, the technical problem that the present invention needs to solve is how to design an effective strategy and method so that in the process of concurrent execution of tasks in the pipeline, we can reasonably deal with the crowded builder resource problem and create a stable, fair and efficient resource allocation environment to improve the concurrent execution efficiency of build tasks, while optimizing the resource utilization of the build machine, and most importantly, to ensure that high-priority tasks can obtain the necessary resources first. Summary of the invention
[0006] The embodiment of the present application provides a method, device and medium for queuing machine resources based on pipeline concurrent execution to solve the problems existing in the related technology. The technical solution is as follows:
[0007] In a first aspect, an embodiment of the present application provides a method for queuing machine resources based on pipeline concurrent execution, including:
[0008] Step 1 builds the trigger and resource selection method, such as Figure 2 and Figure 3 As shown, the build machines registered and managed by the DevOps continuous integration platform are of various types, such as third-party and public build machines, using different hardware and system environments. This enables the DevOps continuous integration platform to dynamically select suitable build machines according to different task requirements. When a user starts a build task, the pipeline will select a suitable build machine based on the build machine resource type selected by the user. If not specified, the build machine with lower resource usage is selected by default. In addition, the platform implements a load balancing strategy to optimize various factors, such as the current load of the build machine and the number of waiting tasks, to ensure the rational use of build machine resources and improve build efficiency. All processes and the current build machine status will be displayed in real time on the pipeline configuration management page for user monitoring and management;
[0009] In step 2, in the builder scheduling concurrency settings, the DevOps continuous integration platform can add at least one concurrency configuration item for a pipeline according to the configuration instructions and display it on the pipeline configuration management page. Figure 4 As shown, these configuration items include the maximum number of tasks allowed to be executed concurrently in the pipeline. Next, the platform will record and save the concurrency configuration set by the user, and generate at least one target concurrency configuration item to enable the integration of the user-defined concurrency service into the DevOps platform. The platform will then respond to the pipeline running instructions, adopt the pipeline queuing strategy according to the set target concurrency configuration and actual running data, and display the current concurrent execution of pipeline tasks. In other words, the platform will display the concurrency indicator data of the task on the concurrent status operation page based on the target concurrency configuration and execution data. Users can add or modify the concurrency configuration to meet their needs, but they also need to consider the carrying capacity of system resources to prevent excessive concurrency from causing system overload or crash;
[0010] In step 3, the pipeline queuing mechanism, such as Figure 7When the user starts the pipeline instruction, the DevOps continuous integration platform will first check the number of pipelines currently being executed. The startup instruction can be manual, code, or remotely triggered. Next, the platform will evaluate according to the number of pipeline concurrency set by the system. If the number of currently executing pipelines is within the concurrency limit set by the system, the new pipeline task will be added to the execution queue and displayed as "Execute Now". If the number of currently executing pipelines exceeds the concurrency limit set by the system, the new pipeline task will be added to the waiting queue, the status will be marked as "Waiting for Execution" and relevant prompt information will be displayed. When build machine resources are available, the platform will respond to the pipeline scheduling instruction, automatically schedule the pipeline tasks at the front of the waiting queue according to the load balancing strategy, and update its status to "Execute Now". The concurrency limit set by the system can be dynamically adjusted according to resource conditions and user needs, and the load balancing strategy can ensure the rational use of build machine resources and improve build efficiency;
[0011] In step 4 of the present invention, the pipeline execution engine manages various stages and tasks in the pipeline, such as Figure 5 and Figure 6 As shown. Through the DevOps continuous integration platform, the pipeline configuration instructions can be responded to, and the execution order, dependencies and concurrency rules of each stage and task of the pipeline can be automatically defined and recorded. The platform responds to the execution instruction to start the pipeline, and the pipeline execution engine automatically triggers and monitors the execution of each stage and task in the pipeline according to the predefined order, dependency and concurrency rules. In addition, the DevOps continuous integration platform responds to the status check instruction to read and update the task execution status in real time. Once the task fails, the execution engine immediately marks the task status and displays an error prompt. If the task is successful, the execution engine will automatically schedule the next task to be executed. All these operations are displayed in real time on the pipeline operation status page, allowing users to monitor the pipeline operation status, execution progress and view task execution results in real time. The pipeline configuration instructions include commands for adding, deleting, and modifying pipeline tasks and stages. The execution dependencies and execution order between tasks can be customized according to the dependencies between tasks and the execution order set by the user.
[0012] In a second aspect, an embodiment of the present application further provides a device for constructing machine resource queues based on concurrent execution of pipelines, applying a method as in any of the above embodiments, including:
[0013] The pipeline management module is responsible for managing various types of build machines, such as third-party build machines and public build machines, and can dynamically select suitable build machines for build tasks according to different task requirements;
[0014] The response module can respond to the build trigger command initiated by the user and select a build machine that meets the user's needs to perform the corresponding build task. If the user does not specifically select the build machine resource type, the pipeline will default to selecting a build machine with lower resource utilization for the build task;
[0015] The load balancing module implements a load balancing scheduling strategy that can be optimized based on multiple factors such as the load of the current build machine and the number of waiting build tasks, ensuring the rational use of build machine resources and maximizing build efficiency;
[0016] The real-time display module is responsible for displaying the build triggering and resource selection process in real time on the pipeline configuration management page, and displays the current status of the build machine, such as "idle", "busy", "executing", etc., to facilitate real-time monitoring and management by users.
[0017] In addition, the device for constructing a machine resource queue based on pipeline concurrent execution further includes: a memory and a processor. The memory stores instructions, which are loaded and executed by the processor to implement the tasks of any module in the pipeline management module, the response module, the load balancing module, and the real-time display module. The memory and the processor communicate with each other through an internal connection path.
[0018] In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a computer, the method in any one of the above-mentioned embodiments is implemented.
[0019] The advantages or beneficial effects of the above technical solution include at least:
[0020] 1. This application uses the DevOps continuous integration platform to dynamically manage the build machine, which fully improves the efficiency of the build task and the utilization of system resources, and effectively reduces unnecessary waste of resources;
[0021] 2. This application not only uses a load-balancing scheduling strategy to reasonably distribute build tasks among build machines, improving execution efficiency and system performance, but also reduces task waiting time and system congestion;
[0022] 3. This application takes user experience into consideration and introduces a real-time display module. By real-time monitoring and displaying the built information, users can clearly understand the progress of the build and see the usage of system resources at a glance, thereby improving the user experience and reducing the time for problem finding and locating. The above overview is for the purpose of description only and is not intended to be limiting in any way. In addition to the illustrative aspects, implementations, and features described above, further aspects, implementations, and features of the present application will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings required for use in the embodiments will be briefly introduced below. In the accompanying drawings, unless otherwise specified, the same reference numerals throughout multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that the following drawings only illustrate certain embodiments of the present application and are therefore not to be regarded as limiting the scope. For those of ordinary skill in the art, other relevant drawings can also be obtained based on these drawings without paying creative work.
[0024] Figure 1 Build a module composition diagram for the pipeline;
[0025] Figure 2 Trigger phase for build;
[0026] Figure 3 For the Build Machine resource type, select;
[0027] Figure 4 Set up for the system;
[0028] Figure 5 Complex choreography for pipelines;
[0029] Figure 6 Provides basic orchestration for pipelines;
[0030] Figure 7 Waiting pages for the pipeline;
[0031] Figure 8 A schematic diagram of the structure of the device. DETAILED DESCRIPTION
[0032] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.
[0033] The present application discloses a method, device and medium for queuing machine resources based on pipeline concurrent execution. The method flow chart is as follows: Figure 1 As shown, the following steps are included:
[0034] Step 1: Build trigger and resource selection methods;
[0035] First, the DevOps continuous integration platform is responsible for registering and managing various types of build machines, such as third-party build machines and public build machines. These build machines are composed of hardware environments and system environments, and can dynamically select the most suitable build machine to complete tasks according to different task requirements.
[0036] The pipeline will then respond to the build task initiated by the user. By referring to the build machine resource type selected by the user, the pipeline will select the build machine that best suits the user's needs for the corresponding construction task. If the user does not explicitly specify the build machine resource type, the pipeline will default to selecting a build machine with lower resource utilization.
[0037] Secondly, the DevOps continuous integration platform also enables a load-balancing scheduling strategy. This strategy optimizes multiple factors such as the load of the current build machine and the number of pending tasks, ensuring the rational use of build machine resources and optimizing construction efficiency. The build triggering and resource selection process will be displayed in real time on the pipeline configuration management page, along with the current status of the build machine, such as "idle", "busy", and "executing", to facilitate real-time monitoring and management by users.
[0038] Step 2: Build machine scheduling concurrency settings;
[0039] First, the DevOps continuous integration platform responds to the concurrency configuration instruction and displays one or more pipeline concurrency settings added on the pipeline configuration management page. The concurrency items that can be set include the maximum number of tasks that can be executed concurrently in the pipeline.
[0040] Secondly, the DevOps continuous integration platform will respond to the save instruction, record and save the concurrency configuration set by the user, and generate one or more target concurrency configuration items. The configuration items will be based on the user-defined concurrency service and integrated into the DevOps continuous integration platform.
[0041] Next, the DevOps continuous integration platform will respond to the pipeline running instructions and implement the corresponding pipeline queuing strategy based on the target concurrency configuration and actual running data. At the same time, the concurrent execution status of the current pipeline task will be displayed on the pipeline running status page.
[0042] This means that according to the target concurrency configuration and execution data, the concurrency indicator data of the tasks in the pipeline will be displayed on the concurrency status operation page. Users can increase or modify the concurrency as needed. At the same time, the pipeline concurrency configuration should also consider the actual bearing capacity of system resources to avoid excessive concurrency causing system overload or crash.
[0043] Step 3: Pipeline queuing mechanism;
[0044] First, the DevOps continuous integration platform responds to the pipeline start instruction and checks the number of pipelines currently executing before execution begins. The start instruction may come from a variety of methods such as manual triggering, remote triggering, or code triggering.
[0045] Secondly, the platform will make an initial judgment based on the number of concurrent pipelines set by the system. If the number of currently executed pipelines does not exceed the concurrent limit, the new pipeline task will be added to the execution queue and the status will be set to "Immediate Execution".
[0046] Next, if the number of currently executing pipelines exceeds the upper limit of the concurrent number set by the system, the new pipeline task will be added to the waiting queue, the status will be set to "waiting for execution", and a corresponding prompt message will appear, such as "The current pipeline task has exceeded the upper limit and needs to wait in line. There are X pipeline tasks waiting in front of you."
[0047] Finally, when the build machine resources are idle, the DevOps continuous integration platform will respond to the pipeline scheduling instructions, adopt a load balancing strategy to automatically schedule the pipeline tasks at the front of the waiting queue, and update their status to "execute immediately".
[0048] The concurrency limit set by the system can be dynamically adjusted according to the current system resource situation and user needs. The load balancing strategy can ensure that the resources of the build machine are reasonably utilized and can maximize the build efficiency.
[0049] Step 4: Pipeline execution engine;
[0050] First, the pipeline execution engine is used to manage all stages and tasks in the pipeline. By responding to the pipeline configuration instructions of the DevOps continuous integration platform, it automatically defines and records the execution order, dependencies and concurrency rules of each stage and task in the pipeline.
[0051] Next, the execution engine starts the pipeline in response to the execution instruction of the DevOps continuous integration platform. According to the predefined order, dependency and concurrency rules, the pipeline execution engine will automatically trigger and monitor the execution of each stage and task in the pipeline.
[0052] Then, the DevOps continuous integration platform will respond to the status check instruction, read and update the task execution status in real time. If a task fails to execute, the pipeline execution engine will mark the task status in time and give an error prompt. If the task is executed successfully, the execution engine will automatically schedule the next task to be executed.
[0053] Finally, all operations of the pipeline execution engine will be displayed in real time on the pipeline operation status page, so that users can monitor the pipeline operation status and execution progress in real time, and view the task execution results.
[0054] Throughout the process, pipeline configuration instructions include commands to add, delete, and modify pipeline tasks and stages. The execution order and execution dependencies of the pipeline can be customized based on the dependencies between tasks and the execution order set by the user.
[0055] Based on the same inventive concept, an embodiment of the present application further provides a device for constructing machine resource queues based on concurrent execution of pipelines, and the device may include:
[0056] The pipeline management module is responsible for managing various types of build machines, including third-party build machines and public build machines, and dynamically selecting suitable build machines for build tasks based on different task requirements;
[0057] The response module can respond to the build trigger instruction initiated by the user and select the build machine that meets the user's needs to perform the corresponding build task; if the user does not specifically select the build machine resource type, the pipeline will default to selecting a build machine with lower resource utilization for the build task;
[0058] The load balancing module implements a load balancing scheduling strategy that optimizes based on multiple factors, namely the load of the current build machine and the number of waiting build tasks, to ensure the rational use of build machine resources and maximize build efficiency;
[0059] The real-time display module is responsible for displaying the build triggering and resource selection process in real time on the pipeline configuration management page, and displays the current status of the build machine, i.e. "Idle", "Busy", and "Executing", to facilitate real-time monitoring and management by users.
[0060] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and will not be repeated here.
[0061] Based on the same inventive concept, the embodiment of the present application also provides a device for constructing machine resource queues in concurrent execution of pipelines, such as Figure 8 As shown, the device may further include: at least one memory 31 and at least one processor 32. Wherein:
[0062] At least one memory 31 is used to store one or more programs.
[0063] When one or more programs are executed by at least one processor 32, the above Figure 1 The method shown is based on queuing of build machine resources in pipeline concurrent execution.
[0064] The device may also optionally include a communication interface, and the communication interface is used to communicate with external devices and exchange data.
[0065] It should be noted that the memory 31 may include an adjustment RAM memory, and may also include a nonvolatile memory (nonvolatile memory), such as at least one disk memory.
[0066] In the specific implementation process, if the memory 31, the processor 32 and the communication interface are integrated on a chip, the memory 31, the processor 32 and the communication interface can communicate with each other through an internal interface. If the memory 31, the processor 32 and the communication interface are implemented independently, the memory 31, the processor 32 and the communication interface can be connected to each other through a bus and communicate with each other.
[0067] Based on the same inventive concept, the embodiment of the present application further provides a computer-readable storage medium, which can store at least one program. When the at least one program is executed by a processor, the above Figure 1 The method shown is based on queuing of build machine resources in pipeline concurrent execution.
[0068] It should be understood that a computer-readable storage medium is any data storage device that can store data or programs, which can then be read by a computer system. Examples of computer-readable storage media include read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage devices, etc.
[0069] The computer readable storage medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
[0070] The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.
[0071] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A method for queuing machine resources based on pipeline concurrent execution, characterized in that: include: Step 1: Execute build triggering and resource selection. By obtaining data from the DevOps continuous integration platform in response to the build trigger instruction, multiple build machine resources selected according to the build requirements are displayed in the pipeline configuration page. The build triggering instructions include adding new build tasks and modifying the status of existing build tasks; The build machine resources include all build machines that can meet the build requirements in various states; Step 2: Start the builder scheduler, which will respond to the scheduling instructions issued by the DevOps continuous integration platform in a timely manner, bind and schedule the selected builder resources, allocate matching pipeline tasks to the builder, and generate a series of builder call instructions; The scheduling allocation of the builder scheduler includes the following steps: Step 2.1, responding to the concurrency configuration instruction through the DevOps continuous integration platform, wherein the concurrency configuration instruction is to edit the concurrency configuration item of the pipeline builder; displaying at least one added pipeline concurrency configuration item in the pipeline configuration management page, wherein the concurrency configuration item includes the maximum number of tasks allowed to be executed concurrently in the pipeline; Step 2.2, responding to the save instruction through the DevOps continuous integration platform, wherein the save instruction is to record and save the concurrency configuration set by the user, and generate at least one target concurrency configuration item; the configuration item is integrated into the DevOps continuous integration platform based on the user-defined concurrency service; Step 2.3, respond to the pipeline operation instruction through the DevOps continuous integration platform, and adopt the corresponding pipeline queuing strategy according to the set target concurrency configuration and actual operation data; The concurrent execution status of the tasks in the current pipeline is displayed on the pipeline operation status page; based on the target concurrency configuration and the actual operation data, the concurrency index data of the tasks in the pipeline is displayed on the concurrent status operation page; The actual operation data includes execution status, task queue information, and resource occupancy; The configuration instructions include adding and modifying the number of concurrent calls, and users can set them accordingly according to their needs. At the same time, the configuration of the number of concurrent calls of the pipeline should also take into account the actual bearing capacity of system resources to prevent excessive concurrency from causing system overload or crash. Step 3: Implement the pipeline queuing rules. The DevOps continuous integration platform will plan the queues for pipeline tasks according to the preset rules in the pipeline configuration page, and can generate pipeline task queues that meet concurrency requirements and maximize resource utilization. The preset rules in the pipeline configuration page include pipeline priority, concurrency number, and pipeline variables; The implementation of pipeline queuing disciplines includes: Step 3.1, responding to the pipeline start instruction through the DevOps continuous integration platform, checking the number of pipelines currently being executed before execution; the start instruction includes manual triggering, remote triggering, code triggering, and timed triggering; Step 3.2, perform the first round of judgment according to the concurrent number of pipelines set by the system; if the number of currently executed pipelines does not exceed the concurrent upper limit set by the system, the new pipeline task will be added to the execution queue, and the status will be displayed as "Immediate Execution"; if the number of currently executed pipelines exceeds the concurrent upper limit set by the system, the new pipeline task will be added to the waiting queue, and the status will be displayed as "Waiting for Execution", and a prompt message will be given, that is, "The current pipeline has exceeded the upper limit, you need to wait in line, and there are X pipelines waiting in front of you"; Step 3.3, when there are idle resources on the build machine, the DevOps continuous integration platform responds to the pipeline scheduling instruction, automatically schedules the pipeline task at the front of the waiting queue using the load balancing strategy, and updates the status of the pipeline task to "execute immediately"; The concurrency limit set by the system can be dynamically adjusted according to the current resource status of the system and the needs of users; at the same time, the load balancing strategy can ensure the rational use of the build machine resources; Step 4: Drive the pipeline execution engine, which responds to the running instructions issued by the DevOps continuous integration platform, receives the data required to execute the task, and then arranges the task execution according to the pipeline task queue corresponding to the builder resource; and dynamically displays the running status of each builder resource and the task execution progress in the execution status operation page according to the actual running data; The driving pipeline execution engine comprises: Step 4.1, the pipeline execution engine is responsible for managing each stage and task in the pipeline, responding to the pipeline configuration instructions through the DevOps continuous integration platform, and automatically defining and recording the execution order, dependencies and concurrency rules of each stage and task in the pipeline; Step 4.2, starting the pipeline in response to the execution instruction through the DevOps continuous integration platform; the pipeline execution engine automatically triggers and monitors the execution of each stage and task in the pipeline according to the predefined execution order, dependency and concurrency rules; Step 4.3, responding to the status check instruction through the DevOps continuous integration platform, reading and updating the task execution status in real time; if a task fails to execute, the pipeline execution engine will promptly mark the status of the task and give an error prompt; if the task is executed successfully, the execution engine will automatically schedule the next task to be executed; Step 4.4, all operations of the pipeline execution engine are displayed in real time on the pipeline operation status page, and the user monitors the operation status and execution progress of the pipeline, and views the task execution results; The pipeline configuration instructions include instructions for adding, deleting, and modifying pipeline tasks and stages. The execution dependencies and execution order of the pipeline are custom configured based on the dependencies between tasks and the execution order set by the user.
2. The method for queuing machine resources based on pipeline concurrent execution according to claim 1, characterized in that: The methods for constructing triggers and resource selection are: First, the DevOps continuous integration platform registers and manages multiple types of build machines, including third-party build machines and public build machines. The build machines are composed of hardware environment and system environment, and dynamically select suitable build machines for build tasks according to different task requirements. Secondly, the pipeline responds to the build trigger instruction initiated by the user, and selects a build machine that meets the user's needs to perform the corresponding build task according to the build machine resource type selected by the user; if the user does not explicitly select the build machine resource type, the pipeline will default to selecting a build machine with lower resource utilization for the build task; At the same time, the DevOps continuous integration platform also implements a load-balancing scheduling strategy, which optimizes according to multiple factors, namely the load of the current build machine and the number of waiting build tasks, to ensure the rational use of build machine resources; the build triggering and resource selection process is displayed in real time in the pipeline configuration management page, and the current status of the build machine, namely "idle", "busy", and "executing", is displayed, which is convenient for users to monitor and manage in real time.
3. A device for constructing machine resource queues based on pipeline concurrent execution, applying the method according to any one of claims 1 to 2, characterized in that: include: The pipeline management module is responsible for managing various types of build machines, including third-party build machines and public build machines, and dynamically selecting suitable build machines for build tasks based on different task requirements; The response module can respond to the build trigger instruction initiated by the user and select the build machine that meets the user's needs to perform the corresponding build task; if the user does not specifically select the build machine resource type, the pipeline will default to selecting a build machine with lower resource utilization for the build task; The load balancing module implements a load balancing scheduling strategy that optimizes based on multiple factors, namely the load of the current build machine and the number of waiting build tasks, to ensure the rational use of build machine resources; The real-time display module is responsible for displaying the build triggering and resource selection process in real time on the pipeline configuration management page, and displays the current status of the build machine, namely "idle", "busy", and "executing", to facilitate real-time monitoring and management by users.
4. The device for constructing machine resource queues based on pipeline concurrent execution according to claim 3, characterized in that: Also includes: A memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement the tasks of any module among the pipeline management module, the response module, the load balancing module and the real-time display module; wherein the memory and the processor communicate with each other through an internal connection path.
5. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program; when the at least one program is executed by a processor, the method according to any one of claims 1 to 2 is implemented.
