CN114780097A - Software integration method and device, storage medium and electronic equipment - Google Patents

Software integration method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN114780097A
CN114780097A CN202110687831.0A CN202110687831A CN114780097A CN 114780097 A CN114780097 A CN 114780097A CN 202110687831 A CN202110687831 A CN 202110687831A CN 114780097 A CN114780097 A CN 114780097A
Authority
CN
China
Prior art keywords
file
target resource
software
target
software integration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110687831.0A
Other languages
Chinese (zh)
Inventor
柳东昕
高鹏飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Great Wall Motor Co Ltd
Original Assignee
Great Wall Motor Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Great Wall Motor Co Ltd filed Critical Great Wall Motor Co Ltd
Priority to CN202110687831.0A priority Critical patent/CN114780097A/en
Publication of CN114780097A publication Critical patent/CN114780097A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing

Abstract

The present disclosure relates to a software integration method, apparatus, storage medium, and electronic device, the method comprising: determining whether all target resource files required for software integration exist according to the acquired multiple source files and the acquired software integration form, wherein the target resource files required for software integration are indicated in the software integration form; under the condition that all the target resource files are determined to exist, performing integrated compiling on the target resource files to obtain compiled files; and performing software test on the compiled file, and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software test is passed. Therefore, the target resource file for software integration can be automatically checked based on the software publishing list, the manual workload is reduced, accurate data support is provided for subsequent software integration, and invalid compiling processes can be avoided to ensure the reliability of the obtained compiled file.

Description

Software integration method and device, storage medium and electronic equipment
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a software integration method and apparatus, a storage medium, and an electronic device.
Background
With the solution of computer technology, the development process of software projects is gradually complicated. The existing software development can be realized by the software integration of the developed code files through the cooperation of multiple developers.
Therefore, the reliability and efficiency of software integration also severely impact the progress of a software development project. In the prior art, a worker who needs to perform software integration generally obtains a corresponding source file, so as to perform software integration and obtain a corresponding software product. However, not only a great deal of manual work is required in the above process, but also the process of software integration and the usability and stability of the software product obtained after integration are directly affected when an error occurs in the process of manually checking the source file.
Disclosure of Invention
The purpose of the present disclosure is to provide a stable and efficient software integration method, device, storage medium and electronic device.
In order to achieve the above object, according to a first aspect of the present disclosure, there is provided a software integration method, the method including:
determining whether all target resource files required for software integration exist according to the acquired multiple source files and the acquired software integration form, wherein the target resource files required for software integration are indicated in the software integration form;
under the condition that all the target resource files are determined to exist, performing integrated compiling on the target resource files to obtain compiled files;
and performing software testing on the compiled file, and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software testing is passed.
Optionally, the determining, according to the obtained multiple source files and the obtained software integration form, whether all target resource files required for software integration exist includes:
traversing the software integrated form to acquire the identifier of the target resource file;
querying from the plurality of source files according to the identification of the target resource file;
and if the target resource file corresponding to the identifier is not inquired from the source files, determining that all the target resource files required for software integration do not exist.
Optionally, the method further comprises:
under the condition that a target resource file corresponding to the identifier is not inquired in the source files, outputting prompt information, wherein the prompt information comprises a target identifier corresponding to the target resource file;
and responding to a received source file uploaded by a user aiming at the prompt message, and if the identifier of the source file is the target identifier, storing the uploaded source file.
Optionally, the determining, according to the obtained multiple source files and the obtained software integration form, whether all target resource files required for software integration exist further includes:
if a target resource file corresponding to each identifier is inquired from the source files, determining whether the version of the target resource file is a target version corresponding to the target resource file;
and under the condition that the version of each target resource file is determined to be the target version corresponding to the target resource file, determining that all target resource files required for software integration exist.
Optionally, the performing integrated compilation on the target resource file to obtain a compiled file includes:
compiling the target resource file based on a compiling module;
under the condition of compiling failure, acquiring a log file;
executing correction operation according to the log file;
and after the correction operation is executed, returning to the step of compiling the target resource file based on the compiling module until the compiled file is obtained.
Optionally, the performing a correction operation according to the log file includes:
inquiring a corresponding correction strategy from a correction strategy library according to the identifier in the log file;
and when a correction strategy corresponding to the identifier is inquired, performing correction operation according to the correction strategy.
Optionally, the method further comprises:
issuing an executable file corresponding to the target software;
and storing the target file according to a preset storage path of the target file, wherein the target file comprises one or more of the executable file and the target resource file.
According to a second aspect of the present disclosure, there is provided a software integration apparatus, the apparatus comprising:
the software integration system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining whether all target resource files required for software integration exist according to a plurality of acquired source files and a software integration form, and the target resource files required for software integration are indicated in the software integration form;
the compiling module is used for carrying out integrated compiling on the target resource file under the condition that all the target resource files are determined to exist so as to obtain a compiled file;
and the second determining module is used for performing software test on the compiled file and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software test is passed.
According to a third aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of any of the methods of the first aspect.
According to a fourth aspect of the present disclosure, there is provided an electronic apparatus comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to implement the steps of the method of any of the first aspects.
In the technical scheme, whether all target resource files required for software integration exist is determined according to a plurality of acquired source files and software integration forms; under the condition that all the target resource files are determined to exist, the target resource files are integrated and compiled to obtain compiled files; and then, carrying out software test on the compiled file, and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software test is passed. Therefore, by the technical scheme, the target resource file for software integration can be automatically checked based on the software development list, so that the manual workload of workers can be effectively reduced, the accuracy of file checking can be effectively guaranteed, and accurate data support is provided for subsequent software integration. And the integrated compilation can be carried out under the condition that all the target resource files exist, so that an invalid compilation process can be avoided, and the reliability of the obtained compiled files can be ensured. In addition, by performing software testing on the compiled file, the reliability and the safety of the obtained compiled file can be further improved, and the running stability of target software corresponding to the compiled file can be ensured to a certain extent.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure, but do not constitute a limitation of the disclosure. In the drawings:
FIG. 1 is a flow chart of a method of software integration provided according to one embodiment of the present disclosure;
FIG. 2 is a block diagram of a software integration apparatus provided in accordance with one embodiment of the present disclosure;
FIG. 3 is a block diagram illustrating an electronic device in accordance with an exemplary embodiment;
FIG. 4 is a block diagram of an electronic device shown in accordance with an example embodiment.
Detailed Description
The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.
Fig. 1 is a flowchart illustrating a software integration method according to an embodiment of the present disclosure. As shown in fig. 1, the method may include:
in step 11, determining whether all target resource files required for software integration exist according to the acquired multiple source files and the acquired software integration form, where the target resource files required for software integration are indicated in the software integration form.
In the development of the software project, a plurality of developers can develop codes according to own tasks to obtain a plurality of source files. And then, a developer can upload the developed code source file through the version control system, so that a resource file is provided for software integration.
As an example, when software integration is performed, resource files that need to be integrated may be predetermined according to the current development task, that is, each target resource file may be predetermined, so that the software integration form may be formed. And then, when the source code file uploaded by the developer is obtained, whether all the target resource files exist is determined so as to determine whether software integration can be performed, and the file security of the software integration is ensured.
In step 12, in the case that it is determined that all the target resource files exist, the target resource files are subjected to integrated compilation to obtain compiled files.
Under the condition that the target resource files are all determined to exist, all files for software integration can be considered to be ready, and under the condition, the target resource files can be automatically integrated and compiled without manual operation of a user. The target resource files can be compiled by adopting the existing compiling tool, so that the compiled files are obtained.
In step 13, a software test is performed on the compiled file, and if the software test is passed, the compiled file is determined as an executable file corresponding to the target software obtained by performing software integration.
After the compiled file is obtained, in order to ensure the usability of the compiled file, a software test may be performed on the compiled file to determine whether the compiled file can implement a function of the target software corresponding to the software integration. For example, the automated test may be performed by using a preset test case and a test tool, which are not described herein again. After the software test is passed, the compiled file may be determined as an executable file corresponding to the target software obtained by performing software integration, so as to deploy and release the compiled file.
In the technical scheme, whether all target resource files required for software integration exist is determined according to a plurality of acquired source files and software integration forms; under the condition that all the target resource files are determined to exist, performing integrated compiling on the target resource files to obtain compiled files; and then, carrying out software test on the compiled file, and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software test is passed. Therefore, by the technical scheme, the target resource file for software integration can be automatically checked based on the software development list, so that the manual workload of workers can be effectively reduced, the accuracy of file checking can be effectively guaranteed, and accurate data support is provided for subsequent software integration. And the integrated compilation can be carried out under the condition that all the target resource files exist, so that an invalid compilation process can be avoided, and the reliability of the obtained compiled files can be ensured. In addition, by performing software testing on the compiled file, the reliability and the safety of the obtained compiled file can be further improved, and the running stability of the target software corresponding to the subsequent compiled file can be ensured to a certain extent.
In a possible embodiment, in step 11, according to the obtained multiple source files, an exemplary implementation manner of determining whether all target resource files required for software integration exist is as follows, and this step may include:
traversing the software integrated form to acquire the identifier of the target resource file;
and inquiring from the source files according to the identification of the target resource file.
The software integration form may record an identifier of each target resource file, for example, the identifier may be a name of the target resource file, or may also be an ID of the target resource file, which is not limited in this disclosure. As an example, a software integration form may be traversed to obtain an identification of a target resource file from the software integration form, and a query may be performed from the obtained plurality of source files according to the identification. For each identifier, if a file corresponding to the identifier is inquired from the source file, determining that a target resource file corresponding to the identifier exists; and if the file corresponding to the identifier is not inquired from the source file, determining that the target resource file corresponding to the identifier does not exist.
And if the target resource file corresponding to the identifier is not inquired from the source files, determining that all the target resource files required for software integration do not exist.
As can be seen from the foregoing, the identifier indicates a target resource file required for software integration, and therefore, if a file corresponding to the identifier is not queried from the plurality of source files, that is, the target resource file corresponding to the identifier is not currently uploaded by a corresponding developer, it may be determined that all target resources do not exist at this time.
In a possible embodiment, if target resource files corresponding to respective identifiers are queried from a plurality of source files, it may be determined that all target resource files required for software integration exist.
Therefore, according to the technical scheme, the identification of the target resource file can be acquired from the software integration form, so that whether the preparation of each target resource file for software integration is completed or not is automatically determined, the resource file loss caused by insufficient uploading of the source file by developers can be avoided, the resource file loss caused by manual collection errors can be avoided, the integrity of the resource file for software integration is ensured, and accurate data support is provided for subsequent software integration.
In another possible embodiment, the method may further include:
and outputting prompt information under the condition that the target resource file corresponding to the identifier is not inquired in the source files, wherein the prompt information comprises the target identifier corresponding to the target resource file.
As described above, the target resource file corresponding to the identifier is not queried in the obtained source file, which indicates that the target resource file is not uploaded, and at this time, prompt information may be output to prompt a user to upload the source file in time, so as to perform software integration.
And responding to a received source file uploaded by a user aiming at the prompt message, and if the identifier of the source file is the target identifier, storing the uploaded source file.
After the prompt information is displayed, a user can upload a corresponding file according to the target identifier in the prompt information, and when a source file uploaded by the user is received, whether the identifier of the source file is the same as the target identifier can be determined, if the identifier of the source file is the same as the target identifier, the source file uploaded by the user is a target resource file required by software integration, and at the moment, the source file can be stored so as to ensure a subsequent software integration process.
If the number of the target resource files which are not inquired is multiple, the target identifiers of the multiple target resource files can be prompted in the prompt message, so that the user can conveniently upload the target identifiers in batches, and the resource file collection efficiency is improved.
Therefore, according to the technical scheme, when the situation that the target resource file for software integration of the user is lost is determined, the user can be prompted through the prompt message, so that the user can conveniently upload the lost source file in time, and the integrity of the file for software integration is ensured.
In another possible embodiment, the code file is updated during the software development process, so that different versions of the source file can appear, and the content of the source file in different versions is not identical. Based on this, the present disclosure also provides the following embodiments.
For example, according to the obtained multiple source files and software integration forms, determining whether all target resource files required for software integration exist in another embodiment may further include:
if a target resource file corresponding to each identifier is inquired from the source files, determining whether the version of the target resource file is a target version corresponding to the target resource file;
and under the condition that the version of each target resource file is determined to be the target version corresponding to the target resource file, determining that all target resource files required for software integration exist.
When software integration is carried out, the target version of each target resource file needing software integration can be predetermined so as to ensure the accuracy of the file content for software integration. In this embodiment of the present disclosure, when it is determined that each target resource file exists based on the identifier of the target resource file, it needs to be further determined whether the version of the obtained target resource file is the required target version, so as to further determine the accuracy of the content of the obtained target resource file.
In a possible embodiment, when a developer performs code development, the developer may add its corresponding version to the file name, so that the developer can distinguish files conveniently. In this embodiment, the version corresponding to the target resource file may be obtained by the name of the target resource file. In another possible embodiment, the content in the source file may include version information, and the version corresponding to the target resource file may be obtained by reading the file content in the queried target resource file.
In this embodiment, the target version corresponding to the target resource file may be stored and set in the software integration form in advance in a version identification manner, or may be stored and set in another description identification file, which is not limited in this disclosure.
Therefore, according to the technical scheme, whether all the target resource files required for software integration exist is determined, the integrity of each target resource file is guaranteed, the accuracy of the content of each target resource file can be guaranteed, the accuracy and the usability of the compiled file obtained by software integration are further improved, and the user experience is improved.
In an actual application scenario, a user is usually required to trigger a file to be compiled, and in the compiling process, if the compiling fails, a worker is required to participate, so that too much time is occupied for the worker. Based on this, the present disclosure also provides the following embodiments.
In a possible embodiment, the exemplary implementation manner of performing integrated compilation on the target resource file to obtain a compiled file is as follows, and the step may include:
and compiling the target resource file based on a compiling module.
The compiling module can be implemented by using an existing compiling tool, and is not described herein again.
Under the condition of compiling failure, acquiring a log file;
and executing correction operation according to the log file.
The storage location of the log file can be preset, so that the log file can be directly acquired based on the storage location to analyze the log file under the condition of failed compilation.
As an example, the implementation manner of performing the correction operation according to the log file is as follows, and this step may include:
and inquiring a corresponding correction strategy from a correction strategy library according to the identifier in the log file.
In this embodiment, a corresponding correction policy may be set in advance for an error log that may occur in the compiling process, where the correction policy indicates a correction operation that needs to be performed, so as to automatically correct a vulnerability in the compiling process based on the correction policy. Wherein the identifier of the error log may be stored in association with the rework policy in the rework policy repository.
And when a correction strategy corresponding to the identifier is inquired, performing correction operation according to the correction strategy.
The content of the log file can be read, so that a corresponding identifier can be obtained from the log file, and the identifier can be used for representing vulnerability information of compiling failure. Then, a solution corresponding to the vulnerability can be determined based on the identifier, a query can be performed from a correction policy library based on the identifier to obtain a correction policy for solving the vulnerability, and a corresponding correction operation is executed.
Therefore, according to the technical scheme, the corresponding correction strategy can be determined based on the error identification of the compiling process, so that correction operation is carried out based on the correction strategy, automatic bug repair in the compiling process is realized, manual intervention of workers is not needed, the manual workload of the workers is reduced, stable execution of the compiling process can be guaranteed to a certain extent, and the efficiency of the software integration method is further improved.
Then, after the modification operation is performed, the compiling process may be continued, and the step of compiling the target resource file based on the compiling module may be returned again until the compiled file is obtained.
In this step, after the revision operation is performed, compilation may be continued based on the resource file obtained after the revision operation is performed, so as to ensure sequential execution of the compilation process, avoid a repeated compilation process on a file that has already been compiled, and improve efficiency of the compilation process. If the compiling fails in the subsequent compiling process, the compiling loophole can be automatically corrected based on the process, the integrated compiling can be realized without manual intervention of workers in the compiling process, the sequential execution of the compiling process can be guaranteed, the accuracy of the obtained compiled files can be guaranteed, the compiling efficiency and the safety are improved, the software integration efficiency and the software integration stability are improved, and the user experience is further improved.
In one possible embodiment, the method may further comprise:
and issuing the executable file corresponding to the target software.
In this embodiment, after the executable file corresponding to the target software is obtained, the executable file may be published for downloading and use by a user, so as to implement version update and iteration of the target software. The target software may be released in a common manner in the art, for example, the software product may be uploaded to a remote server for installation and deployment by a user, which is not limited in the present disclosure.
And then, storing the target file according to a preset storage path of the target file, wherein the target file comprises the executable file and one or more of the target resource files.
In the software updating process, in order to ensure the security and traceability of the software updating, the corresponding file in the current updating process is usually required to be stored, so as to monitor the current updating file. Correspondingly, in this embodiment, a corresponding storage path may be preset for a target file that needs to be stored in the current software integration process, so that the target file may be safely stored after the target software is integrated and released, so that the content of the current update is determined in the subsequent update process.
Illustratively, the object file may include the executable file to store the software released this time. As another example, the target file may include a resource file updated in the software integration process, so as to store the content of the update.
From this, through above-mentioned technical scheme, can carry out the release of new edition to target software, can save the relevant file that corresponds according to predetermineeing the storage route in this target software integration process simultaneously, can carry out safe storage to the relevant data in this integration process on the one hand, guarantee software update's security and traceability, on the other hand also can save manual work volume, and can guarantee the standardization and the accuracy of storage route, in order to improve the efficiency that follow-up file was looked for, further promote user's use and experience.
The present disclosure also provides a software integration apparatus, as shown in fig. 2, the apparatus 10 includes:
a first determining module 100, configured to determine whether all target resource files required for software integration exist according to the obtained multiple source files and a software integration form, where the target resource files required for software integration are indicated in the software integration form;
the compiling module 200 is configured to perform integrated compiling on the target resource file to obtain a compiled file under the condition that all the target resource files are determined to exist;
a second determining module 300, configured to perform a software test on the compiled file, and determine the compiled file as an executable file corresponding to the target software obtained by performing software integration when the software test is passed.
Optionally, the first determining module includes:
the first acquisition submodule is used for traversing the software integrated form to acquire the identifier of the target resource file;
the first query submodule is used for querying from the source files according to the identification of the target resource file;
and the first determining sub-module is used for determining that all target resource files required for software integration do not exist under the condition that the target resource files corresponding to the identifiers are not inquired from the source files.
Optionally, the apparatus further comprises:
an output module, configured to output a prompt message when a target resource file corresponding to the identifier is not queried in the multiple source files, where the prompt message includes a target identifier corresponding to the target resource file;
and the first storage module is used for responding to the received source file uploaded by the user aiming at the prompt message, and storing the uploaded source file if the identifier of the source file is the target identifier.
Optionally, the first determining module further includes:
a second determining sub-module, configured to determine, when a target resource file corresponding to each identifier is queried from the multiple source files, whether a version of the target resource file is a target version corresponding to the target resource file;
and the third determining submodule is used for determining that all the target resource files required for software integration exist under the condition that the version of each target resource file is determined to be the target version corresponding to the target resource file.
Optionally, the compiling module includes:
the compiling submodule is used for compiling the target resource file based on the compiling module;
the second obtaining submodule is used for obtaining the log file under the condition that the compiling fails;
and the first execution submodule is used for executing a correction operation according to the log file and triggering the compiling submodule to compile the target resource file based on the compiling module after the correction operation is executed until the compiled file is obtained.
Optionally, the first execution sub-module includes:
the second query submodule is used for querying a corresponding correction strategy from a correction strategy library according to the identifier in the log file;
and the second execution sub-module is used for executing correction operation according to the correction strategy when the correction strategy corresponding to the identifier is inquired.
Optionally, the apparatus further comprises:
the release module is used for releasing the executable file corresponding to the target software;
and the second storage module is used for storing the target file according to a preset storage path of the target file, wherein the target file comprises one or more of the executable file and the target resource file.
With regard to the apparatus in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be described in detail here.
Fig. 3 is a block diagram illustrating an electronic device 700 according to an example embodiment. As shown in fig. 3, the electronic device 700 may include: a processor 701 and a memory 702. The electronic device 700 may also include one or more of a multimedia component 703, an input/output (I/O) interface 704, and a communication component 705.
The processor 701 is configured to control the overall operation of the electronic device 700, so as to complete all or part of the steps in the software integration method. The memory 702 is used to store various types of data to support operation at the electronic device 700, such as instructions for 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 so forth. The Memory 702 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk. The multimedia components 703 may include screen and audio components. Wherein the screen may be, for example, a touch screen and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may further be stored in the memory 702 or transmitted through the communication component 705. The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 704 provides an interface between the processor 701 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 705 is used for wired or wireless communication between the electronic device 700 and other devices. Wireless Communication, such as Wi-Fi, bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or a combination of one or more of them, which is not limited herein. The corresponding communication component 705 may thus comprise: Wi-Fi modules, Bluetooth modules, NFC modules, and the like.
In an exemplary embodiment, the electronic Device 700 may 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, microcontrollers, microprocessors, or other electronic components for performing the software integration method described above.
In another exemplary embodiment, there is also provided a computer readable storage medium including program instructions which, when executed by a processor, implement the steps of the software integration method described above. For example, the computer readable storage medium may be the memory 702 described above including program instructions that are executable by the processor 701 of the electronic device 700 to perform the software integration method described above.
Fig. 4 is a block diagram illustrating an electronic device 1900 according to an example embodiment. For example, electronic device 1900 may be provided as a server. Referring to fig. 4, an electronic device 1900 includes a processor 1922, which may be one or more in number, and a memory 1932 for storing computer programs executable by the processor 1922. The computer program stored in memory 1932 may include one or more modules that each correspond to a set of instructions. Further, the processor 1922 may be configured to execute the computer program to perform the software integration method described above.
Additionally, the electronic device 1900 may also include a power component 1926 and a communication component 1950, the power component 1926 may be configured toPerforming power management of the electronic device 1900, the communication component 1950 may be configured to enable communication of the electronic device 1900, e.g., wired or wireless communication. In addition, the electronic device 1900 may also include input/output (I/O) interfaces 1958. The electronic device 1900 may operate based on an operating system, such as Windows Server, stored in memory 1932TM，Mac OS XTM，UnixTM，LinuxTMAnd so on.
In another exemplary embodiment, there is also provided a computer readable storage medium including program instructions 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 may be the memory 1932 described above that includes program instructions executable by the processor 1922 of the electronic device 1900 to perform the software integration method described above.
In another exemplary embodiment, a computer program product is also provided, which comprises 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.
The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.
It should be noted that the various features described in the foregoing embodiments may be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, various possible combinations will not be separately described in this disclosure.
In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.

Claims (10)

1. A method of software integration, the method comprising:
determining whether all target resource files required for software integration exist according to the acquired multiple source files and the acquired software integration form, wherein the target resource files required for software integration are indicated in the software integration form;
under the condition that all the target resource files are determined to exist, performing integrated compilation on the target resource files to obtain compiled files;
and performing software testing on the compiled file, and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software testing is passed.
2. The method according to claim 1, wherein the determining whether all target resource files required for software integration exist according to the obtained multiple source files and software integration forms comprises:
traversing the software integrated form to acquire the identifier of the target resource file;
querying from the plurality of source files according to the identification of the target resource file;
and if the target resource file corresponding to the identifier is not inquired from the source files, determining that all the target resource files required for software integration do not exist.
3. The method of claim 2, further comprising:
outputting prompt information under the condition that a target resource file corresponding to the identifier is not inquired in the source files, wherein the prompt information comprises a target identifier corresponding to the target resource file;
and responding to a received source file uploaded by a user aiming at the prompt message, and if the identifier of the source file is the target identifier, storing the uploaded source file.
4. The method according to claim 2, wherein determining whether all target resource files required for software integration exist according to the obtained plurality of source files and software integration forms further comprises:
if a target resource file corresponding to each identifier is inquired from the source files, determining whether the version of the target resource file is a target version corresponding to the target resource file;
and under the condition that the version of each target resource file is determined to be the target version corresponding to the target resource file, determining that all target resource files required for software integration exist.
5. The method of claim 1, wherein the performing the integrated compilation on the target resource file to obtain a compiled file comprises:
compiling the target resource file based on a compiling module;
under the condition of compiling failure, acquiring a log file;
executing correction operation according to the log file;
and after the correction operation is executed, returning to the step of compiling the target resource file based on the compiling module until the compiled file is obtained.
6. The method of claim 5, wherein performing a fix-up operation from the log file comprises:
inquiring a corresponding correction strategy from a correction strategy library according to the identifier in the log file;
and when a correction strategy corresponding to the identifier is inquired, performing correction operation according to the correction strategy.
7. The method of claim 1, further comprising:
issuing an executable file corresponding to the target software;
and storing the target file according to a preset storage path of the target file, wherein the target file comprises one or more of the executable file and the target resource file.
8. A software integration apparatus, the apparatus comprising:
the software integration system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining whether all target resource files required for software integration exist according to a plurality of acquired source files and a software integration form, and the target resource files required for software integration are indicated in the software integration form;
the compiling module is used for carrying out integrated compiling on the target resource file under the condition that all the target resource files are determined to exist so as to obtain a compiled file;
and the second determining module is used for performing software test on the compiled file and determining the compiled file as an executable file corresponding to target software obtained by software integration under the condition that the software test is passed.
9. A non-transitory computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
10. An electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to carry out the steps of the method of any one of claims 1 to 7.
CN202110687831.0A 2021-06-21 2021-06-21 Software integration method and device, storage medium and electronic equipment Pending CN114780097A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110687831.0A CN114780097A (en) 2021-06-21 2021-06-21 Software integration method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110687831.0A CN114780097A (en) 2021-06-21 2021-06-21 Software integration method and device, storage medium and electronic equipment

Publications (1)

Publication Number Publication Date
CN114780097A true CN114780097A (en) 2022-07-22

Family

ID=82423351

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110687831.0A Pending CN114780097A (en) 2021-06-21 2021-06-21 Software integration method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN114780097A (en)

Similar Documents

Publication Publication Date Title
US9940225B2 (en) Automated error checking system for a software application and method therefor
CN108196878B (en) Method and device for generating application program installation package, electronic equipment and storage medium
US9027014B2 (en) Updating firmware compatibility data
US10579966B1 (en) Adapting a shared project build platform to a developer plugin
CN111144839B (en) Project construction method, continuous integration system and terminal equipment
CN109902005B (en) Automatic testing method and system
US11113050B2 (en) Application architecture generation
US20190087310A1 (en) Mobile application program testing method, server, terminal, and storage medium
CN111382048B (en) Management method and device for mobile equipment on true machine test platform
US10579513B2 (en) Test run control method and apparatus
CN110851539A (en) Metadata verification method and device, readable storage medium and electronic equipment
CN111142899A (en) Database script execution method and device, storage medium and electronic equipment
EP3447635A1 (en) Application architecture generation
CN111966390A (en) Project construction method, system, terminal device and storage medium
CN111459509A (en) Container mirror image construction method and device and server
CN110908670A (en) Method and device for automatically publishing service
CN111078265B (en) Web project update patch generation method based on jenkins
CN106909434B (en) Method and device for detecting undefined function in executable program
CN110990833B (en) SDK safety detection method and related equipment
CN115454575B (en) jar packet conversion and automatic loading method, device, equipment and storage medium
CN109684205B (en) System testing method, device, electronic equipment and storage medium
CN114780097A (en) Software integration method and device, storage medium and electronic equipment
CN107220174B (en) Automatic testing method and device
CN113126998A (en) Incremental source code acquisition method and device, electronic equipment and storage medium
CN115168175A (en) Program error solving method, device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination