Continuous integration system and method for domestic platform

Abstract

The invention relates to a domestic platform-oriented continuous integration system and method, and belongs to the technical field of software engineering. The system comprises a code management module, a continuous integration assembly line service engine, a code security enhancement module, an automatic test tool set, a remote compiling construction module and a product management module. According to the method, on the basis of domestic platform development, all tools and plug-ins are adapted to the domestic platform, so that the software development efficiency under the domestic platform can be improved; the waste of development cost and time caused by the fact that products are generated by an existing continuous integration system and then localized system migration adaptation is carried out is avoided; the code security is enhanced; according to the method, foreign continuous integration tools are replaced, dependence on external technologies is reduced, the requirement for continuous integration of domestic platform software development can be met, and national information security can be guaranteed.

Description

Technical Field

[0001] This invention belongs to the field of software engineering technology, specifically relating to a continuous integration system and method for domestically developed platforms. Background Technology

[0002] With the rapid development of software engineering technology, the development and iteration speed of software products is accelerating, and traditional software development models can no longer meet the demands for high-quality, rapid delivery of software products. Continuous Integration (CI), as an effective modern software development practice, is being widely accepted and implemented by software developers. Continuous Integration systems require software developers to frequently integrate code into the codebase and verify the correctness of the code through automated compilation, building, and testing, thereby improving software quality and development efficiency while reducing software development costs and risks.

[0003] As software development scenarios on domestically developed platforms become increasingly common, the demand for continuous integration systems (CIS) tailored to these platforms is growing. Currently, most CIS systems used in software development are based on foreign technologies and tools, such as Jenkins and Travis CI, which present compatibility issues on domestic platforms and pose risks of insufficient code security. Summary of the Invention

[0004] (a) Technical problems to be solved The technical problem to be solved by this invention is how to provide a continuous integration system and method for domestic platforms, so as to solve the problems of compatibility and platform migration adaptation of existing continuous integration systems for domestic platforms.

[0005] (II) Technical Solution To address the aforementioned technical issues, this invention proposes a continuous integration system for domestically developed platforms. This system includes: a code management module, a continuous integration pipeline service engine, a code security enhancement module, an automated testing toolset, a remote compilation and build module, and an artifact management module. The code management module is used to manage and store source code during the development process and is the source of continuous integration; The continuous integration pipeline service engine includes three sub-modules: pipeline orchestration, pipeline scheduling, and pipeline execution and monitoring. It is used for pipeline orchestration, scheduling, execution, and monitoring, and is responsible for managing continuous integration tasks and supporting the integration of other tools. The code security enhancement module includes three sub-modules: code security detection, code tracing, and code obfuscation. These modules are used to protect the security of code and software during development and testing, and to increase the difficulty of reverse engineering the code. An automated testing toolset includes: unit testing tools, integration testing tools, functional testing tools, and performance testing tools. Tools are selected as task nodes in the pipeline orchestration to perform automated code testing. The remote compilation and build module includes two sub-modules: a secure container and a dependency management module. It is used to compile and build code on mainstream domestic platforms, improve compilation and build efficiency, and effectively manage the dependency libraries used by the code. The artifact management module is used to manage binary artifacts generated by the continuous integration pipeline, and supports artifact classification, search, and version management.

[0006] This invention also provides a continuous integration method for domestically developed platforms, the method comprising the following steps: S1. Software developers write code in the integrated development environment of the development machine, submit the code to the code management module, store it in the code repository, and manage the code in the code management module; S2. Software developers perform pipeline orchestration in the continuous integration pipeline orchestration module. After the software developers submit the code to the code repository, the associated pipeline is automatically triggered, pipeline tasks are generated, the continuous integration pipeline service engine pulls the code, and performs code inspection, compilation, building and testing based on the pipeline orchestration information. S3. If the code fails the inspection, it will be reported to the software developers for modification; if it passes, the source code will be obfuscated and remote compilation and build will be performed; the remote compilation and build module will compile and build on mainstream domestic platforms based on secure containers to generate artifacts that can run on the corresponding domestic platforms; S4. After completing the remote compilation and build, select the appropriate tool from the automated testing toolset to perform automated testing; S5. If the test fails, feedback will be given to the software developers for modification; if the test passes, the artifact will be uploaded to the artifact management module for management.

[0007] (III) Beneficial Effects This invention proposes a continuous integration system and method for domestically developed platforms, possessing continuous integration capabilities for software development on domestically developed platforms. This invention has the following technical advantages: (1) For domestic platforms To address the compatibility issues of existing continuous integration systems (CIS) on domestic platforms, this invention proposes a CIS system developed specifically for domestic platforms. All tools and plugins in existing CIS systems are adapted for domestic platforms, thus improving the efficiency of software development on these platforms.

[0008] To address the migration and adaptation issues of existing continuous integration system artifacts to domestic platforms, this invention proposes a continuous integration system for domestic platforms that supports the direct generation of artifacts that can run on mainstream domestic platforms (Loongson, Phytium, Shenwei, Kunpeng, Hygon, Zhaoxin). This avoids the waste of development costs and time caused by generating artifacts in existing continuous integration systems and then migrating and adapting them to domestic platforms.

[0009] (2) Enhance code security To address code security issues, we can enhance code security by implementing code security checks, code tracing, and code obfuscation. This process detects vulnerabilities in software development, identifies open-source code and external dependencies referenced in the software, and obfuscates the code to increase the difficulty of cracking it.

[0010] (3) Safeguarding national information security By developing a continuous integration pipeline service engine and secure containers, we can achieve continuous integration pipeline orchestration, scheduling, execution and monitoring, as well as isolation of environmental resources. This will enable the replacement of foreign continuous integration tools, meet the requirements of continuous integration in the development of domestic platform software, and help safeguard national information security. Attached Figure Description

[0011] Figure 1 This is a functional architecture diagram of the continuous integration system for domestically produced platforms according to the present invention; Figure 2 Deployment architecture diagram for continuous integration systems targeting domestic platforms; Figure 3 Business process diagram for continuous integration systems targeting domestic platforms; Figure 4 A typical continuous integration pipeline workflow diagram; Figure 5 This is a functional architecture diagram for a secure container. Detailed Implementation

[0012] To make the objectives, contents, and advantages of the present invention clearer, the specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples.

[0013] This invention proposes a continuous integration system for domestically developed platforms, comprising: a code management module, a continuous integration pipeline service engine, a code security enhancement module, an automated testing toolset, a remote compilation and build module, and an artifact management module. The code management module is used to manage and store source code during the development process and is the source of continuous integration; The continuous integration pipeline service engine includes three sub-modules: pipeline orchestration, pipeline scheduling, and pipeline execution and monitoring. It is used for pipeline orchestration, scheduling, execution, and monitoring, and is responsible for managing continuous integration tasks and supporting the integration of other tools. The code security enhancement module includes three sub-modules: code security detection, code tracing, and code obfuscation. These modules are used to protect the security of code and software during development and testing, and to increase the difficulty of reverse engineering the code. The automated testing toolset includes unit testing tools, integration testing tools, functional testing tools, and performance testing tools. Tools can be selected as task nodes in the pipeline orchestration to perform automated code testing and improve code quality. The remote compilation and build module includes two sub-modules: a secure container and a dependency management module. It is used to compile and build code on mainstream domestic platforms, which can improve compilation and build efficiency and effectively manage the dependency libraries used by the code. The artifact management module is used to manage binary artifacts generated by the continuous integration pipeline, and supports artifact classification, search, and version management.

[0014] This invention proposes a functional architecture for a continuous integration system oriented towards domestically developed platforms, as follows: Figure 1 As shown.

[0015] This invention proposes a continuous integration system deployment architecture for domestically developed platforms, as follows: Figure 2 As shown.

[0016] The business process of a continuous integration system for domestically developed platforms proposed in this invention is as follows: S1. Software developers write code in the integrated development environment of the development machine, submit the code to the code management module, store it in the code repository, and manage the code in the code management module; S2. Software developers perform pipeline orchestration in the continuous integration pipeline orchestration module. After the software developers commit the code to the code repository, the associated pipeline is automatically triggered, pipeline tasks are generated, the continuous integration pipeline service engine pulls the code, and performs code inspection (code security check, code tracing), compilation and building, and testing based on the pipeline orchestration information. S3. If the code fails the inspection, it is reported to the software developers for modification; if it passes, the source code is obfuscated and remote compilation and build are performed. The remote compilation and build module compiles and builds on mainstream domestic platforms (Loongson, Phytium, Shenwei, Kunpeng, Hygon, Zhaoxin) based on a secure container, generating artifacts that can run on the corresponding domestic platforms; S4. After completing the remote compilation and build, select the appropriate tool from the automated testing toolset to perform automated testing; S5. If the test fails, feedback will be given to the software developers for modification; if the test passes, the artifact will be uploaded to the artifact management module for management.

[0017] This invention proposes a continuous integration system business process for domestically developed platforms, as follows: Figure 3 As shown. Module 1: Code Management Module

[0018] The code management module stores and manages software source code through a code repository, providing functions such as code hosting, branch management, team collaboration, access control, and merge review. It allows for centralized management of the code repository, control of code branches and versions, and team collaboration, thereby improving development speed, code quality, and collaboration efficiency. Software developers submit code to the code management module through their integrated development environment (IDE) for code management. Upon receiving a pipeline trigger command, the continuous integration pipeline service engine module pulls code from the code repository and selects a pre-orchestrated pipeline for execution. Module 2: Continuous Integration Pipeline Service Engine

[0019] The continuous integration pipeline service engine is used to manage continuous integration pipelines, including three sub-modules: pipeline orchestration, pipeline scheduling, and pipeline execution and monitoring. The functions of each module are as follows. (1) Pipeline orchestration submodule

[0020] The pipeline orchestration submodule is used for the visual construction and configuration of continuous integration pipelines. It allows for customized orchestration of pipeline task nodes based on the characteristics of the software project, including configuration of pipeline task nodes, management of execution order and parallel relationships between different task nodes, and setting execution conditions for each task node. This includes orchestration and parameter settings for stages such as code security checks, code tracing, code obfuscation, remote compilation and building, and automated testing. A typical orchestrated continuous integration pipeline workflow is as follows: Figure 4 As shown. (2) Pipeline scheduling submodule

[0021] The pipeline scheduling submodule is used for scheduling continuous integration pipelines, managing continuous integration pipeline tasks, avoiding task conflicts and resource contention, and ensuring the stable and reliable operation of the pipeline. The pipeline scheduling module receives external event messages or local system timed messages, queries pipelines that meet the execution conditions, and sends tasks to task nodes according to the pipeline orchestration. The task nodes are responsible for the actual execution of the tasks and the feedback of execution results. (3) Pipeline execution and monitoring submodule

[0022] The pipeline execution and monitoring submodule is used for continuous integration pipeline execution control and operation record viewing.

[0023] The execution control function allows software developers to adjust the pipeline status in real time. It supports controlling the pipeline's execution status, such as pausing, continuing, and stopping, based on execution records and execution status data, through control buttons or command lines, ensuring that pipeline execution is flexible and controllable.

[0024] The execution log viewing function provides software developers with detailed pipeline execution log information, including execution time, results, and logs. By viewing and analyzing the execution log, software developers can optimize the pipeline, including changing the composition of task nodes, adjusting the execution order and parallel relationships between tasks, and optimizing execution configurations. Module 3: Code Security Enhancement Module

[0025] The code security enhancement module is used to enhance code security and includes three sub-modules: code security detection, code tracing, and code obfuscation. The functions of each module are described below. (1) Code security detection submodule

[0026] The code security detection submodule is used to detect potential security vulnerabilities in the code and whether the code is written in compliance with regulations. It provides a code security detection report, which can improve the security, standardization and maintainability of the code, and reduce the maintenance cost and risk of the software. It mainly includes code security vulnerability detection and code compliance check.

[0027] Code security vulnerability detection is used to perform static analysis on source code. By parsing the syntax, semantics, and data flow of the code, it identifies code that may have security vulnerabilities and proposes remediation suggestions.

[0028] The code compliance check has functions such as setting check rules, scanning code style, and pushing scan exceptions. By automatically detecting the code pulled from the code management module, it can determine whether the code coding follows relevant standards and specifications, which helps to reduce code errors and defects. (2) Code tracing submodule

[0029] The code tracing submodule is used to detect open-source code and its security risks, reducing the vulnerability risks introduced by open-source code. The code tracing submodule mainly includes code source tracing and code dependency tracing. It can trace the specific open-source projects referenced by the code, avoiding the reference of code with security risks; for code using external dependency libraries, it can trace the information of the dependency libraries used, avoiding the reference of dependency libraries with security risks. (3) Code obfuscation submodule

[0030] The code obfuscation submodule is used to obfuscate source code, supporting obfuscation methods such as instruction substitution, name substitution, string encryption, control flow flattening, and control flow forgery. It allows for configuration of obfuscation methods and control over obfuscation strength, achieving a balance between program performance and obfuscation effectiveness. It enables automatic code rewriting without altering program behavior, changing code order and control flow, increasing the difficulty of reverse engineering and enhancing code security. Module 4: Automated Testing Toolset

[0031] The automated testing toolset provides automated testing tools for unit testing, integration testing, functional testing, and performance testing. Currently, it includes JUnit, pytest, Selenium, Cypress, JMeter, and Gatling, and supports the integration and extension of new tools. During pipeline orchestration, automated testing tools can be orchestrated according to project characteristics, and test reports can be generated and displayed to identify code issues and improve software quality. Module 5: Remote Compilation and Build Module

[0032] The remote compilation and build module is used for remote compilation and build of code on mainstream domestic platforms. It includes two sub-modules: a secure container and a dependency management module. The functions of each module are as follows. (1) Safety container

[0033] The secure container is developed based on namespace and cgroup technologies, conforms to the CRI (Container Runtime Interface) specification, provides an independent runtime environment for software, supports seamless cross-container interaction and file sharing between software, and allows software to directly access and use the host machine's network, graphics, and user files. All tools and services used in this invention are packaged into secure container images and run within secure containers.

[0034] The secure container mainly consists of two parts: external interaction and execution engine. Its functional architecture is as follows: Figure 5 As shown.

[0035] The external interaction component supports the interaction between the software inside the secure container and the host operating system, other secure containers, etc., providing the ability to access external devices and share files, and providing the software inside the secure container with a running and usage environment that is basically consistent with the host environment.

[0036] The execution engine is responsible for providing a complete and independent runtime environment for the software, including system permission management, interface interaction management, root file system, persistence of file data state, etc., and introduces a three-member mechanism to enhance container security. (2) Dependency Management Submodule

[0037] The remote compilation and build server cluster includes six mainstream domestic platforms: Loongson, Phytium, Shenwei, Kunpeng, Hygon, and Zhaoxin. The dependency management submodule manages the basic runtime and development libraries required by these six platforms, storing them in a secure container to achieve unified management and sharing of dependency libraries and avoid dependency conflicts. The dependency management submodule features a dependency repository, dependency auditing, and local build acceleration functions. The dependency repository manages the storage of dependency libraries; dependency auditing verifies the safety and compliance of external dependency libraries; and local build acceleration downloads dependency libraries to the local machine during compilation, reducing network transmission time and improving build speed. Module Six: Product Management Module

[0038] The artifact management module stores and manages binary artifacts generated by the continuous integration system that can be directly run or deployed in the target domestic environment. These include bare-metal artifacts (artifacts that run directly on physical machines without any virtualization measures) and secure container images. The artifact management module features a user-friendly interface, providing artifact storage, categorization, search, and version management functions. It also provides installation packages for software deployment and private dependencies for builds.

[0039] This invention proposes a continuous integration system and method for domestically developed platforms, possessing continuous integration capabilities for software development on domestically developed platforms. This invention has the following technical advantages: (1) For domestic platforms To address the compatibility issues of existing continuous integration systems (CIS) on domestic platforms, this invention proposes a CIS system developed specifically for domestic platforms. All tools and plugins in existing CIS systems are adapted for domestic platforms, thus improving the efficiency of software development on these platforms.

[0040] To address the migration and adaptation issues of existing continuous integration system artifacts to domestic platforms, this invention proposes a continuous integration system for domestic platforms that supports the direct generation of artifacts that can run on mainstream domestic platforms (Loongson, Phytium, Shenwei, Kunpeng, Hygon, Zhaoxin). This avoids the waste of development costs and time caused by generating artifacts in existing continuous integration systems and then migrating and adapting them to domestic platforms.

[0041] (2) Enhance code security To address code security issues, we can enhance code security by implementing code security checks, code tracing, and code obfuscation. This process detects vulnerabilities in software development, identifies open-source code and external dependencies referenced in the software, and obfuscates the code to increase the difficulty of cracking it.

[0042] (3) Safeguarding national information security By developing a continuous integration pipeline service engine and secure containers, we can achieve continuous integration pipeline orchestration, scheduling, execution and monitoring, as well as isolation of environmental resources. This will enable the replacement of foreign continuous integration tools, meet the requirements of continuous integration in the development of domestic platform software, and help safeguard national information security.

[0043] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A continuous integration system for domestically developed platforms, characterized in that, The system includes: a code management module, a continuous integration pipeline service engine, a code security enhancement module, an automated testing toolset, a remote compilation and build module, and an artifact management module; The code management module is used to manage and store source code during the development process and is the source of continuous integration; The continuous integration pipeline service engine includes three sub-modules: pipeline orchestration, pipeline scheduling, and pipeline execution and monitoring. It is used for pipeline orchestration, scheduling, execution, and monitoring, and is responsible for managing continuous integration tasks and supporting the integration of other tools. The code security enhancement module includes three sub-modules: code security detection, code tracing, and code obfuscation. These modules are used to protect the security of code and software during development and testing, and to increase the difficulty of reverse engineering the code. An automated testing toolset includes: unit testing tools, integration testing tools, functional testing tools, and performance testing tools. Tools are selected as task nodes in the pipeline orchestration to perform automated code testing. The remote compilation and build module includes two sub-modules: a secure container and a dependency management module. It is used to compile and build code on mainstream domestic platforms, improve compilation and build efficiency, and effectively manage the dependency libraries used by the code. The artifact management module is used to manage binary artifacts generated by the continuous integration pipeline, and supports artifact classification, search, and version management.

2. The continuous integration system for domestically developed platforms as described in claim 1, characterized in that, The code management module stores and manages software source code through a code repository, providing functions such as code hosting, branch management, team collaboration, access control, and merge review. The code management module centrally manages the code repository, controls code branches and versions, and facilitates team collaboration to improve development speed, code quality, and collaboration efficiency. Software developers submit code to the code management module through the integrated development environment for code management. After receiving a pipeline trigger command, the continuous integration pipeline service engine module pulls code from the code repository and selects a pre-arranged pipeline for execution.

3. The continuous integration system for domestically developed platforms as described in claim 2, characterized in that, The pipeline orchestration submodule is used for the visual construction and configuration of continuous integration pipelines. It performs custom orchestration of pipeline task nodes according to the characteristics of software projects, and configures pipeline task nodes, manages the execution order and serial-parallel relationship between different task nodes, and sets the execution conditions for each task node, including the orchestration and parameter settings for code security checks, code tracing, code obfuscation, remote compilation and building, and automated testing phases.

4. The continuous integration system for domestically developed platforms as described in claim 2, characterized in that, The pipeline scheduling submodule is used to schedule the continuous integration pipeline, manage continuous integration pipeline tasks, avoid task conflicts and resource competition, and ensure the stable and reliable operation of the pipeline. The pipeline scheduling module receives external event messages or local system timed messages, queries pipelines that meet the execution conditions, and sends tasks to task nodes according to the pipeline orchestration. The task nodes are responsible for the specific execution of the tasks and the feedback of execution results.

5. The continuous integration system for domestically developed platforms as described in claim 2, characterized in that, The pipeline execution and monitoring submodule is used for continuous integration of pipeline execution control and operation record viewing; The execution control function allows software developers to adjust the pipeline status in real time. It supports controlling the pipeline execution status through control buttons or command lines based on execution records and execution status data, including: pause, continue, and stop, ensuring that pipeline execution is flexible and controllable. The runtime log viewing function provides software developers with detailed pipeline runtime log information, including execution time, results, and logs. By viewing and analyzing the runtime log, software developers can optimize the pipeline, including changing the composition of task nodes, adjusting the execution order and serial-parallel relationships between tasks, and optimizing execution configuration.

6. The continuous integration system for domestically developed platforms as described in any one of claims 3-5, characterized in that, The code security detection submodule is used to detect potential security vulnerabilities in the code and whether the code writing is compliant, and provides a code security detection report, including code security vulnerability detection and code compliance check. The code security vulnerability detection is used to perform static analysis on the source code. By parsing the syntax, semantics and data flow of the code, it identifies code that may have security vulnerabilities and proposes remediation suggestions. The code compliance check has the functions of setting inspection rules, scanning code style, and pushing scan anomalies. By automatically detecting the code pulled from the code management module, it judges whether the code coding follows relevant standards and specifications, which helps to reduce code errors and defects. The code tracing submodule is used to detect open source code and its security risks in the code, and reduce the vulnerability risks brought by open source code. The code tracing submodule includes code tracing and code dependency tracing. It is used to trace the specific open source projects referenced by the code to avoid referencing code with security risks. It is used to trace the dependency library information used by code that uses external dependency libraries to avoid referencing dependency libraries with security risks. The code obfuscation submodule is used to obfuscate source code. It supports instruction substitution, name substitution, string encryption, control flow flattening, and control flow forgery. The obfuscation methods and obfuscation strength can be combined through parameter configuration to achieve a balance between program performance and obfuscation effect. This technology enables the automatic rewriting of code without altering program behavior, changing the code order and control flow, increasing the difficulty of reverse engineering and cracking the code, and enhancing code security.

7. The continuous integration system for domestically developed platforms as described in claim 6, characterized in that, The automated testing toolset provides unit testing, integration testing, functional testing, and performance testing tools, including JUnit, pytest, Selenium, Cypress, JMeter, and Gatling, and supports the integration and extension of new tools. During pipeline orchestration, automated testing tools are orchestrated according to project characteristics, and test reports are generated and displayed to identify problems in the code and improve software quality.

8. The continuous integration system for domestically developed platforms as described in claim 7, characterized in that, The remote compilation and build module is used for remote compilation and build of code on mainstream domestic platforms, including two sub-modules: a security container and a dependency management module. The secure container is developed based on Namespace and Cgroup technologies, conforms to CRI specifications, provides an independent running environment for software, supports seamless cross-container interaction and file sharing between software, and allows software to directly access and use the host machine's network, graphics and user files. The tools and services have all been packaged into secure container images and run within secure containers; A secure container consists of two parts: an external interaction mechanism and an execution engine. The external interaction component supports the interaction between the software inside the secure container and the host operating system and other secure containers, providing the ability to access external devices and share files, and providing the software inside the secure container with a running and usage environment that is basically consistent with the host environment. The execution engine is responsible for providing a complete and independent runtime environment for the software, including system permission management, interface interaction management, root file system, file data state persistence, and introduces a three-member mechanism to enhance container security. The remote compilation and build server cluster includes six mainstream domestic platforms: Loongson, Phytium, Shenwei, Kunpeng, Hygon, and Zhaoxin. The dependency management submodule manages the basic runtime libraries and development libraries required by these six mainstream domestic platforms and stores them in a secure container to achieve unified management and sharing of dependency libraries and avoid dependency conflicts. The dependency management submodule has dependency repository, dependency auditing, and local build acceleration functions. The dependency repository is used for the storage management of dependency libraries; dependency auditing is used to verify whether external dependency libraries are safe and compliant; and local build acceleration is used to download dependency libraries to the local machine during compilation and build.

9. The continuous integration system for domestically developed platforms as described in claim 8, characterized in that, The artifact management module is used to store and manage binary artifacts generated by the continuous integration system that can be directly run or deployed in the target domestic environment, including bare metal artifacts and secure container images. The artifact management module has a user-friendly interface, provides artifact storage, classification, search and version management functions, provides installation packages for software deployment, and provides private dependencies for building.

10. A continuous integration method for a domestically developed platform based on the system described in any one of claims 1-9, characterized in that, The method includes the following steps: S1. Software developers write code in the integrated development environment of the development machine, submit the code to the code management module, store it in the code repository, and manage the code in the code management module; S2. Software developers perform pipeline orchestration in the continuous integration pipeline orchestration module. After the software developers submit the code to the code repository, the associated pipeline is automatically triggered, pipeline tasks are generated, the continuous integration pipeline service engine pulls the code, and performs code inspection, compilation, building and testing based on the pipeline orchestration information. S3. If the code fails the inspection, it will be reported to the software developers for modification; if it passes, the source code will be obfuscated and remote compilation and build will be performed; the remote compilation and build module will compile and build on mainstream domestic platforms based on secure containers to generate artifacts that can run on the corresponding domestic platforms; S4. After completing the remote compilation and build, select the appropriate tool from the automated testing toolset to perform automated testing; S5. If the test fails, feedback will be given to the software developers for modification; if the test passes, the artifact will be uploaded to the artifact management module for management.

Images