Continuous integration method, device and system suitable for engineering machinery product software

Abstract

The invention discloses a continuous integration method, device and system suitable for engineering machinery product software, and the method comprises the steps: selecting an adaptive assembly line template based on an obtained version change event, and generating an assembly line execution task; generating a software product based on the pipeline execution task; performing quality judgment on a construction log, a construction state and product data generated in a software product generation process based on the assembly line execution task, and determining to continue or stop executing the assembly line execution task according to a quality judgment result; performing automatic verification on the software product based on the assembly line execution task, and generating verification data; performing quality judgment on the verification data based on the assembly line execution task, and determining to continue or stop executing the assembly line execution task according to a quality judgment result; and performing unified archiving management on the software products passing the automatic verification. According to the method, automation and standardization of the whole process including code (model) submission, compiling construction (software product generation), test verification and product filing are achieved.

Description

Technical Field

[0001] This invention belongs to the field of software development technology, specifically relating to a continuous integration method, apparatus, and system suitable for engineering machinery product software. Background Technology

[0002] With the deep integration of the "Industrial Internet" and construction machinery manufacturing, the industry is accelerating its transformation and upgrading towards a stage centered on intelligence and unmanned operation. Software has become a key factor determining the overall performance, functional differentiation, and user experience of construction machinery, and "software-defined construction machinery" is becoming an important trend driving industry development. Software not only carries core functions such as control logic, operation algorithms, remote diagnostics, and intelligent optimization, but also directly affects the safety, stability, and intelligence level of products.

[0003] However, with the increasing complexity of engineering machinery software functions, the faster pace of version iterations, and the growing integration of software and hardware, traditional software development models that rely primarily on manual intervention and phased verification are no longer adequate for current needs. Existing development processes generally suffer from prominent problems such as long build cycles, delayed quality feedback, difficulties in problem localization, and low collaboration efficiency.

[0004] In actual R&D, engineering machinery software projects typically involve multiple areas such as electrical systems, hydraulic systems, and control systems. Inconsistent development paces among different teams and unclear integration interface definitions often lead to delays in functional verification and difficulties in version traceability. Due to the lack of a continuous integration automated pipeline mechanism, R&D teams usually need to conduct centralized integration and verification in the later stages of the project, which is risky and costly. Once a problem is discovered, the cost of fixing it increases significantly.

[0005] Current software building and integration methods largely rely on manual triggering and environment configuration, resulting in low levels of automation. The build results lack unified standards and quality control mechanisms; testing is fragmented, making it difficult to quantify test coverage and feedback; and product output lacks standardized management processes, failing to guarantee version consistency and traceability. These problems directly lead to low software integration efficiency, long verification cycles, and delayed defect discovery, impacting product time-to-market and system reliability.

[0006] Therefore, there is an urgent need to research a continuous integration methodology suitable for software development of construction machinery products. This methodology aims to address issues such as integration delays, fragmented processes, and uncontrollable quality in traditional development models, achieving full automation and a closed-loop quality process from development and verification to release. Advancing this research will have significant engineering value and economic implications for enhancing the software development capabilities of the construction machinery industry and accelerating its digital transformation.

[0007] In the software development field of the construction machinery industry, OEMs and control system suppliers commonly use tools such as Codesys and Simulink for control logic design. These software systems are typically used in construction machinery equipment such as excavators, loaders, cranes, and pavers to realize core functions such as power control, motion coordination, energy management, and safety protection.

[0008] In existing technologies, the development process of engineering machinery software includes stages such as software design, software development, unit testing, integration testing, and real-machine verification. To improve development efficiency, some companies have attempted to introduce the concept of continuous integration to automate the software compilation, building, and testing processes. The main implementation schemes are as follows:

[0009] 1. Automated compilation and build mechanisms. Enterprises typically configure build scripts to automate the generation of executable artifacts from source files. This approach can reduce manual operations to some extent and improve build consistency.

[0010] 2. Automated Testing Mechanism. Some enterprises integrate unit testing and HIL simulation testing interfaces to automate the functional verification of code or logic modules. Test results are aggregated into reports by the system to evaluate software stability and functional correctness.

[0011] 3. Manually Triggered Prototype Verification Process: Currently, most construction machinery companies' continuous integration systems only cover the compilation and testing phases of the R&D stage. The prototype testing phase is still mainly based on manual operation, and test results need to be recorded and fed back offline, resulting in a low degree of automation in the process.

[0012] While existing technical solutions have achieved initial automation of software development and testing, they remain at the level of simple migration and application of general continuous integration frameworks, failing to fully consider the industry characteristics and quality control requirements of the construction machinery sector. Specifically, the following problems exist:

[0013] (1) Lack of deep integration with Simulink and Codesys tools, commonly used software for engineering machinery.

[0014] Most existing continuous integration systems are based on general software development frameworks, while software development in the construction machinery industry involves the use of specific tools such as Simulink and Codesys. Existing continuous integration systems cannot integrate Simulink's model design and code generation capabilities, nor Codesys' control logic download and compilation capabilities. This leads to inconsistencies in the toolchain during development, increases the complexity of manual operations, and negatively impacts development efficiency and software quality.

[0015] (2) The automated production line lacks multi-stage verification coverage.

[0016] Existing continuous integration solutions typically only cover code building and unit testing. However, the development of engineering machinery software requires not only code verification but also multiple key stages such as model verification, HIL simulation testing, and prototype testing. Current technologies cannot achieve automated scheduling and feedback loops in the pipeline, resulting in long development cycles, opaque verification results, and insufficient quality gates in the verification process, which affects the stability and reliability of the software.

[0017] (3) Insufficient quality control and security access control mechanisms.

[0018] Most existing continuous integration solutions rely on general quality gate rules (such as static code analysis and compile checks), failing to introduce specific quality control mechanisms such as security verification, safety compliance checks, and high reliability testing tailored to the unique needs of the construction machinery industry. Because mandatory quality gates are not embedded, the build results cannot provide real-time feedback on whether they meet stringent industry standards. Therefore, existing systems struggle to guarantee the continued high quality and compliance of software throughout the product lifecycle, especially in complex hardware and software integration scenarios, failing to fully ensure system security and functional consistency.

[0019] (4) It cannot provide full lifecycle version tracking and management.

[0020] Existing continuous integration systems typically focus on short-term builds and testing during the development process, lacking full lifecycle traceability management of artifacts. From software development and testing to final production and packaging, existing systems cannot effectively control and trace software at different stages. This is particularly problematic in the construction machinery industry, where software products require rigorous acceptance and maintenance, and software-hardware compatibility needs continuous monitoring after each release. The lack of a unified version management and history traceability platform in current technologies makes it difficult to ensure continuous stability during actual deployment and maintenance.

[0021] (5) Lack of automated fault diagnosis and repair mechanism.

[0022] Error diagnosis in existing continuous integration systems typically relies on developers manually analyzing logs to locate problems. Information such as build failures and test failures can get lost in the massive amounts of logs, leading to inefficient fault location and remediation. The existing error feedback and localization process is inefficient and lacks intelligent diagnostic and remediation mechanisms. Developers need to troubleshoot step-by-step based on logs, impacting the efficiency and collaboration of the entire development process. This is especially true in large-scale team collaborations and complex system integration, often resulting in delayed problem discovery and increased difficulty and time commitment for remediation. Summary of the Invention

[0023] To address the aforementioned issues, this invention proposes a continuous integration method, apparatus, and system suitable for engineering machinery product software. It achieves full-process automation and standardization from code (model) submission, compilation and construction, testing and verification, and product archiving. It realizes an automated development system with toolchain collaboration, multi-stage verification closed loop, mandatory quality access control, full lifecycle traceability, and intelligent fault diagnosis, significantly improving software development efficiency, verification accuracy, and product consistency, and ensuring high security, high reliability, and continuous maintainability of the software in complex industrial environments.

[0024] To achieve the above-mentioned technical objectives and effects, the present invention is implemented through the following technical solution:

[0025] In a first aspect, the present invention provides a continuous integration method for software of engineering machinery products, comprising:

[0026] Based on the obtained version change event, select the appropriate pipeline template according to preset rules and generate pipeline execution tasks;

[0027] Based on the software version information, configuration parameters, and build strategy carried in the pipeline execution task, a software artifact is generated;

[0028] Based on the quality judgment criteria defined in the pipeline execution task, the build logs, build status and artifact data generated during the software artifact generation process are judged for quality, and the pipeline execution task is continued or terminated based on the quality judgment results.

[0029] Based on the verification strategy defined in the pipeline execution task, the software artifact is automatically verified and verification results are generated.

[0030] Based on the quality judgment criteria defined in the pipeline execution task, the verification results are judged for quality, and the pipeline execution task is continued or terminated based on the quality judgment results.

[0031] Software artifacts that have passed automated verification are archived and managed in a unified manner, and the archive completion status is returned, marking the end of one continuous integration pipeline execution process.

[0032] In conjunction with the first aspect, optionally, the step of selecting an appropriate pipeline template based on the acquired version change event according to preset rules and generating pipeline execution tasks includes:

[0033] When a code commit, model update, or version merge event is detected, the appropriate pipeline template is selected according to preset rules, and a pipeline execution task is generated.

[0034] The pipeline execution tasks include software version information, configuration parameters and build strategies, verification strategies and quality judgment criteria.

[0035] In conjunction with the first aspect, optionally, the method for generating the software artifact includes:

[0036] Based on the software version information, configuration parameters, and build strategy carried in the pipeline execution task, the corresponding software source files and model files are obtained from the version control repository, and automatic compilation, dependency resolution, and artifact packaging operations are performed to obtain the software artifact.

[0037] In conjunction with the first aspect, optionally, the step of deciding whether to continue or terminate the execution of the pipeline task based on the quality judgment result includes:

[0038] When the quality assessment results determine that the current stage results meet the release conditions, continue executing the steps that have not yet been completed in the current pipeline task.

[0039] If the quality assessment results indicate that the current stage does not meet the release conditions, then the unfinished steps in the current production line task should be terminated immediately.

[0040] In conjunction with the first aspect, the continuous integration method may optionally further include:

[0041] After generating the pipeline execution task, a unique pipeline instance identifier is created, and the corresponding log context is initialized. The log context is used to identify the execution process of this pipeline task.

[0042] During the pipeline execution of task generation, automated verification, and quality judgment, the start time, end time, execution node identifier, and abnormal information generated by quality judgment of each process are automatically recorded to form a structured stage log; quality backtracking analysis is performed based on the structured stage log;

[0043] The fault causes are identified based on the structured stage logs, and repair suggestions are generated.

[0044] In conjunction with the first aspect, optionally, during the automated verification of the software artifact, each verification stage is an independent execution node in the pipeline. If the previous verification stage fails, the execution of the subsequent verification stage is automatically terminated. The verification results of each verification stage are used to compare with the quality judgment standard to generate a quality judgment result, and the pipeline execution task is continued or terminated based on the quality judgment result.

[0045] In conjunction with the first aspect, optionally, the pipeline template defines the execution stages, execution order, triggering conditions, and quality judgment criteria of the pipeline in a parameterized manner, including:

[0046] Basic identification parameters for the production line, used to uniquely identify and manage production line templates;

[0047] Triggering and adaptation parameters are used to describe the triggering conditions and adaptation rules of the pipeline template;

[0048] The execution phase definition parameters are used to define the execution phases and execution order contained in the pipeline template;

[0049] Stage execution control parameters are used to describe the specific execution method of each execution stage;

[0050] Verification strategy parameters are used to define the rules related to automated verification;

[0051] Quality access control parameters are used to define the nodes in the pipeline template that are required to perform quality checks, and to control whether the pipeline is allowed to proceed to the next execution stage.

[0052] Intelligent analysis of related parameters supports subsequent intelligent diagnosis and continuous optimization.

[0053] Secondly, the present invention provides a continuous integration device suitable for software in engineering machinery products, comprising:

[0054] The triggering and task scheduling module, based on the obtained version change event, selects the appropriate pipeline template according to preset rules and generates pipeline execution tasks;

[0055] The build and artifact generation module is used to generate software artifacts based on the software version information, configuration parameters and build strategies carried in the pipeline execution tasks;

[0056] A multi-stage automated verification module is used to automatically verify the software artifacts based on the verification strategy defined in the pipeline execution task and generate verification results.

[0057] The quality access control module is used to perform quality judgment on the build logs, build status and artifact data generated during the software artifact generation process based on the quality judgment criteria defined in the pipeline execution task, and decide whether to continue or terminate the execution of the pipeline execution task based on the quality judgment result; and to perform quality judgment on the verification results based on the quality judgment criteria defined in the pipeline execution task, and decide whether to continue or terminate the execution of the pipeline execution task based on the quality judgment result.

[0058] The artifact management and traceability module is used to uniformly archive and manage software artifacts that have passed automated verification, and return the archiving completion status, marking the end of a continuous integration pipeline execution process.

[0059] In conjunction with the second aspect, optionally, the continuous integration apparatus further includes:

[0060] The pipeline execution log generation and management module is used to create a unique pipeline instance identifier and initialize the corresponding log context after generating a pipeline execution task, which is used to identify the execution process of this pipeline task. During the pipeline execution task generation, automated verification, and quality judgment process, it automatically records the start time, end time, execution node identifier, and abnormal information generated by quality judgment for each process, forming a structured stage log.

[0061] The intelligent analysis and fault diagnosis module is used to identify fault causes and generate repair suggestions based on the structured stage logs in the pipeline execution log generation and management module.

[0062] The product management and traceability module is also connected to the production line execution log generation and management module, which is used for quality backtracking analysis based on structured stage logs.

[0063] Thirdly, the present invention provides a continuous integration system suitable for software of engineering machinery products, including a storage medium and a processor;

[0064] The storage medium is used to store instructions;

[0065] The processor is configured to operate according to the instructions to perform the method according to any one of the first aspects.

[0066] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0067] This invention proposes a continuous integration method, device, and system for engineering machinery product software. It realizes full-process automation and standardization from code (model) submission, compilation and construction, testing and verification, and product archiving. It achieves an automated development system with toolchain collaboration, multi-stage verification closed loop, mandatory quality gate control, full life cycle traceability, and intelligent fault diagnosis, which significantly improves software development efficiency, verification accuracy, and product consistency, and ensures high security, high reliability, and continuous maintainability of software in complex industrial environments. Attached Figure Description

[0068] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein:

[0069] Figure 1 This is a flowchart illustrating a continuous integration method according to an embodiment of the present invention;

[0070] Figure 2This is a schematic diagram of the continuous integration device according to an embodiment of the present invention. Detailed Implementation

[0071] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0072] Furthermore, if the embodiments of this invention involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed by this invention.

[0073] Example 1

[0074] This invention provides a continuous integration method for software in engineering machinery products, comprising the following steps:

[0075] (1) Based on the obtained version change event, select the appropriate pipeline template according to the preset rules and generate pipeline execution tasks;

[0076] (2) Based on the software version information, configuration parameters and build strategy carried in the pipeline execution task, generate software artifacts;

[0077] (3) Based on the quality judgment criteria defined in the pipeline execution task, perform quality judgment on the build logs, build status and artifact data produced during the software artifact generation process, and decide whether to continue or terminate the execution of the pipeline execution task based on the quality judgment result;

[0078] (4) Based on the verification strategy defined in the pipeline execution task, perform automated verification of the software artifact and generate verification results;

[0079] (5) Based on the quality judgment criteria defined in the pipeline execution task, the verification results are judged for quality, and the pipeline execution task is continued or terminated according to the quality judgment results;

[0080] (6) Perform unified archiving management on software artifacts that have passed automated verification and return the archiving completion status to mark the end of a continuous integration pipeline execution process.

[0081] In one specific embodiment of the present invention, the step of selecting an appropriate pipeline template based on the acquired version change event according to preset rules and generating pipeline execution tasks includes:

[0082] When a code commit, model update, or version merge event is detected, the appropriate pipeline template is selected according to preset rules, and a pipeline execution task is generated.

[0083] The pipeline execution tasks include software version information, configuration parameters and build strategies, verification strategies and quality judgment criteria.

[0084] In one specific embodiment of the present invention, the method for generating the software artifact includes:

[0085] Based on the software version information, configuration parameters, and build strategy carried in the pipeline execution task, the corresponding software source files and model files are obtained from the version control repository, and automatic compilation, dependency resolution, and artifact packaging operations are performed to obtain the software artifact.

[0086] In one specific embodiment of the present invention, the step of deciding whether to continue or terminate the pipeline execution task based on the quality judgment result includes:

[0087] When the quality assessment results determine that the current stage results meet the release conditions, continue executing the steps that have not yet been completed in the current pipeline task.

[0088] If the quality assessment results indicate that the current stage does not meet the release conditions, then the unfinished steps in the current production line task should be terminated immediately.

[0089] In one specific embodiment of the present invention, the continuous integration method further includes:

[0090] After generating the pipeline execution task, a unique pipeline instance identifier is created, and the corresponding log context is initialized. The log context is used to identify the execution process of this pipeline task.

[0091] During the pipeline execution of task generation, automated verification, and quality judgment, the start time, end time, execution node identifier, and abnormal information generated by quality judgment of each process are automatically recorded to form a structured stage log.

[0092] Support quality backtracking analysis based on the structured stage logs;

[0093] The cause of the failure is identified based on the configuration stage log, and repair suggestions are generated.

[0094] In one specific embodiment of the present invention, during the automated verification of the software artifact, each verification stage is an independent execution node in the pipeline. If the previous verification stage fails, the execution of the subsequent verification stage is automatically terminated. The verification results of each verification stage are used to compare with the quality judgment standard to generate a quality judgment result, and the pipeline execution task is continued or terminated based on the quality judgment result.

[0095] In one specific embodiment of the present invention, the pipeline template defines the execution stages, execution order, triggering conditions, and quality judgment criteria of the pipeline in a parameterized manner, including:

[0096] Basic identification parameters for the production line, used to uniquely identify and manage production line templates;

[0097] Triggering and adaptation parameters are used to describe the triggering conditions and adaptation rules of the pipeline template;

[0098] The execution phase definition parameters are used to define the execution phases and execution order contained in the pipeline template;

[0099] Stage execution control parameters are used to describe the specific execution method of each execution stage;

[0100] Verification strategy parameters are used to define the rules related to automated verification;

[0101] Quality access control parameters are used to define the nodes in the pipeline template that are required to perform quality checks, and to control whether the pipeline is allowed to proceed to the next execution stage.

[0102] Intelligent analysis of related parameters supports subsequent intelligent diagnosis and continuous optimization.

[0103] Based on the above solution, the entire process from code (model) submission, compilation and building, testing and verification and artifact archiving is automated and standardized. It realizes an automated development system with toolchain collaboration, multi-stage verification closed loop, mandatory quality access control, full life cycle traceability and intelligent fault diagnosis, which significantly improves software development efficiency, verification accuracy and product consistency, and ensures high security, high reliability and continuous maintainability of software in complex industrial environments.

[0104] Example 2

[0105] This invention provides a continuous integration device suitable for software in engineering machinery products, comprising:

[0106] The triggering and task scheduling module, based on the obtained version change event, selects the appropriate pipeline template according to preset rules and generates pipeline execution tasks;

[0107] The build and artifact generation module is used to generate software artifacts based on the software version information, configuration parameters and build strategies carried in the pipeline execution tasks;

[0108] A multi-stage automated verification module is used to automatically verify the software artifacts based on the verification strategy defined in the pipeline execution task and generate verification results.

[0109] The quality access control module is used to perform quality judgment on the build logs, build status and artifact data generated during the software artifact generation process based on the quality judgment criteria defined in the pipeline execution task, and decide whether to continue or terminate the execution of the pipeline execution task based on the quality judgment result; and to perform quality judgment on the verification results based on the quality judgment criteria defined in the pipeline execution task, and decide whether to continue or terminate the execution of the pipeline execution task based on the quality judgment result.

[0110] The artifact management and traceability module is used to uniformly archive and manage software artifacts that have passed automated verification, and return the archiving completion status, marking the end of a continuous integration pipeline execution process.

[0111] In one specific embodiment of the present invention, the continuous integration device further includes:

[0112] The pipeline execution log generation and management module is used to create a unique pipeline instance identifier and initialize the corresponding log context after generating a pipeline execution task. The log context is used to identify the execution process of this pipeline task. During the pipeline execution task generation, automated verification, and quality judgment process, the module automatically records the start time, end time, execution node identifier, and abnormal information generated by the quality judgment of each process to form a structured stage log.

[0113] The intelligent analysis and fault diagnosis module is used to identify fault causes and generate repair suggestions based on the structured stage logs in the pipeline execution log generation and management module.

[0114] The product management and traceability module is also connected to the production line execution log generation and management module, which is used for quality backtracking analysis based on structured stage logs.

[0115] The continuous integration device in this embodiment of the invention will be described in detail below with reference to a specific implementation method.

[0116] like Figure 2 As shown, the continuous integration device includes:

[0117] (1) Triggering and Task Scheduling Module

[0118] The triggering and task scheduling module monitors code commits, model updates, or version merge events during the software development process (specifically, it receives change events from version control systems, model management systems, or configuration management systems and triggers continuous integration tasks). When a version change event (i.e., code commit, model update, or version merge event) is detected, an appropriate pipeline template is selected according to preset rules (i.e., a self-adaptive pipeline template is implemented for different types of changes), and a pipeline execution task is generated. The triggering and task scheduling module supports rule-based triggering strategies and can automatically select the corresponding build and verification process based on the change type (i.e., code commit, model update, or version merge event) to ensure timely pipeline response and efficient execution.

[0119] (2) Construction and Product Generation Module

[0120] During the automated build phase, the pipeline pulls source files and configuration files from the version control repository and performs automatic compilation, dependency resolution, and artifact packaging. The automated build process is completed automatically by the execution machine. The system can process multiple build tasks in parallel and generate an artifact package with digital signatures and hash verification upon completion, ensuring the uniqueness and tamper-proof nature of the software artifacts.

[0121] (3) Multi-stage automated verification module

[0122] The multi-stage automated verification module includes key stages such as unit testing, integration testing, simulation verification, and prototype verification. Based on the verification strategies defined in the pipeline execution tasks, it automatically calls the corresponding test scripts or interfaces to execute tasks and collects test data and results in real time. Through a step-by-step verification mechanism, it ensures that the entire process undergoes functional verification and performance checking, achieving end-to-end controllability of development quality.

[0123] Unit testing is used to verify the correctness of the smallest functional unit or algorithm module. The implementation steps of unit testing include:

[0124] 1. Test Case Preparation

[0125] During the pipeline initialization phase, the continuous integration device automatically loads unit test cases matching the current version from the test case library. The test cases include input parameters, expected outputs, and decision conditions.

[0126] 2. Building Block Loading

[0127] After the build and artifact generation module completes the target code generation, the continuous integration device loads the functions, modules, or model units to be tested into the unit test execution environment.

[0128] 3. Automated test execution

[0129] The continuous integration device automatically calls test scripts through the test execution engine, injects test data into the target unit sequentially, and collects its output results.

[0130] 4. Result Comparison and Judgment

[0131] The continuous integration device automatically compares the actual output with the expected result and generates a judgment result indicating whether the unit test passed or failed.

[0132] 5. Reporting test results

[0133] The unit test results, along with log information, are uploaded to the quality access control module in real time, serving as one of the criteria for determining whether to proceed to the next stage.

[0134] The steps to implement integration testing include:

[0135] Integration testing is used to verify the collaborative working ability of multiple functional modules combined. Its automated implementation steps include:

[0136] 1. Integrated Environment Setup

[0137] The continuous integration device loads multiple functional modules that have passed unit tests according to the pipeline template definition to form a complete software runtime environment.

[0138] 2. Interface consistency verification

[0139] The interface consistency check program is executed automatically to verify whether the signals, parameters and calling relationships between modules meet the preset interface specifications.

[0140] 3. Scenario-driven test execution

[0141] The continuous integration device automatically executes preset operating scenarios according to the integration test strategy, simulating various control conditions and input states.

[0142] 4. Run data acquisition

[0143] During the test, the system collects information on key variables, state changes, and abnormal events in real time.

[0144] 5. Determination of Integration Results

[0145] The continuous integration device automatically analyzes the integration test results based on the test data and preset judgment rules, and generates corresponding test conclusions.

[0146] Simulation verification is used to evaluate the behavior of software under complex operating conditions in a virtual environment. The implementation steps of simulation verification include:

[0147] 1. Simulation model loading

[0148] The continuous integration device automatically loads a virtual whole machine model or system simulation model that matches the type of target engineering machinery.

[0149] 2. Software artifact deployment

[0150] The software artifacts that have passed integration testing are embedded into the simulation model to establish a closed-loop simulation runtime environment.

[0151] 3. Automatic injection under operating conditions

[0152] The continuous integration device automatically performs various typical and extreme operating condition tests according to the simulation test strategy, including load changes and fault injection.

[0153] 4. Performance indicator monitoring

[0154] During the simulation, the system continuously monitors key performance indicators such as control stability, response time, and resource consumption.

[0155] 5. Simulation Result Analysis

[0156] After the simulation is completed, the system automatically analyzes the collected data, generates a simulation verification report, and feeds it back to the quality access control module.

[0157] Prototype verification is used to verify the software's performance in a real or equivalent hardware environment. The implementation steps of prototype verification include:

[0158] 1. Prototype resource scheduling

[0159] The continuous integration device automatically selects actual or virtual prototype resources based on the pipeline configuration and completes the occupancy and initialization.

[0160] 2. Automated deployment of products

[0161] The software artifacts that have passed simulation verification are automatically sent to the target controller via the communication interface.

[0162] 3. Functional tests are executed automatically.

[0163] The continuous integration device automatically sends control commands through the communication interface based on the prototype test cases, triggering actual actions or state changes.

[0164] 4. Data Acquisition and Feedback

[0165] During the test, the continuous integration device automatically collects control signals, sensor data, and abnormal statuses, and transmits them back to the production line system in real time.

[0166] 5. Prototype Verification and Judgment

[0167] The continuous integration device automatically compares and analyzes the collected data to determine whether the software meets the functional and performance requirements under actual operating conditions.

[0168] V. Step-by-step verification and pipeline linkage mechanism

[0169] In each of the above stages, the present invention employs a step-by-step verification mechanism:

[0170] • Each stage of testing is executed as an independent node in the automated pipeline;

[0171] • If the previous stage test fails, the system will automatically terminate the execution of the subsequent stage;

[0172] • The results of each stage are fed back to the quality access control module for implementation of release or blocking control.

[0173] Through the above implementation method, multi-level automated verification of software from the unit level to the actual machine level is realized, ensuring that the software of engineering machinery products has fully covered the functional, performance and reliability verification requirements before delivery.

[0174] (4) Quality access control module

[0175] This invention sets mandatory quality gates at each key stage of the pipeline (i.e., code (model) inspection, compilation and building, automated testing, prototype verification, and AI-assisted analysis). These gates automatically or manually review and determine whether the build results meet security, real-time performance, performance stability, and compliance requirements. The gate rules can be defined and dynamically adjusted by the enterprise's quality system. When a test fails, the pipeline automatically interrupts, generating a defect report and repair suggestions, thus ensuring software quality from the source.

[0176] (5) Pipeline execution log generation and management module

[0177] During the operation of the continuous integration automated pipeline described in this invention, the continuous integration device automatically generates pipeline execution logs at each execution stage to record the execution status, behavior process, and result information of pipeline tasks, providing basic data support for subsequent quality control, intelligent analysis, and fault diagnosis.

[0178] Specifically, the process of generating pipeline execution logs includes the following steps:

[0179] (5.1) Log triggering and context initialization

[0180] When the triggering and task scheduling module starts a continuous integration task, the continuous integration device creates a unique pipeline instance identifier for the task and initializes the corresponding log context, which is used to identify the execution process of this pipeline task.

[0181] (5.2) Stage-level log collection

[0182] During each execution stage, including code inspection, compilation and building, automated testing, simulation verification, and prototype verification, the continuous integration device automatically records the start time, end time, execution node identifier, called tool interfaces and parameter information, and abnormal information generated by quality judgment by the corresponding modules, forming a structured stage log.

[0183] (5.3) Event and Exception Log Recording

[0184] When events such as build failure, test anomaly, resource conflict, or quality gate failure occur during pipeline execution, the continuous integration device automatically generates an event log, recording the anomaly type, stage of occurrence, error code, error message, and related context data.

[0185] (5.4) Summary of Results and Status Logs

[0186] After each execution phase is completed, the continuous integration device automatically generates a phase execution result log, including the execution status, pass / fail judgment result and corresponding reason explanation, and associates the result log with the quality access control judgment result.

[0187] (5.5) Unified Log Archiving and Indexing

[0188] All pipeline execution logs are archived uniformly according to the pipeline instance identifier and stored in the log management module. At the same time, a searchable index relationship is established for the intelligent analysis module and the historical backtracking module to call.

[0189] (6) Intelligent analysis and fault diagnosis module

[0190] The system has a built-in AI analysis engine that can automatically learn and classify pipeline execution logs and test verification results. When a build or verification fails, it can automatically identify the cause of the failure and generate repair suggestions, improving the efficiency of problem localization and recovery, and enabling the system to self-learn and continuously optimize.

[0191] (7) Product Management and Traceability Module

[0192] After each software artifact build is completed, the structured phase log automatically archives the software artifacts, test reports, access control results (i.e., quality assessment results), and version information to a unified artifact repository. All software artifacts have traceable version files, supporting historical backtracking queries based on build number or release time, ensuring the integrity and compliance of the development and delivery processes.

[0193] The continuous integration automated pipeline operation process of this invention, such as Figure 1 As shown, it includes the following main stages:

[0194] 1. Triggering Phase

[0195] When a code commit, model update, or version merge event is detected (i.e., the software source file, model, or configuration file is updated), the appropriate pipeline template is selected according to preset rules, and a pipeline execution task is generated.

[0196] 2. Code (Model) Inspection Phase

[0197] The system automatically performs static code checks, model specification checks, and unit tests to verify naming conventions, signal interfaces, and parameter consistency.

[0198] 3. Compilation and Build Phase

[0199] The continuous integration device automatically performs code compilation, dependency resolution, and artifact generation to ensure the consistency and security of software artifacts.

[0200] 4. Automated Testing Phase

[0201] Based on the verification strategy defined in the pipeline execution task, the software artifacts are subjected to automated testing, and test results are generated. Test results are recorded in real time and compared with quality gate control standards (i.e., quality judgment standards). Once all results pass, a quality report is automatically generated, and the process proceeds to the next stage. If testing hardware resources are available, the system can trigger automatic deployment and HIL simulation testing.

[0202] 5. Prototype Verification Phase

[0203] The software artifacts are deployed to a real or virtual prototype environment, and prototype functional testing and data acquisition are automatically performed via communication interfaces (CAN, Ethernet, etc.). The verification results are automatically transmitted back to the automated pipeline system to evaluate the performance and stability of the algorithm logic in a real controller environment.

[0204] 6. AI-assisted analysis stage

[0205] After testing, the continuous integration device's built-in intelligent analysis and fault diagnosis module analyzes the build logs and test data (i.e., structured phase logs). Based on historical automated pipeline data and an error classification model, this module performs result evaluation, anomaly detection, and root cause localization, generating an intelligent diagnostic report. The continuous integration device can automatically trigger retry builds, generate remediation suggestions, or mark potentially risky versions based on the analysis results, achieving intelligent and self-optimizing operation of the automated pipeline.

[0206] 7. Quality access control and feedback

[0207] Mandatory quality access control is embedded in each stage of the automated production line. The continuous integration device automatically determines whether the requirements for security, real-time performance, and functional consistency are met. Versions that fail to pass the access control are automatically blocked from proceeding and a problem report and repair suggestions are generated.

[0208] 8. Product archiving and traceability

[0209] Verified software artifacts are uniformly archived in the artifact repository, generating complete traceable files. The files include build information, test results, quality access status, version signatures, and release records.

[0210] In specific implementation, the traceable archive may include:

[0211] (8.1) Basic identification information of products

[0212] Used to uniquely identify a software artifact, including but not limited to:

[0213] Unique identifier for the product;

[0214] Product name and type;

[0215] Project or product model identifier;

[0216] Product production time;

[0217] This type of information is used to distinguish different product instances and support version-level traceability.

[0218] (8.2) Construct execution information

[0219] Used to record the build source and build environment of software artifacts, including but not limited to:

[0220] The code commit or model version identifier that triggered the build;

[0221] Build execution machine and tool version information;

[0222] Assign task number and execution status;

[0223] Build log index information;

[0224] The above information is used to support the reproducibility of the build process and the backtracking of issues.

[0225] (8.3) Test and verification results information

[0226] Used to record the testing status of software artifacts at each verification stage, including but not limited to:

[0227] Unit test and integration test results;

[0228] Simulation verification results and key performance indicators;

[0229] Prototype verification test results;

[0230] Test time and execution environment identifiers for each stage;

[0231] This type of information is used to support integrity verification in multi-stage validation.

[0232] (8.4) Quality access control status information

[0233] Used to reflect the quality control status of software artifacts in the production line, including but not limited to:

[0234] The judgment results of each quality access control point;

[0235] The rule identifier on which the judgment is based;

[0236] Records and processing status of blocked access when access is denied;

[0237] Manual review of intervention records;

[0238] The above information is used to demonstrate whether the software product meets established quality and safety standards.

[0239] (8.5) Version Signature and Security Verification Information

[0240] Used to ensure the integrity and tamper-proof nature of software artifacts, including but not limited to:

[0241] Digital signature information;

[0242] Hash check value;

[0243] Signature algorithm and verification status;

[0244] This type of information is used to meet the software security requirements of engineering machinery products.

[0245] (8.6) Publishing and circulating information

[0246] Used to record the usage and circulation status of software artifacts, including but not limited to:

[0247] Whether it has been approved for release;

[0248] Corresponding application scenarios (prototype, mass production, small batch production, etc.);

[0249] Filling or deployment records;

[0250] Release of approval information and timing;

[0251] This type of information supports the traceability of software products during the production and service stages.

[0252] (8.7) Related Reference Information

[0253] Used to record the relationships between the software artifact and other R&D assets, including but not limited to:

[0254] Related software requirements or design identifiers;

[0255] Related test cases and defect records;

[0256] The associated hardware configuration or controller model;

[0257] Ensure the formation of a complete traceability chain across systems and stages.

[0258] By linking and archiving the above information in the form of a data model, traceability management of engineering machinery software products from construction and verification to release is realized, providing reliable data support for software quality auditing, problem backtracking, and compliance verification.

[0259] Based on the above analysis, this invention addresses the problems in software development for engineering machinery products, such as fragmented toolchains, incomplete verification processes, lack of quality gates, insufficient hardware-software collaboration, and difficulties in version traceability. It proposes a continuous integration automated pipeline method integrating Simulink and Codesys, achieving automated and intelligent management of the entire process of engineering machinery control software, from code (model) submission, compilation and construction, testing and verification, to product archiving. Compared to existing technologies, this invention has the following significant advantages:

[0260] 1. Achieve toolchain integration and automated collaboration specifically for the engineering machinery field.

[0261] This invention enables deep integration of Simulink and Codesys, two mainstream software development tools for engineering machinery, into a unified automated pipeline (specifically, integrated into the build and artifact generation modules; the pipeline can call Simulink and Codesys tools on the server when it needs to perform compilation and build), opening up data pathways and achieving automated build and result synchronization. The system can automatically trigger build tasks after code or model updates without manual intervention, effectively solving the problems of model and logic disconnect and process fragmentation in existing development, and significantly improving the consistency and automation of software development.

[0262] 2. Construct a multi-stage verification closed loop to improve software reliability and consistency.

[0263] This invention integrates a multi-stage automated verification module. Each stage has independent test tasks, quality gates, and verification baselines to ensure that the control algorithm undergoes systematic verification from model to actual operation. This step-by-step verification mechanism can detect integration problems early, reduce the risk of systemic failures, and improve the reliability of software in engineering machinery products.

[0264] 3. Introduce a mandatory quality access control mechanism to achieve process controllability and safety compliance.

[0265] This invention establishes multi-dimensional quality gates, including model consistency checks, static code analysis, and test coverage checks. The process is automatically interrupted if any gate fails, preventing it from proceeding to the next stage and preventing low-quality versions from entering the production stage. This mechanism strengthens the security and quality control capabilities of software development, ensuring that the output meets industry safety and compliance requirements.

[0266] 4. Establish a full lifecycle traceability system for products.

[0267] This invention achieves end-to-end traceability from model, source code, build artifacts to the final release version through artifact digital signatures, hash verification, and version archive mechanisms. Each artifact has a unique identifier, associated with build logs, test reports, access control results, and release records, supporting rapid location of historical versions and dependencies, and providing complete evidence for software maintenance, quality analysis, and security auditing.

[0268] 5. Achieve AI-driven automated analysis and intelligent diagnosis

[0269] This invention introduces an AI-powered intelligent analysis module to automatically analyze and locate the root causes of automated pipeline operation logs, test data, and anomalies. Based on historical execution data, the system performs trend prediction and error classification, automatically generating repair suggestions or triggering retry builds. This significantly improves the intelligence level of automated pipeline operation, shortens the problem-solving cycle, reduces manual analysis costs, and enhances the overall stability and self-healing capabilities of the system.

[0270] 6. Improve development efficiency and team collaboration capabilities

[0271] Through event-driven automated execution mechanisms, developers can receive rapid feedback on build and test results immediately after submitting code, reducing communication and waiting costs. Unified automated pipeline templates and access control rules ensure that all projects follow a consistent development process, thereby improving cross-team collaborative development efficiency and achieving standardized and systematic management of the software development process in engineering machinery enterprises.

[0272] 7. Enhance product competitiveness and sustainable innovation capabilities

[0273] This invention establishes a highly reliable software development system for the construction machinery industry, providing fundamental support for enterprises to achieve intelligent and digital R&D. This system is reusable and continuously optimized, supporting enterprises in achieving a strategic transformation towards "software-defined construction machinery," significantly improving product market responsiveness and core competitiveness.

[0274] Example 3

[0275] This invention provides a continuous integration system suitable for software in engineering machinery products, including a storage medium and a processor;

[0276] The storage medium is used to store instructions;

[0277] The processor is configured to operate according to the instructions to execute the method according to any one of Embodiment 1.

[0278] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0279] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0280] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0281] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0282] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

[0283] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A continuous integration method for software in engineering machinery products, characterized in that, include: Based on the obtained version change event, select the appropriate pipeline template according to preset rules and generate pipeline execution tasks; Based on the software version information, configuration parameters, and build strategy carried in the pipeline execution task, a software artifact is generated; Based on the quality judgment criteria defined in the pipeline execution task, the build logs, build status and artifact data generated during the software artifact generation process are judged for quality, and the pipeline execution task is continued or terminated based on the quality judgment results. Based on the verification strategy defined in the pipeline execution task, the software artifact is automatically verified and verification results are generated. Based on the quality judgment criteria defined in the pipeline execution task, the verification results are judged for quality, and the pipeline execution task is continued or terminated based on the quality judgment results. Software artifacts that have passed automated verification are archived and managed in a unified manner, and the archive completion status is returned, marking the end of one continuous integration pipeline execution process.

2. The continuous integration method for software of engineering machinery products according to claim 1, characterized in that: The process of selecting an appropriate pipeline template based on the acquired version change event according to preset rules and generating pipeline execution tasks includes: When a code commit, model update, or version merge event is detected, the appropriate pipeline template is selected according to preset rules, and a pipeline execution task is generated. The pipeline execution tasks include software version information, configuration parameters and build strategies, verification strategies and quality judgment criteria.

3. A continuous integration method for software of engineering machinery products according to claim 1 or 2, characterized in that: The method for generating the software artifact includes: Based on the software version information, configuration parameters, and build strategy carried in the pipeline execution task, the corresponding software source files and model files are obtained from the version control repository, and automatic compilation, dependency resolution, and artifact packaging operations are performed to obtain the software artifact.

4. The continuous integration method for software of engineering machinery products according to claim 1, characterized in that: The step of deciding whether to continue or terminate the pipeline execution task based on the quality judgment result includes: When the quality assessment results determine that the current stage results meet the release conditions, continue executing the steps that have not yet been completed in the current pipeline task. If the quality assessment results indicate that the current stage does not meet the release conditions, then the unfinished steps in the current production line task should be terminated immediately.

5. The continuous integration method for software of engineering machinery products according to claim 1, characterized in that: The continuous integration method further includes: After generating the pipeline execution task, a unique pipeline instance identifier is created, and the corresponding log context is initialized. The log context is used to identify the execution process of this pipeline task. During the pipeline execution of task generation, automated verification, and quality judgment, the start time, end time, execution node identifier, and abnormal information generated by quality judgment of each process are automatically recorded to form a structured stage log; quality backtracking analysis is performed based on the structured stage log; The fault causes are identified based on the structured stage logs, and repair suggestions are generated.

6. The continuous integration method for software of engineering machinery products according to claim 1, characterized in that: In the automated verification process of the software artifact, each verification stage is an independent execution node in the pipeline. If the previous verification stage fails, the execution of the subsequent verification stage will be automatically terminated. The verification results of each verification stage are used to compare with the quality judgment criteria to generate a quality judgment result. Based on the quality judgment result, it is decided whether to continue or terminate the execution of the pipeline task.

7. The continuous integration method for software of engineering machinery products according to claim 1, characterized in that: The pipeline template defines the execution stages, execution order, triggering conditions, and quality judgment criteria of the pipeline in a parameterized manner, including: Basic identification parameters for the production line, used to uniquely identify and manage production line templates; Triggering and adaptation parameters are used to describe the triggering conditions and adaptation rules of the pipeline template; The execution phase definition parameters are used to define the execution phases and execution order contained in the pipeline template; Stage execution control parameters are used to describe the specific execution method of each execution stage; Verification strategy parameters are used to define the rules related to automated verification; Quality access control parameters are used to define the nodes in the pipeline template that are required to perform quality checks, and to control whether the pipeline is allowed to proceed to the next execution stage. Intelligent analysis of related parameters supports subsequent intelligent diagnosis and continuous optimization.

8. A continuous integration device suitable for software in engineering machinery products, characterized in that, include: The triggering and task scheduling module, based on the obtained version change event, selects the appropriate pipeline template according to preset rules and generates pipeline execution tasks; The build and artifact generation module is used to generate software artifacts based on the software version information, configuration parameters and build strategies carried in the pipeline execution tasks; A multi-stage automated verification module is used to automatically verify the software artifacts based on the verification strategy defined in the pipeline execution task and generate verification results. The quality access control module is used to perform quality judgment on the build logs, build status and artifact data generated during the software artifact generation process based on the quality judgment criteria defined in the pipeline execution task, and decide whether to continue or terminate the execution of the pipeline execution task based on the quality judgment result. Furthermore, based on the quality judgment criteria defined in the pipeline execution task, the verification results are judged for quality, and the pipeline execution task is continued or terminated based on the quality judgment results. The artifact management and traceability module is used to uniformly archive and manage software artifacts that have passed automated verification, and return the archiving completion status, marking the end of a continuous integration pipeline execution process.

9. A continuous integration device for software of engineering machinery products according to claim 8, characterized in that, The continuous integration device also includes: The pipeline execution log generation and management module is used to create a unique pipeline instance identifier and initialize the corresponding log context after generating a pipeline execution task, which is used to identify the execution process of this pipeline task. During the pipeline execution task generation, automated verification, and quality judgment process, it automatically records the start time, end time, execution node identifier, and abnormal information generated by quality judgment for each process, forming a structured stage log. The intelligent analysis and fault diagnosis module is used to identify fault causes and generate repair suggestions based on the structured stage logs in the pipeline execution log generation and management module. The product management and traceability module is also connected to the production line execution log generation and management module, which is used for quality backtracking analysis based on structured stage logs.

10. A continuous integration system suitable for software in engineering machinery products, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the method according to any one of claims 1-7.

Images