Software integration method, apparatus, storage medium, and electronic device

Abstract

The present disclosure relates to a software integration method, device, storage medium and electronic equipment. The method comprises: determining whether all target resource files required for software integration exist according to a plurality of source files and a software integration form, wherein the software integration form indicates the target resource files required for software integration; in the case where it is determined that all the target resource files exist, integrating and compiling the target resource files to obtain a compiled file; performing software testing on the compiled file, and in the case where the software testing is passed, determining the compiled file as an executable file corresponding to target software obtained by software integration. Thus, the target resource files for software integration can be automatically checked based on a software development form, the manual workload is reduced, accurate data support is provided for subsequent software integration, and invalid compilation processes can be avoided to ensure the reliability of the obtained compiled file.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of computer, in particular, to a software integration method and device, a storage medium and an electronic device. BACKGROUND

[0002] With the development of computer technology, the software development process is also gradually complicated. The existing software development can be realized by software integration of the code files developed by multiple developers through cooperation.

[0003] Therefore, the reliability and efficiency of software integration seriously affect the progress of software development project. In the prior art, the staff who need to perform software integration obtain the corresponding source files to perform software integration and obtain the corresponding software product. However, in the above process, a large amount of manual work is required, and errors in the process of manually checking the source files will directly affect the process of software integration and the availability and stability of the software product obtained after integration. SUMMARY

[0004] The purpose of the present disclosure is to provide a stable and efficient software integration method, device, storage medium and electronic device.

[0005] In order to achieve the above purpose, according to a first aspect of the present disclosure, a software integration method is provided, the method comprising:

[0006] According to the obtained multiple source files and software integration forms, it is determined whether the target resource files required for software integration are all present, wherein the software integration forms indicate the target resource files required for software integration;

[0007] In the case where it is determined that the target resource files are all present, the target resource files are integrated and compiled to obtain a compiled file;

[0008] The compiled file is software tested, and in the case where the software test is passed, the compiled file is determined as an executable file corresponding to the target software obtained by software integration.

[0009] Optionally, the step of determining whether the target resource files required for software integration are all present according to the obtained multiple source files and software integration forms comprises:

[0010] Iterating the software integration forms to obtain the identification of the target resource files;

[0011] According to the identification of the target resource files, the multiple source files are queried;

[0012] If the target resource file corresponding to the identifier is not found in the plurality of source files, it is determined that the target resource files required for software integration are not all present.

[0013] Optionally, the method further comprises:

[0014] In the case that the target resource file corresponding to the identifier is not found in the plurality of source files, outputting prompt information, wherein the prompt information contains the target identifier corresponding to the target resource file;

[0015] In response to receiving the source file uploaded by the user for the prompt information, if the identifier of the source file is the target identifier, storing the uploaded source file.

[0016] Optionally, the method of determining whether the target resource files required for software integration are all present according to the plurality of source files and the software integration form further comprises:

[0017] If the target resource file corresponding to each identifier is found in the plurality of source files, it is determined whether the version of the target resource file is the target version corresponding to the target resource file;

[0018] In the case that the version of each target resource file is determined to be the target version corresponding to the target resource file, it is determined that the target resource files required for software integration are all present.

[0019] Optionally, the method of integrating and compiling the target resource file to obtain a compiled file comprises:

[0020] Compiling the target resource file based on a compiling module;

[0021] In the case of compilation failure, obtaining a log file;

[0022] Performing a correction operation according to the log file;

[0023] After performing the correction operation, returning to the step of compiling the target resource file based on the compiling module until the compiled file is obtained.

[0024] Optionally, the method of performing a correction operation according to the log file comprises:

[0025] According to the identifier in the log file, querying a corresponding correction strategy from a correction strategy library;

[0026] When the correction strategy corresponding to the identifier is queried, performing a correction operation according to the correction strategy.

[0027] Optionally, the method further comprises:

[0028] publishing an executable file corresponding to the target software;

[0029] storing the target file according to a preset storage path of the target file, wherein the target file includes the executable file and one or more of the target resource files.

[0030] According to a second aspect of the present disclosure, a software integration device is provided, and the device includes:

[0031] a first determining module configured to determine whether all target resource files required for software integration are present according to the obtained plurality of source files and a software integration form, wherein the software integration form indicates the target resource files required for software integration;

[0032] a compiling module configured to integrate and compile the target resource files to obtain a compiled file when it is determined that all the target resource files are present;

[0033] a second determining module configured to perform software testing on the compiled file, and determine the compiled file as an executable file corresponding to the target software obtained by software integration when the software testing is passed.

[0034] According to a third aspect of the present disclosure, a non-transitory computer readable storage medium is provided, and the medium stores a computer program which, when executed by a processor, implements the steps of any of the methods of the first aspect.

[0035] According to a fourth aspect of the present disclosure, an electronic device is provided, and the device includes:

[0036] a memory storing a computer program;

[0037] a processor configured to execute the computer program in the memory to implement the steps of any of the methods of the first aspect.

[0038] In the technical solution, whether all the target resource files required for software integration exist is determined according to the obtained multiple source files and software integration forms; and in the case that it is determined that all the target resource files exist, the target resource files are integrated and compiled to obtain a compiled file; then the compiled file is tested, and in the case that the software test is passed, the compiled file is determined as an executable file corresponding to the target software obtained by software integration. Thus, by the technical solution, the target resource files for software integration can be automatically checked based on the software development forms, which can effectively reduce the workload of the staff and effectively ensure the accuracy of file checking, and provide accurate data support for subsequent software integration. In the case that it is determined that all the target resource files exist, integration and compilation are performed, which can avoid invalid compilation process and ensure the reliability of the obtained compiled file. In addition, by testing the compiled file, the reliability and safety of the obtained compiled file can be further improved, which can ensure the stability of the target software corresponding to the compiled file to a certain extent.

[0039] Other features and advantages of the present disclosure will be described in detail in the following detailed description section. BRIEF DESCRIPTION OF DRAWINGS

[0040] The accompanying drawings are included to provide a further understanding of the present disclosure and constitute a part of the specification, which together with the following detailed description, serve to explain the present disclosure. In the drawings:

[0041] Figure 1 is a flowchart of a software integration method according to an embodiment of the present disclosure;

[0042] Figure 2 is a block diagram of a software integration apparatus according to an embodiment of the present disclosure;

[0043] Figure 3 is a block diagram of an electronic device according to an exemplary embodiment;

[0044] Figure 4 is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0045] The detailed description of the present disclosure will be described below in conjunction with the accompanying drawings. It should be understood that the detailed description described herein is only used to explain and describe the present disclosure, and is not used to limit the present disclosure.

[0046] Figure 1 is a flowchart of a software integration method according to an embodiment of the present disclosure. As shown in the figure, Figure 1As shown, the method can include:

[0047] In step 11, it is determined whether all target resource files required for software integration are present according to the obtained multiple source files and software integration form, wherein the software integration form indicates the target resource files required for software integration.

[0048] In software project development, multiple developers can develop codes for their own tasks to obtain multiple source files. Then the developers can upload the developed code source files through a version control system to provide resource files for software integration.

[0049] As an example, when performing software integration, the resource files required for integration can be determined in advance according to the current development task, that is, each target resource file can be determined in advance to form the software integration form. Then when the source code files uploaded by the developers are obtained, it is determined whether all target resource files are present to determine whether software integration can be performed, thereby ensuring the file security of software integration.

[0050] In step 12, when it is determined that all target resource files are present, the target resource files are integrated and compiled to obtain a compiled file.

[0051] When it is determined that all target resource files are present, it can be considered that all files for software integration have been prepared, and in this case, the target resource files can be automatically integrated and compiled without manual operation by the user. The existing compilation tools can be used to compile the multiple target resource files to obtain a compiled file.

[0052] In step 13, the compiled file is subjected to software testing, and when the software testing is passed, the compiled file is determined as an executable file corresponding to the target software obtained by software integration.

[0053] After obtaining the compiled file, in order to ensure the usability of the compiled file, the compiled file can be subjected to software testing to determine whether the compiled file can realize the function of the target software corresponding to software integration. As an example, the preset test cases and test tools can be used for automatic testing, which will not be described here. After the software testing is passed, the compiled file can be determined as an executable file corresponding to the target software obtained by software integration, so as to deploy and release the compiled file.

[0054] In the technical solution, whether all target resource files required for software integration are present is determined according to the obtained multiple source files and the software integration form; and in the case that all target resource files are present, the target resource files are integrated and compiled to obtain a compiled file; then the compiled file is tested, and in the case that the software test is passed, the compiled file is determined as an executable file corresponding to target software obtained by software integration. Thus, the target resource files for software integration can be automatically checked based on the software development form according to the technical solution, which can effectively reduce the workload of staff and effectively ensure the accuracy of file checking, and provide accurate data support for subsequent software integration. In the case that all target resource files are present, integration and compilation are performed, which can avoid invalid compilation process and ensure the reliability of the obtained compiled file. In addition, the software test on the compiled file can further improve the reliability and security of the obtained compiled file, and to some extent, can ensure the stability of the target software corresponding to the compiled file.

[0055] In a possible embodiment, in step 11, an example implementation of determining whether all target resource files required for software integration are present according to the obtained multiple source files is as follows, which can include:

[0056] Iterating the software integration form to obtain the identification of the target resource file;

[0057] According to the identification of the target resource file, the multiple source files are queried.

[0058] In the software integration form, the identification of each target resource file can be recorded, for example, the identification can be the name of the target resource file, or the ID of the target resource file, which is not limited in the present disclosure. For example, the software integration form can be iterated to obtain the identification of the target resource file from the software integration form, and the identification is queried from the obtained multiple source files. For each identification, if the file corresponding to the identification is queried from the source file, it is determined that the target resource file corresponding to the identification exists; if the file corresponding to the identification is not queried from the source file, it is determined that the target resource file corresponding to the identification does not exist.

[0059] If the target resource file corresponding to the identification is not queried from the multiple source files, it is determined that all target resource files required for software integration are not present.

[0060] As described above, the identifier indicates the target resource file required for software integration, therefore, if the file corresponding to the identifier is not queried from the plurality of source files, that is, the target resource file corresponding to the identifier has not been uploaded by the corresponding developer, it can be determined that the target resource does not exist in its entirety.

[0061] In a possible embodiment, if the target resource file corresponding to each identifier is queried from the plurality of source files, it can be determined that the target resource file required for software integration exists in its entirety.

[0062] Therefore, by the technical solution described above, the identifier of the target resource file can be acquired from the software integration form, so as to automatically determine whether each target resource file for software integration is ready, thereby avoiding the missing of the resource file due to the insufficient uploading of the source file by the developer, and avoiding the missing of the resource file due to the manual collection error, ensuring the integrity of the resource file for software integration, and providing accurate data support for subsequent software integration.

[0063] In another possible embodiment, the method can further include:

[0064] In the case that the target resource file corresponding to the identifier is not queried from the plurality of source files, outputting prompt information, wherein the prompt information contains the target identifier corresponding to the target resource file.

[0065] As described above, in the case that the target resource file corresponding to the identifier is not queried from the acquired source file, it indicates that the target resource file has not been uploaded, at this time, the prompt information can be outputted to prompt the user to upload the source file in time for software integration.

[0066] In response to receiving the source file uploaded by the user for the prompt information, if the identifier of the source file is the target identifier, storing the uploaded source file.

[0067] After displaying the prompt information, the user can upload the corresponding file for the target identifier in the prompt information, when receiving the source file uploaded by the user, it can be determined whether the identifier of the source file and the target identifier are the same, if they are the same, it indicates that the source file uploaded by the user is the target resource file required for software integration, at this time, the source file can be stored to ensure the subsequent software integration process.

[0068] If the unqueried target resource file is a plurality of target resource files, the target identifiers of the plurality of target resource files can be prompted in the prompt information, so as to facilitate the user to upload in batches and improve the efficiency of resource file collection.

[0069] Therefore, by the technical solution, when it is determined that the target resource file required for software integration is missing, the user can be prompted by a prompt message, so that the user can upload the missing source file in time, and the integrity of the file for software integration is ensured.

[0070] In another possible embodiment, the code file is usually updated during the software development process, so that different versions of source files appear, and the contents in different versions of source files are not completely same. Based on this, the present disclosure further provides the following embodiments.

[0071] For example, the step of determining whether the target resource files required for software integration are all present according to the obtained plurality of source files and the software integration form can further include:

[0072] If the target resource file corresponding to each identifier is queried from the plurality of source files, it is determined whether the version of the target resource file is the target version corresponding to the target resource file.

[0073] In a case where it is determined that the version of each target resource file is the target version corresponding to the target resource file, it is determined that the target resource files required for software integration are all present.

[0074] The target version of each target resource file required for software integration can be determined in advance when the software integration is performed, so as to ensure the accuracy of the content of the file for software integration. In the embodiment of the present disclosure, when it is determined that each target resource file is present based on the identifier of the target resource file, it is further determined whether the version of the obtained target resource file is the target version required by the target resource file, so as to further determine the accuracy of the content of the obtained target resource file.

[0075] In a possible embodiment, the developer can add the corresponding version when naming the file when developing the code, so as to facilitate the differentiation of each file. In this embodiment, the target version corresponding to the target resource file can be obtained through the name of the target resource file. In another possible embodiment, the content in the source file can contain version information, so that the target version corresponding to the target resource file can be obtained by reading the file content in the queried target resource file.

[0076] In this embodiment, the target version corresponding to the target resource file can be stored and set in the software integration form in the form of a version identifier, or can be stored and set by using other description identifier files, which are not limited in the present disclosure.

[0077] Therefore, by the technical solution, whether the target resource files required for software integration are all present is determined, the integrity of each target resource file is ensured, the accuracy of the content of each target resource file is ensured, the accuracy and availability of the compiled file obtained by software integration are further improved, and user experience is improved.

[0078] In an actual application scenario, a user usually needs to trigger a file for compilation, and if the compilation fails, a staff needs to participate in the compilation, which occupies too much time of the staff. Based on this, the present disclosure further provides the following embodiments.

[0079] In a possible embodiment, an exemplary implementation manner of integrating and compiling the target resource files to obtain a compiled file is as follows, and the step can include:

[0080] Compiling the target resource files based on a compiling module.

[0081] The compiling module can be implemented by using an existing compiling tool, and details are not described herein.

[0082] In the case of compilation failure, a log file is obtained.

[0083] A correction operation is performed according to the log file.

[0084] The storage location of the log file can be set in advance, so that the log file can be directly obtained based on the storage location in the case of compilation failure, and the log file is analyzed.

[0085] As an example, an implementation manner of performing the correction operation according to the log file is as follows, and the step can include:

[0086] An identifier in the log file is used to query a corresponding correction strategy from a correction strategy library.

[0087] In this embodiment, a corresponding correction strategy can be set in advance for an error log that can occur in the compilation process, the correction strategy indicates a correction operation that needs to be performed, and the correction strategy is used to automatically correct a loophole in the compilation process. The identifier of the error log and the correction strategy are stored in the correction strategy library in association.

[0088] When the correction strategy corresponding to the identifier is queried, a correction operation is performed according to the correction strategy.

[0089] The identifier corresponding to the vulnerability information of the compilation failure can be obtained from the log file by reading the content of the log file. The solution corresponding to the vulnerability can be determined based on the identifier. The correction strategy for solving the vulnerability can be obtained from the correction strategy library based on the identifier, and the corresponding correction operation is performed.

[0090] Thus, by the above technical solution, the corresponding correction strategy can be determined based on the error identification of the compilation process, and the correction operation is performed based on the correction strategy, realizing automatic vulnerability repair in the compilation process without manual intervention of the staff, reducing the manual workload of the staff, and ensuring the stable execution of the compilation process to a certain extent, further improving the efficiency of the software integration method.

[0091] After the correction operation is performed, the compilation process can continue, and the step of compiling the target resource file based on the compilation module can be returned until the compiled file is obtained.

[0092] In this step, the compilation can continue based on the resource file obtained after the correction operation is performed after the correction operation is performed, ensuring the sequential execution of the compilation process and avoiding repeated compilation of the files that have been compiled successfully, improving the efficiency of the compilation process. If the compilation fails in the subsequent compilation process, the automatic correction of the compilation vulnerability can be realized based on the above process. In this compilation process, the staff does not need to manually intervene to realize integrated compilation, which can ensure the sequential execution of the compilation process and the accuracy of the obtained compiled file, improve the compilation efficiency and security, thereby improving the efficiency and stability of software integration, and further improving the user experience.

[0093] In one possible embodiment, the method can further include:

[0094] The executable file corresponding to the target software is published.

[0095] In this embodiment, after obtaining the executable file corresponding to the target software, the executable file can be published for users to download and use, realizing version update and iteration of the target software. The publication of the target software can be published in a common way in the art, such as uploading the software product to a remote server for user installation and deployment, which is not limited in the present disclosure.

[0096] Then, the target file can be stored according to a preset storage path of the target file, wherein the target file includes one or more of the executable file and the target resource file.

[0097] In the software updating process, in order to ensure the safety and traceability of software updating, the corresponding files in the current updating process are usually stored for monitoring the current updating files. Accordingly, in this embodiment, the corresponding storage path can be set in advance for the target files that need to be stored in the current software integration process, and then the target files can be safely stored after the target software integration is released, so as to clearly indicate the content of the current update in the subsequent updating process.

[0098] For example, the target file can include the executable file to store the software released this time. As another example, the target file can include the resource file updated in the current software integration process, so as to store the content of the current update.

[0099] Therefore, by the above technical solution, the new version of the target software can be released, and the corresponding related files in the target software integration process can be stored according to the preset storage path. On the one hand, the related data in the current integration process can be safely stored to ensure the safety and traceability of software updating. On the other hand, the manual workload can be saved, and the standardization and accuracy of the storage path can be ensured to improve the efficiency of subsequent file searching and further improve the user experience.

[0100] The present disclosure also provides a software integration device, such as Figure 2 As shown in the figure, the device 10 includes:

[0101] A first determination module 100 is configured to determine whether all target resource files required for software integration exist according to the obtained plurality of source files and a software integration form, wherein the software integration form indicates the target resource files required for software integration.

[0102] A compiling module 200 is configured to integrate and compile the target resource files to obtain a compiled file when it is determined that all target resource files exist.

[0103] A second determination module 300 is configured to perform software testing on the compiled file, and determine the compiled file as an executable file corresponding to the target software obtained by software integration when the software testing is passed.

[0104] Optionally, the first determination module includes:

[0105] A first acquisition sub-module is configured to traverse the software integration form to obtain the identification of the target resource file.

[0106] A first query sub-module is configured to query from the plurality of source files according to the identification of the target resource file.

[0107] The first determining sub-module is configured to determine that all target resource files required for software integration are not present in the case that the target resource file corresponding to the identifier is not found in the plurality of source files.

[0108] Optionally, the apparatus further comprises:

[0109] The output module is configured to output prompt information in the case that the target resource file corresponding to the identifier is not found in the plurality of source files, wherein the prompt information comprises a target identifier corresponding to the target resource file.

[0110] The first storage module is configured to store the uploaded source file in the case that the identifier of the uploaded source file is the target identifier in response to receiving the uploaded source file of the user for the prompt information.

[0111] Optionally, the first determining module further comprises:

[0112] The second determining sub-module is configured to determine whether the version of the target resource file is a target version corresponding to the target resource file in the case that the target resource file corresponding to each identifier is found in the plurality of source files.

[0113] The third determining sub-module is configured to determine that all target resource files required for software integration are present in the case that the version of each target resource file is the target version corresponding to the target resource file.

[0114] Optionally, the compiling module comprises:

[0115] The compiling sub-module is configured to compile the target resource file based on the compiling module.

[0116] The second obtaining sub-module is configured to obtain a log file in the case of compiling failure.

[0117] The first executing sub-module is configured to perform a correction operation according to the log file, and trigger the compiling sub-module to compile the target resource file based on the compiling module after performing the correction operation, until the compiling file is obtained.

[0118] Optionally, the first executing sub-module comprises:

[0119] The second querying sub-module is configured to query a corresponding correction strategy from a correction strategy library according to an identifier in the log file.

[0120] The second executing sub-module is configured to perform a correction operation according to the correction strategy in the case that the correction strategy corresponding to the identifier is queried.

[0121] Optionally, the apparatus further includes:

[0122] a publishing module, configured to publish the executable file corresponding to the target software;

[0123] a second storage module, configured to store the target file according to a preset storage path of the target file, wherein the target file includes one or more of the executable file and the target resource file.

[0124] As to the apparatus in the above-mentioned embodiments, the specific manners in which various modules perform operations have been described in details in the embodiments of the method, and thus will not be described in details here.

[0125] Figure 3 is a block diagram of an electronic device 700 according to an exemplary embodiment. As shown in Figure 3 the electronic device 700 can include a processor 701, a memory 702. The electronic device 700 can also include one or more of a multimedia component 703, an input / output (I / O) interface 704, and a communication component 705.

[0126] The processor 701 is configured to control overall operations of the electronic device 700 to complete all or part of the steps of the software integration method described above. The memory 702 is configured to store various types of data to support operations of the electronic device 700, which can include, for example, instructions of any application or method operating on the electronic device 700, and application-related data such as contact data, transmitted and received messages, pictures, audio, video, and the like. The memory 702 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as a static random access memory (SRAM), an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a programmable read-only memory (PROM), a read-only memory (ROM), a magnetic storage, a flash memory, a magnetic disk, or an optical disk. The multimedia component 703 can include a screen and an audio component. The screen can be, for example, a touch screen, and the audio component is configured to output and / or input audio signals. For example, the audio component can include a microphone configured to receive external audio signals. The received audio signals can be further stored in the memory 702 or transmitted through the communication component 705. The audio component further includes at least one speaker configured to output audio signals. The I / O interface 704 provides an interface between the processor 701 and other interface modules, which can be a keyboard, a mouse, a button, and the like. The buttons can be virtual buttons or physical buttons. The communication component 705 is configured to perform wired or wireless communication between the electronic device 700 and other devices. The wireless communication, such as Wi-Fi, Bluetooth, near field communication (NFC), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, and the like, or a combination of one or more of them, is not limited herein. Therefore, the communication component 705 can include, for example, a Wi-Fi module, a Bluetooth module, an NFC module, and the like.

[0127] In an example embodiment, the electronic device 700 can be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors, or other electronic elements for executing the software integration method described above.

[0128] In another example embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the software integration method described above. For example, the computer-readable storage medium can be the memory 702 described above including program instructions executable by the processor 701 of the electronic device 700 to complete the software integration method described above.

[0129] Figure 4 is a block diagram of an electronic device 1900 according to an example embodiment. For example, the electronic device 1900 can be provided as a server. Referring to Figure 4 , the electronic device 1900 includes a processor 1922, the number of which can be one or more, and a memory 1932 for storing computer programs executable by the processor 1922. The computer programs stored in the memory 1932 can include one or more than one module each corresponding to a set of instructions. In addition, the processor 1922 can be configured to execute the computer programs to perform the software integration method described above.

[0130] In addition, the electronic device 1900 can also include a power supply component 1926, which can be configured to perform power management of the electronic device 1900, and a communication component 1950, which can be configured to implement communication of the electronic device 1900, such as wired or wireless communication. In addition, the electronic device 1900 can also include an input / output (I / O) interface 1958. The electronic device 1900 can operate based on an operating system stored in the memory 1932, such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , etc.

[0131] In another exemplary embodiment, a computer readable storage medium including program instructions is also provided, which when executed by a processor implement the steps of the software integration method described above. For example, the non-transitory computer readable storage medium can be the memory 1932 described above including program instructions executable by the processor 1922 of the electronic device 1900 to complete the software integration method described above.

[0132] In another exemplary embodiment, a computer program product is also provided, which contains a computer program executable by a programmable apparatus, the computer program having code portions for performing the software integration method described above when executed by the programmable apparatus.

[0133] The preferred embodiments of the present disclosure are described in detail above with reference to the accompanying drawings, but the present disclosure is not limited to the specific details in the above-described embodiments. Various simple modifications can be made to the technical solutions of the present disclosure within the scope of the technical concepts of the present disclosure, and all these simple modifications shall fall within the protection scope of the present disclosure.

[0134] In addition, it should be noted that each of the specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction. In order to avoid unnecessary repetition, various possible combinations are not described again in the present disclosure.

[0135] Furthermore, any combination of the various different embodiments of the present disclosure can also be made, as long as it does not deviate from the idea of the present disclosure, it should also be considered as disclosed by the present disclosure.

Claims

1. A software integration method, characterized in that, The method includes: Traverse the software integration form to obtain the identifier of the target resource file and the identifier of the target version, wherein the software integration form indicates the target resource file required for software integration; Based on the identifier of the target resource file, a query is performed from multiple source files, and the file name of each source file includes a version identifier; If a target resource file corresponding to each of the identifiers is found from the multiple source files, determine whether the version identifier of the target resource file is the target version identifier corresponding to the target resource file; If it is determined that the version identifier of each target resource file is the target version identifier corresponding to that target resource file, it is determined that all target resource files required for software integration exist; If all target resource files are confirmed to exist, the target resource files are compiled using the compilation module. If compilation fails, a log file is obtained. Based on the identifier in the log file, the corresponding correction strategy is queried from the correction strategy library. When a correction strategy corresponding to the identifier is found, the correction operation is performed according to the correction strategy. After the correction operation is performed, the process returns to the step of compiling the target resource files based on the compilation module until a compiled file is obtained. The compiled file is subjected to software testing, and if the software testing passes, the compiled file is identified as the executable file corresponding to the target software obtained through software integration. If the target resource file corresponding to the identifier is not found in the multiple source files, it is determined that not all the target resource files required for software integration exist. If the target resource file corresponding to the identifier is not found in the multiple source files, a prompt message is output, wherein the prompt message contains the target identifier corresponding to the target resource file; In response to receiving a source file uploaded by the user in response to the prompt information, if the identifier of the source file is the target identifier, the uploaded source file is stored.

2. The method according to claim 1, characterized in that, The method further includes: The executable file corresponding to the target software is released; The target file is stored according to a preset storage path, wherein the target file includes the executable file and one or more of the target resource files.

3. A software integration device, characterized in that, The device includes: The first determining module is used to traverse the software integration form to obtain the identifiers of target resource files and target version identifiers, wherein the software integration form indicates the target resource files required for software integration; based on the identifiers of the target resource files, it queries from multiple source files, each source file's filename including a version identifier; if a target resource file corresponding to each identifier is found from the multiple source files, it determines whether the version identifier of the target resource file is the target version identifier corresponding to that target resource file; if it is determined that the version identifiers of the target resource files are the target version identifier corresponding to that target resource file, it is determined that all target resource files required for software integration exist; if no target resource file corresponding to the identifier is found from the multiple source files, it is determined that not all target resource files required for software integration exist. The compilation module is used to compile the target resource files based on the compilation module when it is determined that all the target resource files exist; if the compilation fails, it obtains a log file; queries the corresponding correction policy from the correction policy library according to the identifier in the log file; when a correction policy corresponding to the identifier is found, it performs a correction operation according to the correction policy; after performing the correction operation, it returns to the step of compiling the target resource files based on the compilation module until a compiled file is obtained. The second determining module is used to perform software testing on the compiled file, and if the software test passes, determine the compiled file as the executable file corresponding to the target software obtained by software integration; The output module is used to output a prompt message when the target resource file corresponding to the identifier is not found in the multiple source files, wherein the prompt message contains the target identifier corresponding to the target resource file; The first storage module is configured to, in response to receiving a source file uploaded by a user in response to the prompt information, store the uploaded source file if the identifier of the source file is the target identifier.

4. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method described in any one of claims 1-2.

5. An electronic device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program in the memory to implement the steps of the method according to any one of claims 1-2.

Images