Containerization transformation method and system based on Windows test construction tool and storage medium

Abstract

The invention belongs to the technical field of software development, and relates to a containerization transformation method and system based on a Windows test construction tool and a storage medium, and the method comprises the following steps: creating a basic mirror image: taking Windows server core: ltsc2019 as a bottom layer operation system, and constructing a basic environment for container operation; configuring a deployment key: configuring the deployment key corresponding to the code warehouse of the application platform, and establishing a secure connection channel between the container and the code warehouse; installing a registration service: installing the registration service for pulling a devops project from an application platform code warehouse, and synchronizing a project code to a local disk of the container through the service; installing a tool assembly: installing a compiling construction tool, a test tool and an Agent interaction service in sequence in the container environment of the acquired project resources; setting continuous command output: calling a ping command in Windows in an ENTRYPOINT command of the Docker, and keeping the container in a continuous running state; and constructing a mirror image, namely packaging the whole container environment into a reusable mirror image instance by using a docker build-t image: tag command of the Docker.

Description

Technical Field

[0001] This invention belongs to the field of software development technology and relates to a containerization transformation method, system and storage medium based on Windows test build tools. Background Technology

[0002] In software development, different projects often rely on specific versions of Integrated Development Environments (IDEs). Taking Visual Studio as an example, versions such as VS2010, 2015, and 2022 differ significantly in compiler features, dependency library versions, and project formats. In traditional development models, deploying multiple IDE versions faces the following problems: (1) Severe environmental conflicts: When multiple versions of VS are installed on the same physical machine or virtual machine, the environment is prone to crash due to conflicts in system variables, registry configurations, and dependent components. In particular, in Windows systems, the compatibility issues between different versions of .NET Framework and MSBuild toolchain are prominent.

[0003] (2) Low build efficiency: The lack of an automated scheduling mechanism means that multiple versions of projects need to manually switch environments or rely on dedicated personnel to maintain multiple physical environments. The lack of parallel build capability leads to the continuous integration process being stuck.

[0004] (3) Poor configuration consistency: Manually configured environment parameters (such as MSBuild path and compilation options) are prone to deviation and are difficult to synchronize to all nodes of the team, increasing the risk of project compilation failure.

[0005] (4) Low resource utilization: Allocation of server resources for a single version of the IDE leads to idle hardware resources, especially in periodic build scenarios, where resource waste is significant.

[0006] While existing containerization technologies can achieve environment isolation, there are still gaps in the technology for specific adaptations to multiple versions of Visual Studio (such as Windows dependency injection and MSBuild dynamic invocation), and a complete solution is urgently needed. Summary of the Invention

[0007] The technical problem solved by this invention: Based on the problems mentioned in the background art, this invention provides a containerization transformation method, system, and approach based on Windows test build tools. Implementers can pull images to the container runtime environment on the application platform according to actual scenarios. Through the application platform's resource pool management, container resources are registered with the application platform. Users can schedule tasks by selecting a resource pool. At the underlying application platform, a load balancing algorithm selects an available execution machine container to run the task. The compilation, build, and test images all have a unified registration service. This registration service reports local environment data to the application platform, including CPU, memory, and disk data. These containerized tools effectively solve the bottleneck problems of ordinary tools by amplifying execution machine resources through horizontal scaling, rather than relying on virtual machine resources for expansion.

[0008] Technical solution of the present invention A containerization method based on Windows test build tools includes the following steps: (1) Create a base image: Use Windows Server Core: LTSC 2019 as the underlying operating system to build the basic environment for container operation; (2) Configure deployment key: In the base image environment created in step (1), configure the deployment key corresponding to the application platform code repository to establish a secure connection channel between the container and the code repository; (3) Install the registration service: Based on the key connection configured in step (2), install the registration service used to pull DevOps projects from the application platform code repository, and use this service to synchronize the project code to the container's local disk; (4) Install tool components: In the container environment where the project resources have been acquired in step (3), install three types of tools in sequence: compilation and build tools, testing tools, and Agent interaction service; (5) Set up continuous command output: After the tool components are installed in step (4), call the Windows internal ping command in the Docker ENTRYPOINT command to keep the container running continuously; (6) Build the image: After completing steps (1) to (5), use Docker's docker build -t image:tag command to package the entire container environment into a reusable image instance.

[0009] Furthermore, in step (3), the registration service includes communication with the application platform and transmitting information inside the container to the application platform.

[0010] Furthermore, in step (4), the compilation and build tool is based on the embedded software environment, which allows users to execute compilation instructions inside the container in a container-running manner, compiling the software source code into a runnable executable program; the compilation and build tool realizes the compilation and build operation based on the DevOps project resources pulled in the installation and registration service step, with the help of the underlying environment provided by the base image created in the base image creation step.

[0011] Furthermore, in step (4), the Agent interaction service communicates with the application platform via the network and interacts with the testing tools via the network. The Agent interaction service includes an interface for receiving test cases, running test suites, pulling tool repositories, status feedback, report parsing, heartbeat, stop, and cleanup. The Agent interaction service is installed in the tool component installation step. Its network communication with the application platform depends on the secure connection built by the deployment key configured in the deployment key configuration step. Its interaction with various testing sub-tools is based on the testing tools installed in the tool component installation step. The continuous command output settings ensure that the Agent interaction service runs continuously and stably.

[0012] Furthermore, in step (4), the testing tools include unit testing sub-tools, configuration item testing sub-tools, and control law independent testing sub-tools. The test interactions of various types of testing sub-tools are managed by the Agent interaction service. Each type of testing sub-tool is distributed and executed through the factory pattern + strategy pattern in the Agent. The various interfaces provided by the Agent interaction service support the interaction of testing tools and the distribution and execution of testing tasks, while the project resources obtained in the installation and registration service steps provide test objects for various testing sub-tools to carry out testing.

[0013] A system applied to the method, the system architecture comprising: Application platform: The application platform plays a scheduling role, used to select appropriate container resources; Application layer: Used to receive the source code executed by the test component tool, receive the image execution parameters, output the results, and interact with the application platform; Business function layer: Containerization transformation for testing build tools; Data persistence layer: Used for outputting logs and results during container operation.

[0014] Furthermore, the business function layer includes: Base image creation module: Used to build the basic environment for container operation using Windows Server Core: LTSC 2019 as the underlying operating system; Deployment key configuration module: Used to configure the deployment key corresponding to the application platform code repository in the base image environment created by the base image creation module, thereby establishing a secure connection channel between the container and the code repository; Registration service installation module: Used to install a registration service for pulling DevOps projects from the application platform code repository based on the key connection configured in the deployment key configuration module, and to synchronize the project code to the container's local disk through this service; Tool component installation module: Used to install the compilation and build tools, testing tools, and Agent interaction service sequentially in the container environment where the registration service installation module has acquired project resources; Continuous command output setting module: After the tool component is installed, it calls the Windows internal ping command in the Docker ENTRYPOINT command to keep the container running continuously. Image build module: Used with Docker's docker build -t image:tag command to package the entire container environment into a reusable image instance.

[0015] A computer storage medium having computer-executable instructions stored thereon, which, when executed by a processor, implement the method described thereon.

[0016] Beneficial effects This invention provides a containerization transformation method, system, and storage medium based on Windows test build tools. It is a tool containerization solution based on Windows Docker. By encapsulating various versions of IDEs and related tools into independent image instances, multiple isolated container environments can be quickly created on a single execution machine. This achieves environmental consistency throughout the entire process of compilation, unit testing, and configuration item testing, while breaking through the limitations of single-task execution on a single execution machine. By leveraging container parallel scheduling, it improves resource utilization, thereby filling the gap in existing containerization technologies for adapting to multiple versions of VS on the Windows platform and providing complete support for the efficient collaborative deployment of multiple versions of IDEs.

[0017] It has the following advantages: (1) The image can run on Windows Server 2016+ servers. You can use it by simply pulling the image.

[0018] (2) Containers can be started according to actual needs, which can improve the concurrency of the operating environment.

[0019] (3) The actual functions inside the image can be adjusted as needed to achieve scalability.

[0020] In summary, the containerization transformation method, system, and storage medium based on Windows test build tools proposed in this invention have good high concurrency and convenience, and have broad application prospects. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the system architecture for containerization. Figure 2 This is a flowchart of the containerized scheduling process; Figure 3 This is a diagram illustrating the relationship between technical points and software. Figure 4 This is a flowchart of the application platform's task scheduling process. Detailed Implementation

[0022] The features and illustrative embodiments of various aspects of the present invention will now be described in detail. Numerous specific details are set forth in the following detailed description to provide a thorough understanding of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without requiring some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the invention by illustrating examples of the invention. The invention is by no means limited to any specific setups and methods set forth below, but covers any improvements, substitutions, and modifications to structures, methods, and devices without departing from the spirit of the invention. Well-known structures and techniques are not shown in the drawings and the following description to avoid unnecessarily obscuring the invention.

[0023] It should be noted that, unless otherwise specified, the embodiments of the present invention and the features thereof can be combined with each other, and the various embodiments can be referenced and cited in each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] One embodiment of the present invention provides a containerization transformation method for Windows test build tools. This method achieves containerized deployment of the tool through a progressive series of steps, with each step tightly connected and logically clear. The details are as follows: (1) Create a base image: use Windows Server Core: LTSC 2019 as the underlying operating system to build the basic environment for container operation, providing stable underlying support for the deployment of all subsequent tools and services.

[0025] (2) Configure deployment key: In the base image environment created in step (1), configure the deployment key corresponding to the application platform code repository to establish a secure connection channel between the container and the code repository. This is a prerequisite for successfully pulling project code in the future.

[0026] (3) Install the registration service: Based on the key connection configured in step (2), install the registration service for pulling DevOps projects from the application platform code repository. Through this service, the project code is synchronized to the container's local disk, providing the necessary project resources for the subsequent operation of the tools.

[0027] (4) Install tool components: In the container environment where the project resources have been acquired in step (3), install three types of core tools in sequence: the compilation and build tool is responsible for the compilation and build process of the project, the test tool is used to execute various test tasks, and the Agent interaction service serves as the core interaction hub, including functions such as receiving test cases, running test suites, pulling tool repositories, status feedback interface, report parsing interface, heartbeat interface, stop interface, and cleanup interface, to realize the full-process interaction between the container and the external platform.

[0028] (5) Set continuous command output: After the tool components are installed in step (4), the container will be automatically destroyed if the ENTRYPOINT command does not have continuous output after it starts. Therefore, the ping command inside Windows is called in the ENTRYPOINT command to keep the container running continuously and ensure that the installed tools and services can play a stable role.

[0029] (6) Build the image: After completing all the configurations and deployments in steps (1) to (5), use Docker's dockerbuild -t image:tag command to package the entire container environment into a reusable image instance, providing a basic template for creating multiple identical container environments in the future.

[0030] A second embodiment of the present invention provides a system applied to the method, the system architecture of which is described below. Figure 1 ,include: (1) Application platform: The application platform plays a scheduling role and is used to select appropriate container resources; (2) Application layer: used to receive the source code of the test component tool, receive the image execution parameters, output the results, and interact with the application platform; (3) Business Function Layer: Used for containerization of test build tools; (4) Data persistence layer: used for outputting logs and results during container operation.

[0031] The aforementioned business function layer includes: (3.1) Base image creation module: used to build the basic environment for container operation using Windows Server Core: LTSC 2019 as the underlying operating system; (3.2) Deployment key configuration module: used to configure the deployment key corresponding to the application platform code repository in the base image environment created by the base image creation module, thereby establishing a secure connection channel between the container and the code repository; (3.3) Registration service installation module: It is used to install the registration service for pulling DevOps projects from the application platform code repository based on the key connection configured in the deployment key configuration module, and to synchronize the project code to the container local disk through the service; The registration service includes communication with the application platform and transmitting information such as the container's CPU, disk, and memory to the application platform. This registration service is installed during the installation process. Its communication with the application platform relies on the secure connection channel established by the deployment key configured in the deployment key configuration step. Simultaneously, the base image created in the base image creation step provides a stable environment for the registration service, ensuring its continuous and accurate transmission of container information to the application platform.

[0032] (3.4) Tool component installation module: Used to install the compilation and build tools, testing tools and Agent interaction service in sequence in the container environment where the registration service installation module has obtained project resources; The compilation and build tool is based on an embedded software environment, allowing users to execute compilation instructions within a container to compile software source code into executable programs such as *.bin / .elf / .exe. This functionality relies on the compilation and build tool installed during the installation of the tool components. This tool, based on the DevOps project resources retrieved during the installation and registration service steps, leverages the underlying environment provided by the base image created during the base image creation step to achieve efficient compilation and build operations.

[0033] The testing tools encompass various sub-tools, including unit tests, configuration item tests, and independent control law tests. The interaction between these sub-tools is managed by the Agent application, with each type of testing tool distributed and executed via a factory pattern combined with a strategy pattern within the Agent. The testing tools and Agent interaction service, installed via the installation tool component steps, provide crucial support for the interaction of testing tools and the distribution and execution of test tasks. Meanwhile, the project resources acquired during the installation and registration service steps provide the necessary test objects for various types of tests.

[0034] The Agent service interacts with the application platform via network communication and with various testing tools via network communication. This includes interfaces for receiving test cases, running test suites, pulling tool repositories, providing status feedback, parsing reports, performing heartbeats, stopping, and cleaning up. The service is installed during the tool installation step. Its network communication with the application platform relies on a secure connection established by the deployment key configured in the deployment key configuration step. Its interaction with various testing tools is based on the testing tools installed during the tool installation step. The continuous command output configured in the continuous command output setting step ensures the Agent service runs continuously and stably, thus enabling uninterrupted interaction.

[0035] (3.5) Continuous command output setting module: After the tool components are installed, the Windows internal ping instruction is called in the Docker ENTRYPOINT command to keep the container running continuously; (3.6) Image building module: Used to package the entire container environment into a reusable image instance using Docker's docker build -t image:tag command.

[0036] In this embodiment, there are some basic application instructions during the image building process, including source, copy, environment variables, workspace, etc.

[0037] FROM: The FROM instruction is used to set the container image to be used during the new image creation process. For example, using the instruction FROM mcr.microsoft.com / windows / servercore results in an image derived from and dependent on the Windows Server Core base operating system image. If the specified image does not exist on the system where the Docker build process is underway, the Docker engine will attempt to download it from a public or private image registry.

[0038] RUN: The RUN instruction specifies the commands to be run and captured in the new container image. These commands include installing software, creating files and directories, and creating environment configurations.

[0039] COPY: The COPY instruction copies files and directories to the container's file system. Files and directories must be located relative to the paths specified in the Dockerfile.

[0040] ADD: The ADD directive is similar to the COPY directive but includes more functionality. In addition to copying files from the host to the container image, the ADD directive can also copy files from remote locations using URL specifications.

[0041] WROKDIR: The WORKDIR instruction is used to set a working directory for other Dockerfile instructions (such as RUN, CMD), and also to set the working directory used to run container image instances.

[0042] CMD: The CMD instruction is used to set the default command to run when an instance of a container image is deployed. For example, if the container will host an NGINX web server, CMD might include instructions that work with commands like nginx.exe to start the web server. If multiple CMD instructions are specified in the Dockerfile, only the last one is evaluated.

[0043] During container scheduling, the application platform typically selects available execution machine resources, and the load balancing algorithm within the application platform then schedules the task to an available container. The container scheduling flowchart is shown in Figure 2.

[0044] The third embodiment of the present invention provides a process for performing code compilation, building, and test case tasks in an application platform based on a containerized tool.

[0045] (1) Task submission and identification: After the user submits a task containing code compilation and building and test case testing to the application platform, the application platform’s identification of task requirements depends on the receiving function of the Agent interaction service deployed in the step of installing tool components in the containerization transformation. The Agent service can accurately parse the compilation and building environment, testing environment and specific dependencies required by the task, which is the starting point of the whole process. (2) Resource pool management: The container resource pool managed by the application platform is built through a series of containerization transformation steps. Among them, the step of creating a base image provides a stable underlying operating system environment for the containers in the resource pool, and the reusable image instance generated by the image building step is the basic template for the containers in the resource pool, enabling the resource pool to efficiently manage container resources that support different tasks.

[0046] (3) Task scheduling: The application platform scheduler selects suitable container resources based on the load balancing algorithm. These schedulable containers can run stably and have the ability to undertake tasks, which is inseparable from the guarantee of setting up a continuous command output step. This step ensures that the container runs continuously and provides usable container instances for task scheduling. At the same time, the information such as container CPU, disk, and memory transmitted by the service deployed in the registration service step to the application platform also provides data support for the scheduler to judge the container load. (4) Containerization tool preparation: When the application platform pulls or creates container instances from the resource pool according to task requirements, the base image on which these instances are based (such as Windows ServerCore) is the result of the base image creation step, while the pre-configured compilation and building tools, testing tools and related services in the instance are the product of the tool component installation step. The rapid preparation of container instances depends on the standardized environment created by each step of containerization transformation. (5) Code compilation and building: After the code is pushed to the container instance, the compilation and building tool in the container performs the compilation operation. This tool comes from the installation tool component step. The source code required for compilation is the DevOps project resources pulled by the installation registration service step through the secure connection established by the configuration deployment key step. The compilation process relies on the underlying environment provided by the creation base image step to proceed stably. (6) Test Case Testing: After compilation, the test tools in the container execute various tests. The test tools come from the installation tool component step, and the test process is managed by the Agent service deployed in this step. The Agent service uses its included functions such as running test suites and receiving test cases to achieve the orderly execution of unit tests, configuration item tests, etc. The test object is the project resources synchronized to the container by the installation and registration service step. (7) Results collection and feedback: After the test is completed, the Agent service collects the results and feeds them back to the application platform. This relies on its report parsing interface, status feedback interface and other functions. These functions are provided in the tool component installation step to ensure that the test results can be smoothly transmitted back to the application platform. (8) Resource recycling and release: The cleanup of container instances after the task is completed is achieved by the cleanup interface, stop interface and other functions of the Agent service deployed in the installation tool component steps. By deleting temporary files and clearing container status, resources are released for use by other tasks, ensuring the efficient circulation of the resource pool.

[0047] See the full process diagram. Figure 4 .

[0048] A fourth embodiment of the present invention provides a computer storage medium having computer-executable instructions stored thereon, which, when executed by a processor, implement the method described thereon.

[0049] The following technical points are utilized in this invention: (1) Docker container technology: Docker, as an open-source application container engine, is integrated throughout the entire containerization process. The creation of the base image, using Windows Server Core:ltsc2019 as the underlying operating system to build the basic environment, relies on Docker's containerization capabilities. The image building step, using the `docker build -t image:tag` command to package the container environment, is also a direct application of Docker technology. These operations achieve tool containerization, laying the foundation for concurrent operation of multiple environments and efficient resource utilization.

[0050] (2) Continuous Integration / Continuous Deployment (CI / CD): The automation concept of CI / CD is reflected in the tool component installation step. The compilation and testing tools installed in this step provide tool support for the subsequent automation of compilation, building and testing through the CI / CD process, enabling code changes to be quickly integrated and problems to be discovered through automated testing, thereby improving development efficiency and software quality.

[0051] (3) Load balancing technology: Although load balancing technology mainly plays a role in the application platform's selection of execution machine containers to run tasks, the image building step generates reusable image instances, which provides a basis for creating multiple identical container environments. The existence of multiple container environments is a prerequisite for the application platform to perform load balancing distribution, ensuring efficient resource allocation and stable task execution.

[0052] (4) Microservice architecture: The independent yet interactive nature of services in a microservice architecture is evident in the installation and registration service and installation tool component steps. The registration service deployed in the installation and registration service step, and the Agent service deployed in the installation tool component step, operate independently yet cooperate with each other. The Agent service communicates upwards with the application platform and interacts downwards with the testing tools, while the registration service is responsible for communicating with the application platform and transmitting container information. This demonstrates the advantages of a microservice architecture, improving system maintainability and scalability.

[0053] (5) Container monitoring technology: Container monitoring technology provides assurance for the entire container operation process. By setting up continuous command output, the container is kept running continuously, which facilitates the collection and analysis of runtime data by container monitoring technology. At the same time, the information on the container's internal CPU, disk, and memory transmitted by the registration service also provides data support for container monitoring, which helps to discover and solve problems in a timely manner and ensure service continuity and reliability.

[0054] (6) Cloud-native technologies: The elasticity and scalability of cloud-native technologies are relied upon in the creation and building of base images. The stable underlying environment built by the base image and the reusable image instances generated by the build image enable containerization tools to better adapt to cloud-native environments, facilitate deployment on cloud platforms, fully utilize cloud platform resources and services, and improve development and operational efficiency.

[0055] (7) Safety reinforcement technology: Security hardening technology is applied in the deployment key configuration step, which establishes a secure connection channel between the container and the code repository, ensuring the security of the project code retrieval process. At the same time, throughout the containerization process, security hardening technology is also reflected in the security scanning of container images, ensuring the overall security of the container.

[0056] A diagram illustrating the relationship between technical points and software is available. Figure 3 .

[0057] In summary, this invention provides a containerization transformation method, system, and storage medium based on Windows test build tools. It is a containerization solution for tools based on Windows Docker. By encapsulating various versions of IDEs and related tools into independent image instances, multiple isolated container environments can be quickly created on a single execution machine. This achieves environmental consistency throughout the entire process of compilation, unit testing, and configuration item testing, while breaking through the limitations of single-task execution on a single execution machine. By leveraging container parallel scheduling, it improves resource utilization, thereby filling the gap in existing containerization technologies for adapting to multiple versions of VS on the Windows platform and providing complete support for the efficient collaborative deployment of multiple versions of IDEs.

[0058] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should be covered within the protection scope of the present invention.

Claims

1. A containerization transformation method based on Windows test build tools, characterized in that, Includes the following steps: (1) Create a base image: Use Windows Server Core: LTSC 2019 as the underlying operating system to build the basic environment for container operation; (2) Configure deployment key: In the base image environment created in step (1), configure the deployment key corresponding to the application platform code repository to establish a secure connection channel between the container and the code repository; (3) Install the registration service: Based on the key connection configured in step (2), install the registration service used to pull DevOps projects from the application platform code repository, and use this service to synchronize the project code to the container's local disk; (4) Install tool components: In the container environment where the project resources have been acquired in step (3), install three types of tools in sequence: compilation and build tools, testing tools, and Agent interaction service; (5) Set up continuous command output: After the tool components are installed in step (4), call the Windows internal ping command in the Docker ENTRYPOINT command to keep the container running continuously; (6) Build the image: After completing steps (1) to (5), use Docker's docker build -t image:tag command to package the entire container environment into a reusable image instance.

2. The containerization transformation method based on Windows test build tools according to claim 1, characterized in that, In step (3), the registration service includes communication with the application platform and passing information inside the container to the application platform.

3. The containerization transformation method based on Windows test build tools according to claim 2, characterized in that, In step (4), the compilation and build tool is based on the embedded software environment and allows users to execute compilation instructions inside the container in a container-running manner to compile the software source code into a runnable executable program. The compilation and build tools utilize the underlying environment provided by the base image created in the base image creation step, based on the DevOps project resources pulled during the installation and registration service steps.

4. The containerization transformation method based on Windows test build tools according to claim 3, characterized in that, In step (4), the Agent interaction service communicates with the application platform via the network and interacts with the testing tools via the network. The Agent interaction service includes interfaces for receiving test cases, running test suites, pulling tool repositories, status feedback, report parsing, heartbeat, stop, and cleanup. The Agent interaction service is installed in the tool component installation step. Its network communication with the application platform relies on the secure connection built by the deployment key configured in the deployment key configuration step. Its interaction with various testing sub-tools is based on the testing tools installed in the tool component installation step. The continuous command output settings ensure that the Agent interaction service runs continuously and stably.

5. The containerization transformation method based on Windows test build tools according to claim 4, characterized in that, In step (4), the testing tools include unit testing sub-tools, configuration item testing sub-tools and control law independent testing sub-tools. The test interactions of various types of testing sub-tools are managed by the Agent interaction service. Each type of testing sub-tool is distributed and executed through the factory pattern + strategy pattern in the Agent. The various interfaces provided by the Agent interaction service support the interaction of testing tools and the distribution and execution of testing tasks, while the project resources obtained in the installation and registration service steps provide test objects for various testing sub-tools to carry out testing.

6. A system applied to the method of claim 5, characterized in that, The system architecture includes: Application platform: The application platform plays a scheduling role, used to select appropriate container resources; Application layer: Used to receive the source code executed by the test component tool, receive the image execution parameters, output the results, and interact with the application platform; Business function layer: Containerization transformation for testing build tools; Data persistence layer: Used for outputting logs and results during container operation.

7. The system according to claim 6, characterized in that, The aforementioned business function layer includes: Base image creation module: Used to build the basic environment for container operation using Windows Server Core: LTSC 2019 as the underlying operating system; Deployment key configuration module: Used to configure the deployment key corresponding to the application platform code repository in the base image environment created by the base image creation module, thereby establishing a secure connection channel between the container and the code repository; Registration service installation module: Used to install a registration service for pulling DevOps projects from the application platform code repository based on the key connection configured in the deployment key configuration module, and to synchronize the project code to the container's local disk through this service; Tool component installation module: Used to install the compilation and build tools, testing tools, and Agent interaction service sequentially in the container environment where the registration service installation module has acquired project resources; Continuous command output setting module: After the tool component is installed, it calls the Windows internal ping command in the Docker ENTRYPOINT command to keep the container running continuously. Image build module: Used with Docker's docker build -t image:tag command to package the entire container environment into a reusable image instance.

8. A computer storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the method of any one of claims 1-5.

Images