Continuous integration method, device and system for vehicle electronic control software

Abstract

The invention discloses a continuous integration method, device and system for vehicle electronic control software, and relates to the technical field of vehicle software development, the continuous integration method for the vehicle electronic control software is applied to an integration server, and the method comprises the following steps: responding to an integration task request, and reading version number information in a collaborative management platform according to current incoming parameters; updating a file version of a local warehouse according to the version number information to obtain an updated file version, and sending the updated file version to a source code management platform, so that the source code management platform feeds back a model code file according to the updated file version, the model code file is generated and obtained through a generation server by sending the update file version to the generation server by the source code management platform; and performing integration according to the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file. And the quality and research and development efficiency of automobile embedded software products are improved.

Description

Technical Field

[0001] The present application relates to the technical field of automobile software development, and in particular to a method, device and system for continuous integration of vehicle electronic control software. Background Art

[0002] In the process of automotive electronic control software development, for projects with complex structures, traditional manual operations are obviously not suitable for integrated testing and are inefficient. In addition, version errors and configuration errors are likely to occur during the preparation process. These human factors cause software problems that are not conducive to software testing and are more likely to bring serious consequences. Therefore, how to solve the low quality and R&D efficiency of automotive embedded software products has become an urgent problem to be solved. Summary of the invention

[0003] The main purpose of this application is to provide a method, device and system for continuous integration of vehicle electronic control software, aiming to solve the technical problems of low quality and R&D efficiency of automotive embedded software products.

[0004] To achieve the above-mentioned purpose, the present application proposes a continuous integration method for vehicle electronic control software, which is applied to an integration server and includes: Respond to the integration task request and read the version number information in the collaborative management platform according to the current input parameters; The file version of the local warehouse is updated according to the version number information to obtain an updated file version, and the updated file version is sent to the source code management platform, so that the source code management platform feeds back a model code file according to the updated file version, wherein the model code file is generated by the generation server when the source code management platform sends the updated file version to the generation server; Integration is performed according to the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

[0005] In one embodiment, the step of integrating the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file includes: Updating the integrated code version according to the model code file to obtain a version update status; When the version update status is an update completion status, obtaining a basic service file in a source code management platform; Integration is performed according to the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

[0006] In one embodiment, the step of responding to the integration task request and reading the version number information in the collaborative management platform according to the current input parameters includes: Respond to integration task requests and determine parameter update types based on current incoming parameters; The version number information in the collaborative management platform is read according to the parameter update type.

[0007] In one embodiment, after integrating the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file, the method further includes: Sending the integrated intermediate file to a source code management platform so that the source code management platform stores the integrated intermediate file; The integration target file is sent to a continuous integration platform, so that the continuous integration platform stores the integration target file.

[0008] To achieve the above-mentioned purpose, the present application proposes a continuous integration method for vehicle electronic control software, which is applied to a generation server and includes: Get updated file versions sent by the source code management platform; The generated code version is updated according to the update file version to obtain the current update status; When the current update state is an update completion state, a model code file is generated according to the initial model file, and the model code file is sent to a source code management platform for integration according to the model code file.

[0009] In one embodiment, when the current update state is the update completion state, the step of generating a model code file according to the initial model file includes: When the current update state is an update completion state, identifying the initial model file and determining a model identification result; Determine the corresponding target application layer model according to the model recognition result; A model code file is generated according to the target application layer model.

[0010] To achieve the above objectives, the present application proposes a continuous integration method for vehicle electronic control software, which is applied to a continuous integration platform and includes: Obtain user login information, verify the user login information, and determine the user verification status; When the user verification status is a verification passed status, an integration task request is initiated to an integration server based on a parameterized interface to perform continuous integration.

[0011] In one embodiment, obtaining a target integration result and an integration log file; A target mail file is generated according to a preset mail template, the target integration result and the integration log file, and the target mail file is sent to the user.

[0012] In addition, to achieve the above-mentioned purpose, the present application also proposes a continuous integration device for vehicle electronic control software, the continuous integration device for vehicle electronic control software comprising: The response module is used to respond to the integration task request and read the version number information in the collaborative management platform according to the current input parameters; An update module, used to update the file version of the local warehouse according to the version number information to obtain an updated file version, and send the updated file version to the source code management platform, so that the generation server generates a model code file according to the updated file version in the source code management platform; The integration module is used to integrate the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

[0013] In addition, to achieve the above-mentioned purpose, the present application also proposes a continuous integration device for vehicle electronic control software, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the continuous integration method for vehicle electronic control software as described above.

[0014] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the continuous integration method of vehicle electronic control software as described above are implemented.

[0015] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the continuous integration method of vehicle electronic control software as described above.

[0016] In addition, to achieve the above-mentioned purpose, the present application also provides a continuous integration system for vehicle electronic control software, characterized in that the data transmission system includes the integration server, generation server and continuous integration platform as described above.

[0017] This application responds to the integration task request and reads the version number information in the collaborative management platform according to the current input parameters; updates the file version of the local warehouse according to the version number information to obtain the updated file version, and sends the updated file version to the source code management platform, so that the source code management platform can feedback the model code file according to the updated file version, and the model code file is generated by the source code management platform sending the updated file version to the generation server; integrates according to the model code file and the basic service file to obtain the integrated intermediate file and the integrated target file. Improve the quality and R&D efficiency of automotive embedded software products. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1 A flowchart of the continuous integration method of vehicle electronic control software applied to an integrated server according to the first embodiment of the present application; Figure 2 The overall flow diagram provided for the first embodiment of the continuous integration method of vehicle electronic control software applied to the integrated server of the present application; Figure 3 A flow chart of a first embodiment of a method for continuous integration of vehicle electronic control software applied to a server in the present application; Figure 4 A flow chart of a first embodiment of a continuous integration method for vehicle electronic control software applied to a continuous integration platform of the present application; Figure 5 A brief flowchart of the continuous integration method of vehicle electronic control software provided in Example 1 of the present application; Figure 6 A schematic diagram of the module structure of a continuous integration device for vehicle electronic control software according to an embodiment of the present application; Figure 7 Schematic diagram of the device structure of the hardware operating environment involved in the continuous integration method of vehicle electronic control software in the embodiment of the present application.

[0021] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0022] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0023] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0024] The main solution of the embodiment of the present application is: responding to the integration task request, and reading the version number information in the collaborative management platform according to the current incoming parameters; updating the file version of the local warehouse according to the version number information to obtain the updated file version, and sending the updated file version to the source code management platform, so that the source code management platform can feedback the model code file according to the updated file version, and the model code file is generated by the generation server when the source code management platform sends the updated file version to the generation server; integrating according to the model code file and the basic service file to obtain the integrated intermediate file and the integrated target file.

[0025] In the process of automotive electronic control software development, for projects with complex structures, traditional manual operations are obviously not suitable for integrated testing and are inefficient. In addition, version errors and configuration errors are likely to occur during the preparation process. These human factors cause software problems that are not conducive to software testing and are more likely to bring serious consequences. Therefore, how to solve the low quality and R&D efficiency of automotive embedded software products has become an urgent problem to be solved.

[0026] This application responds to the integration task request and reads the version number information in the collaborative management platform according to the current input parameters; updates the file version of the local warehouse according to the version number information to obtain the updated file version, and sends the updated file version to the source code management platform, so that the source code management platform can feedback the model code file according to the updated file version, and the model code file is generated by the source code management platform sending the updated file version to the generation server; integrates according to the model code file and the basic service file to obtain the integrated intermediate file and the integrated target file. Improve the quality and R&D efficiency of automotive embedded software products.

[0027] Based on this, the embodiment of the present application provides a method for continuous integration of vehicle electronic control software, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the continuous integration method of vehicle electronic control software of the present application.

[0028] In this embodiment, the continuous integration method of the vehicle electronic control software is applied to an integration server, and the method includes steps S10 to S30: Step S10, responding to the integration task request, and reading the version number information in the collaborative management platform according to the current input parameters; It should be noted that if Figure 2 As shown, this embodiment uses the SystemWeaver collaborative management platform and SCM source code management platforms such as Gitlab, Mercurial, and SVN to implement a method for continuous integration of automotive electronic control software: Application Software (ASW) developers and Basic The developers of BSW (Building Software) push the model files and basic service files of the simulation software to the SCM source code management platform respectively; the developers update the correctly pushed version number and other information to the SystemWeaver collaborative management platform; when the developers confirm that the update is complete, the software integrator enters the Jenkins continuous integration platform and initiates the integration task through the parameterized interface; when the Jenkins task is triggered, the proxy server responsible for the integration task reads the version number one by one from the SystemWeaver collaborative management platform based on the input parameters and updates the version of the local warehouse, and pushes it to the SCM source code management platform after the update is completed; the proxy server responsible for model code generation is updated to the latest code version, identifies all application layer models in the integration project, generates model codes respectively, and pushes them to the SCM source code management platform after the generation is completed; the proxy server responsible for the integration task is updated to the latest code version, integrates and compiles the model code and the underlying service files, and pushes the generated intermediate files and target files to the SCM source code management platform after the integration is completed; the integration results and integration process logs are sent to relevant personnel in the form of emails.

[0029] It can be understood that the executor of this embodiment is the proxy server responsible for the integration task. The integration task request refers to the integration task initiated by the user through the Jenkins continuous integration platform. The current incoming parameters include the item number of the corresponding project in SystemWeaver, whether to ignore errors in updating the local warehouse, the number of concurrent model code generation, whether to ignore the generated model code, whether to ignore errors in model code generation, the basic version number of this integration, whether to clean up the last temporary files before integration, and other special parameters of the project itself. The version number information refers to the version number corresponding to the model file and basic service file of the simulation software.

[0030] In the specific implementation, when the integration task initiated by the user through the Jenkins continuous integration platform is received, the version number corresponding to the model file and the basic service file of the simulation software in the SystemWeaver collaborative management platform is read according to the item number of the corresponding project in SystemWeaver, whether to ignore errors in updating the local warehouse, the number of concurrent model code generation, whether to ignore the generated model code, whether to ignore errors in model code generation, the basic version number of this integration, whether to clean up the last temporary files before integration, and other special parameters of the project itself, so as to obtain the version number information, wherein the SystemWeaver collaborative management platform saves the version numbers of each module including ASW and BSW in the required integration and the corresponding warehouse addresses in the SCM source code management platform.

[0031] In a feasible implementation, step S10 may include steps A11-A12: Step A11, responding to the integration task request and determining the parameter update type according to the current input parameters; It is understandable that parameter update types include incremental update and full update.

[0032] In the specific implementation, after responding to the integration task initiated by the user through the Jenkins continuous integration platform, the parameter update type is determined according to the item number of the corresponding project in SystemWeaver, whether to ignore errors in updating the local warehouse, the number of concurrent model code generation, whether to ignore the generated model code, whether to ignore errors in model code generation, the basic version number of this integration, whether to clean up the last temporary files before integration, and other special parameters of the project itself. Specifically, this embodiment can realize incremental update and full update of the model code by passing in different parameters, control the server load required for the integration task, and whether to ignore integration errors.

[0033] Step A12: read the version number information in the collaborative management platform according to the parameter update type.

[0034] In the specific implementation, the corresponding version number information in the SystemWeaver collaborative management platform is read according to the determined parameter update type (incremental update and full update). That is, when the Jenkins task is triggered, the proxy server responsible for the integration task reads the version number one by one from the SystemWeaver collaborative management platform based on the incoming parameters and updates the version of the local warehouse. After the update is completed, it is pushed to the SCM source code management platform.

[0035] Step S20, updating the file version of the local warehouse according to the version number information to obtain an updated file version, and sending the updated file version to the source code management platform, so that the source code management platform feeds back a model code file according to the updated file version, wherein the model code file is generated by the generation server when the source code management platform sends the updated file version to the generation server; It can be understood that updating the file version refers to the file version obtained by updating the local repository, the source code management platform refers to the SCM (Source Code Management) platform, where the SCM source code management platform includes common SCM source code management platforms such as Mercurial, SVN, and Gitlab, and the model code file refers to the generated application layer model code file.

[0036] In a specific implementation, the file version of the local warehouse of the proxy server responsible for the integration task is updated according to the version numbers corresponding to the model files and basic service files of the simulation software, and the file version obtained by updating the local warehouse is sent to the source code management platform, so that the source code management platform can feedback the generated application layer model code file to the proxy server responsible for the integration task, wherein the generated application layer model code file is generated by the proxy server responsible for model code generation.

[0037] Step S30, integrating the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

[0038] It can be understood that the basic service file refers to the underlying service file developed by the BSW underlying developers, the intermediate file refers to the C++ file generated by the basic service file, and the target files include S19, ARL, elf and map, etc.

[0039] In the specific implementation, the proxy server responsible for the integration task is updated to the latest code version, and the model code and underlying service files are integrated and compiled. After the integration is completed, the generated intermediate files and target files are pushed to the SCM source code management platform.

[0040] In a feasible implementation, step S30 may include steps A31 to A33: Step A31, updating the integrated code version according to the model code file to obtain a version update status; It can be understood that the integrated code version refers to the code version of the proxy server responsible for the integration task, and the version update status includes an update completion status and an update incomplete status.

[0041] In the specific implementation, in order to carry out the integration task, the proxy server responsible for the integration task needs to be updated to the latest code version. Specifically, the proxy server responsible for the integration task obtains the generated application layer model code file through the SCM source code management platform, and then updates the code version of the proxy server responsible for the integration task according to the generated application layer model code file, and finally obtains the version update status.

[0042] Step A32, when the version update status is the update completion status, obtaining the basic service file in the source code management platform; It can be understood that when the version update status is the update completion status, it indicates that the proxy server responsible for the integration task can perform the integration task, and then read the underlying service files developed by the BSW underlying developers in the SCM source code management platform to perform the integration task according to the underlying service files developed by the BSW underlying developers.

[0043] Step A33, integrating the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

[0044] It can be understood that the model code and the underlying service files are integrated and compiled to obtain intermediate files and target files, and after the integration is completed, the generated intermediate files and target files are pushed to the SCM source code management platform.

[0045] In a feasible implementation manner, step S30 may include steps B31 to B32: Step B31, sending the integrated intermediate file to a source code management platform, so that the source code management platform stores the integrated intermediate file; It is understandable that after the integration is completed, the integrated intermediate file is sent to the SCM source code management platform so that the integrated intermediate file is saved through the SCM source code management platform.

[0046] Step B32: sending the integration target file to the continuous integration platform so that the continuous integration platform stores the integration target file.

[0047] In a specific implementation, after the integration is completed, the integration target file is sent to the Jenkins continuous integration platform, so that the Jenkins continuous integration platform saves the integration target file.

[0048] This embodiment responds to the integration task request and reads the version number information in the collaborative management platform according to the current input parameters; updates the file version of the local warehouse according to the version number information to obtain the updated file version, and sends the updated file version to the source code management platform, so that the source code management platform can feedback the model code file according to the updated file version, and the model code file is generated by the source code management platform sending the updated file version to the generation server; integrates according to the model code file and the basic service file to obtain the integrated intermediate file and the integrated target file. The quality and R&D efficiency of automotive embedded software products are improved.

[0049] In the first embodiment of the present application applied to the generation server, the same or similar contents as those in the above-mentioned embodiment 1 applied to the integration server can be referred to the above introduction, and will not be repeated in the following. Figure 3 The continuous integration method of the vehicle electronic control software is applied to a generation server, and the method comprises steps S11 to S13: Step S11, obtaining the updated file version sent by the source code management platform; It can be understood that the execution subject of this embodiment is a proxy server responsible for model code generation.

[0050] In a specific implementation, the proxy server responsible for model code generation reads the file version obtained by updating the local warehouse in the SCM source code management platform to perform version update according to the file version obtained by updating the local warehouse.

[0051] Step S12, updating the generated code version according to the update file version to obtain the current update status; It can be understood that the generated code version refers to the code version of the proxy server responsible for model code generation, and the current update status refers to the version update status of the proxy server responsible for model code generation.

[0052] In the specific implementation, in order to generate the code file of the application layer model, it is necessary to update the code version of the proxy server responsible for model code generation, and then update the version according to the file version obtained by reading the updated local warehouse, and finally obtain the current update status.

[0053] Step S13, when the current update state is the update completion state, generating a model code file according to the initial model file, and sending the model code file to the source code management platform for integration according to the model code file.

[0054] It can be understood that the initial model file refers to the model file of the simulation software developed by the ASW application developer.

[0055] In a specific implementation, when the previous update status is the update completion status, it indicates that the proxy server responsible for model code generation can generate code files, and then generate corresponding application layer model code files according to the model files of the simulation software developed by the ASW application developers, and send the application layer model code files to the SCM source code management platform to perform integration tasks according to the application layer model code files.

[0056] In a feasible implementation, step S13 may include steps A131 to A133: Step A131, when the current update state is the update completion state, identifying the initial model file and determining the model identification result; It can be understood that the model recognition result refers to the recognition result of the application layer model.

[0057] In the specific implementation, when the current update status is the update completion status, the proxy server responsible for model code generation can generate the code file, and then identify the model file of the simulation software developed by the ASW application developers to identify all application layer models, that is, to obtain the model recognition result.

[0058] Step A132, determining the corresponding target application layer model according to the model recognition result; It can be understood that the target application layer model refers to all application layer models, and all application layer models, namely the target application layer model, are determined based on the recognition results of the model files of the simulation software developed by the ASW application developers.

[0059] Step A133, generating a model code file according to the target application layer model.

[0060] In a specific implementation, corresponding model code files are generated according to all identified application layer models through a proxy server responsible for model code generation.

[0061] This embodiment obtains the update file version sent by the source code management platform; updates the generated code version according to the update file version to obtain the current update status; when the current update status is the update completion status, generates a model code file according to the initial model file, and sends the model code file to the source code management platform to be integrated according to the model code file. Through the above method, the problem of low quality and R&D efficiency of automotive embedded software products is solved.

[0062] In the first embodiment of the present application applied to the continuous integration platform, the same or similar contents as those in the above-mentioned embodiment 1 applied to the integration server and / or embodiment 1 applied to the generation server can be referred to the above introduction and will not be described in detail later. Figure 4 The continuous integration method of the vehicle electronic control software is applied to the continuous integration platform, and the method comprises steps S21-S22: Step S21, obtaining user login information, verifying the user login information, and determining the user verification status; It can be understood that the execution subject of this embodiment is the Jenkins continuous integration platform, the user login information refers to the information of the user logging into the Jenkins continuous integration platform, and the user verification status includes the verification pass status and the verification fail status.

[0063] In the specific implementation, in order to initiate the integration task, the software integrator needs to enter the Jenkins continuous integration platform, and then obtain the user's login information to the Jenkins continuous integration platform, and verify the user's login information to the Jenkins continuous integration platform, and finally obtain the user verification status.

[0064] Step S22: when the user verification status is a verification passed status, an integration task request is initiated to an integration server based on a parameterized interface to perform continuous integration.

[0065] It is understandable that the parameterized interface refers to the Pipeline pipeline interface of Jenkins.

[0066] In the specific implementation, when the user verification status is the verification passed status, it indicates that the software integrator has successfully entered the Jenkins continuous integration platform, and then initiated an integration task request to the integration server through the Jenkins Pipeline interface, so that the integration server responds to the integration task for continuous integration.

[0067] In a feasible implementation manner, step S22 may include steps A221 to A222: Step A221, obtaining target integration results and integration log files; It can be understood that the target integration result refers to the result of whether the integration task is completed, and the integration log file refers to the errors, warnings, debugging information, etc. during the integration task.

[0068] In the specific implementation, after completing the integration task, in order to notify the relevant personnel of the integration results, the Jenkins continuous integration platform obtains the results of whether the integration task is completed and the errors, warnings, debugging information, etc. during the integration task.

[0069] Step A221: Generate a target mail file according to a preset mail template, the target integration result and the integration log file, and send the target mail file to the user.

[0070] In the specific implementation, the preset email template refers to the template of the pre-set notification email, and the target email file refers to the email used to notify relevant personnel of the integration results. The result of whether the integration task is completed and the errors, warnings, debugging information, etc. in the integration task process are filled into the pre-set notification email template to obtain the target email file, and finally the target email file is sent to the relevant personnel.

[0071] This embodiment obtains user login information and verifies the user login information to determine the user verification status; when the user verification status is a verification pass status, an integration task request is initiated to the integration server based on a parameterized interface to perform continuous integration. Through the above method, the problem of low quality and R&D efficiency of automotive embedded software products is solved.

[0072] For example, to help understand the implementation process of the continuous integration method of vehicle electronic control software obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 5 , Figure 5 A brief flow chart of the continuous integration method of vehicle electronic control software is provided, specifically: S1, ASW application developers and BSW bottom-level developers push the model files and basic service files of the simulation software to the SCM source code management platform respectively; S2, developers update the correctly pushed version number and other information to the SystemWeaver collaborative management platform; S3, when the developer confirms that the update is complete, the software integrator enters the Jenkins continuous integration platform and initiates the integration task through the parameterized interface; S4, when the Jenkins task is triggered, the proxy server responsible for the integration task receives the SystemWeaver package from the SystemWeaver package based on the input parameters ver collaborative management platform reads the version number one by one and updates the version of the local warehouse. After the update is completed, it is pushed to the SCM source code management platform; S5. The proxy server responsible for model code generation is updated to the latest code version, identifies all application layer models in the integration project, generates model codes respectively, and pushes them to the SCM source code management platform after the generation is completed; S6. The proxy server responsible for the integration task is updated to the latest code version, integrates and compiles the model code and the underlying service files, and pushes the generated intermediate files and target files to the SCM source code management platform after the integration is completed; S7. The integration results and integration process logs are sent to relevant personnel in the form of emails.

[0073] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the continuous integration method of the vehicle electronic control software of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0074] This application also provides a continuous integration device for vehicle electronic control software, please refer to Figure 6The continuous integration device of the vehicle electronic control software is applied to the integration server, and the device comprises: The response module 10 is used to respond to the integration task request and read the version number information in the collaborative management platform according to the current input parameters; An updating module 20, configured to update the file version of the local repository according to the version number information to obtain an updated file version, and send the updated file version to the source code management platform, so that the generation server generates a model code file according to the updated file version in the source code management platform; The integration module 30 is used to perform integration according to the model code file and the basic service file to obtain an integration intermediate file and an integration target file.

[0075] Optionally, the integrated module 30 is further used for: Updating the integrated code version according to the model code file to obtain a version update status; When the version update status is an update completion status, obtaining a basic service file in a source code management platform; Integration is performed according to the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

[0076] Optionally, the response module 10 is further configured to: Respond to integration task requests and determine parameter update types based on current incoming parameters; The version number information in the collaborative management platform is read according to the parameter update type.

[0077] Optionally, the integrated module 30 is further used for: Sending the integrated intermediate file to a source code management platform so that the source code management platform stores the integrated intermediate file; The integration target file is sent to a continuous integration platform, so that the continuous integration platform stores the integration target file.

[0078] The present application also provides a continuous integration device for vehicle electronic control software, the continuous integration device for vehicle electronic control software is applied to a generation server, and the device includes: The acquisition module 101 is used to acquire the update file version sent by the source code management platform; An updating module 102, used to update the generated code version according to the update file version to obtain a current update status; The generation module 103 is used to generate a model code file according to the initial model file when the current update state is the update completion state, and send the model code file to the source code management platform for integration according to the model code file.

[0079] Optionally, the generating module 103 is further used to: When the current update state is an update completion state, identifying the initial model file and determining a model identification result; Determine the corresponding target application layer model according to the model recognition result; A model code file is generated according to the target application layer model.

[0080] The present application also provides a continuous integration device for vehicle electronic control software, the continuous integration device for vehicle electronic control software is applied to a continuous integration platform, and the device includes: Verification module 201, used to obtain user login information, verify the user login information, and determine the user verification status; The initiating module 202 is used to initiate an integration task request to the integration server based on the parameterized interface to perform continuous integration when the user verification status is a verification passed status.

[0081] Optionally, the initiating module 202 is further configured to: Get the target integration results and integration log files; A target mail file is generated according to a preset mail template, the target integration result and the integration log file, and the target mail file is sent to the user.

[0082] The continuous integration device for vehicle electronic control software provided by the present application adopts the continuous integration method for vehicle electronic control software in the above embodiment, which can solve the technical problems of low quality and R&D efficiency of automotive embedded software products. Compared with the prior art, the beneficial effects of the continuous integration device for vehicle electronic control software provided by the present application are the same as the beneficial effects of the continuous integration method for vehicle electronic control software provided by the above embodiment, and other technical features in the continuous integration device for vehicle electronic control software are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0083] The present application provides a continuous integration device for vehicle electronic control software, the continuous integration device for vehicle electronic control software includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the continuous integration method for vehicle electronic control software in the above-mentioned embodiment one.

[0084] Reference below Figure 7, which shows a schematic diagram of the structure of a continuous integration device for vehicle electronic control software suitable for implementing the embodiment of the present application. The continuous integration device for vehicle electronic control software in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The continuous integration device for vehicle electronic control software shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0085] like Figure 7 As shown, the continuous integration device of vehicle electronic control software may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to the program stored in a read-only memory (ROM: Read Only Memory) 1002 or the program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the continuous integration device of vehicle electronic control software are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the continuous integration device of the vehicle electronic control software to communicate wirelessly or wired with other devices to exchange data. Although the continuous integration device of the vehicle electronic control software with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have alternatively.

[0086] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0087] The continuous integration device for vehicle electronic control software provided by the present application adopts the continuous integration method for vehicle electronic control software in the above embodiment, which can solve the technical problems of low quality and R&D efficiency of automotive embedded software products. Compared with the prior art, the beneficial effects of the continuous integration device for vehicle electronic control software provided by the present application are the same as the beneficial effects of the continuous integration method for vehicle electronic control software provided by the above embodiment, and the other technical features in the continuous integration device for vehicle electronic control software are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0088] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0089] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0090] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the continuous integration method of vehicle electronic control software in the above-mentioned embodiment.

[0091] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0092] The computer-readable storage medium may be included in the continuous integration device of the vehicle electronic control software; or may exist independently without being assembled into the continuous integration device of the vehicle electronic control software.

[0093] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the continuous integration device of the vehicle electronic control software, the continuous integration device of the vehicle electronic control software: responds to the integration task request, and reads the version number information in the collaborative management platform according to the current input parameters; updates the file version of the local warehouse according to the version number information to obtain the updated file version, and sends the updated file version to the source code management platform, so that the source code management platform can feedback the updated model code file according to the updated file version, and the updated model code file is generated by the generation server when the source code management platform sends the updated file version to the generation server; integrates according to the model code file and the basic service file to obtain the integrated intermediate file and the integrated target file.

[0094] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0095] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0096] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0097] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned method for continuous integration of vehicle electronic control software, and can solve the technical problems of low quality and R&D efficiency of automotive embedded software products. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the method for continuous integration of vehicle electronic control software provided in the above-mentioned embodiment, and will not be described in detail here.

[0098] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the continuous integration method of vehicle electronic control software as described above.

[0099] The computer program product provided by this application can solve the technical problems of low quality and R&D efficiency of automotive embedded software products. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the continuous integration method of vehicle electronic control software provided by the above embodiment, which will not be repeated here.

[0100] In addition, to achieve the above objectives, the present invention also proposes a continuous integration system for vehicle electronic control software, which includes the integration server, generation server and continuous integration platform mentioned above.

[0101] Since the continuous integration system of the vehicle electronic control software adopts all the technical solutions of all the above-mentioned embodiments, it has at least all the beneficial effects brought by the technical solutions of the above-mentioned embodiments, which will not be described one by one here.

[0102] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A continuous integration method for vehicle electronic control software, characterized in that: The continuous integration method of the vehicle electronic control software is applied to an integration server, and the method comprises: Respond to the integration task request and read the version number information in the collaborative management platform according to the current input parameters; The file version of the local warehouse is updated according to the version number information to obtain an updated file version, and the updated file version is sent to the source code management platform, so that the source code management platform feeds back a model code file according to the updated file version, wherein the model code file is generated by the generation server when the source code management platform sends the updated file version to the generation server; Integration is performed according to the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

2. The method according to claim 1, characterized in that The step of integrating the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file comprises: Updating the integrated code version according to the model code file to obtain a version update status; When the version update status is an update completion status, obtaining a basic service file in a source code management platform; Integration is performed according to the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

3. The method according to claim 1, characterized in that The step of responding to the integration task request and reading the version number information in the collaborative management platform according to the current input parameters includes: Respond to integration task requests and determine parameter update types based on current incoming parameters; The version number information in the collaborative management platform is read according to the parameter update type.

4. The method according to claim 1, characterized in that After integrating the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file, the method further includes: Sending the integrated intermediate file to a source code management platform so that the source code management platform stores the integrated intermediate file; The integration target file is sent to a continuous integration platform, so that the continuous integration platform stores the integration target file.

5. A continuous integration method for vehicle electronic control software, characterized in that: The continuous integration method of the vehicle electronic control software is applied to a generation server, and the method comprises: Get updated file versions sent by the source code management platform; The generated code version is updated according to the update file version to obtain the current update status; When the current update state is an update completion state, a model code file is generated according to the initial model file, and the model code file is sent to a source code management platform for integration according to the model code file.

6. The method according to claim 5, characterized in that The step of generating a model code file according to the initial model file when the current update state is an update completion state comprises: When the current update state is an update completion state, identifying the initial model file and determining a model identification result; Determine the corresponding target application layer model according to the model recognition result; A model code file is generated according to the target application layer model.

7. A continuous integration method for vehicle electronic control software, characterized in that: The continuous integration method of the vehicle electronic control software is applied to a continuous integration platform, and the method comprises: Obtain user login information, verify the user login information, and determine the user verification status; When the user verification status is a verification passed status, an integration task request is initiated to an integration server based on a parameterized interface to perform continuous integration.

8. The method according to claim 7, characterized in that After the step of initiating an integration task request based on a parameterized interface when the user verification status is a verification passed status so that the integration server responds to the integration task request, the method further includes: Get the target integration results and integration log files; A target mail file is generated according to a preset mail template, the target integration result and the integration log file, and the target mail file is sent to the user.

9. A continuous integration device for vehicle electronic control software, characterized in that: The device comprises: The response module is used to respond to the integration task request and read the version number information in the collaborative management platform according to the current input parameters; An update module, used to update the file version of the local warehouse according to the version number information to obtain an updated file version, and send the updated file version to the source code management platform, so that the generation server generates a model code file according to the updated file version in the source code management platform; The integration module is used to integrate the model code file and the basic service file to obtain an integrated intermediate file and an integrated target file.

10. A continuous integration system for vehicle electronic control software, characterized in that: The continuous integration system of vehicle electronic control software comprises an integration server as described in any one of claims 1 to 4, a generation server as described in any one of claims 5 to 6, and a continuous integration platform as described in any one of claims 7 to 8.

Images