CN113535558A - Software version transmission method and device - Google Patents

Software version transmission method and device Download PDF

Info

Publication number
CN113535558A
CN113535558A CN202110793900.6A CN202110793900A CN113535558A CN 113535558 A CN113535558 A CN 113535558A CN 202110793900 A CN202110793900 A CN 202110793900A CN 113535558 A CN113535558 A CN 113535558A
Authority
CN
China
Prior art keywords
target
package
installation
software version
test environment
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
CN202110793900.6A
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.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
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 Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202110793900.6A priority Critical patent/CN113535558A/en
Publication of CN113535558A publication Critical patent/CN113535558A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/368Test management for test version control, e.g. updating test cases to a new software version
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/40Transformation of program code
    • G06F8/41Compilation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

The embodiment of the application provides a software version transmission method and a device, which can be used in the technical field of finance, and the method comprises the following steps: generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information; and packaging the target installation template, generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version, and transmitting the target software version to a target test environment to construct a corresponding target software version in the target test environment. The method and the device can meet the requirement of creating different software versions for multiple times in one test environment, and can also correctly install the new software versions even if each software version created in the test environment is not created according to the original installation sequence, and can not cause the files of the original versions to be wrongly covered, so that the application effectiveness and reliability of the test environment can be effectively improved.

Description

Software version transmission method and device
Technical Field
The application relates to the technical field of data processing, in particular to the technical field of finance, and specifically relates to a software version transmission method and device.
Background
With the rapid development of the fields such as the financial science and technology industry and the like, the business requirements are increasingly updated, the multi-branch needs to be operated in parallel for a long period due to the research and development rhythm problem, and the magnitude of the software version is continuously increased. In order to ensure that the software operates correctly in the production environment, each software version needs to be tested in a test environment.
At present, the existing software version transmission mode only supports the situation that software version files in a test environment are all covered, the requirement that different software versions are created in one test environment for many times cannot be met, once each software version created in the test environment is not created according to the original installation sequence, the situation that the original version files are covered by errors can be caused, the test environment is further unavailable, service testing cannot be carried out smoothly, and the problems that the service requirements are normally put into a production environment and the like are influenced are solved.
Disclosure of Invention
Aiming at the problems in the prior art, the application provides a software version transmission method and a software version transmission device, which can meet the requirement of creating different software versions for multiple times in a test environment, can correctly install new target software versions even if each software version created in the test environment is not created according to the original installation sequence, and can not cause the files of the original versions to be covered by errors, thereby effectively improving the application effectiveness and reliability of the test environment, leading the service test to be carried out smoothly and ensuring that the service requirement is normally put into the production environment.
In order to solve the technical problem, the application provides the following technical scheme:
in a first aspect, the present application provides a software version transmission method, including:
generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information;
packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version;
and transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
Further, the generating a target installation template including a target software version according to at least one policy item corresponding to the target policy package information includes:
receiving target strategy package information, wherein the target strategy package information comprises a strategy package name, a strategy package identification and informing information for indicating whether the target strategy package is an intelligent package;
if the notification information corresponding to the target policy package information indicates that the installation policy package corresponding to the target policy package information is an intelligent package, acquiring at least one policy item corresponding to the target policy package information from the corresponding relationship between each pre-stored policy package identifier and each policy item;
and generating a target installation template corresponding to the target strategy package information according to at least one strategy item, the strategy package name and the strategy package identification corresponding to the target strategy package information.
Further, the target policy package information further includes an initial version number of the target policy package;
correspondingly, before the packaging processing of the target installation template, the method further includes:
and storing the initial version number of the target strategy package corresponding to the target installation template.
Further, the packaging the target installation template and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation policy package corresponding to the target software version includes:
packaging the target installation template to generate a compiling version number corresponding to the initial version number of the target strategy package, and generating a corresponding label, compiling time and a hash code to obtain a target intelligent installation strategy package of the target software version corresponding to the target strategy package information;
the target intelligent installation strategy package is further provided with an intelligent file list, and the intelligent file list is used for storing all file information and relative paths corresponding to the initial version number, the compiling time, the label, the compiling version number, the hash code and the target software version.
Further, before the transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number, and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment, the method further includes:
acquiring a current environment list of a target test environment;
and judging whether the environment list contains an intelligent installation strategy package with the same strategy package name and/or strategy package identification as the target intelligent installation strategy package, if not, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
Further, the transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number, and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment includes:
if the environment list is judged to contain the intelligent installation strategy package which is the same as the target intelligent installation strategy package, judging whether the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment;
if the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment, and if the hash code corresponding to the target intelligent installation strategy package already covers the hash code of the intelligent installation strategy package in the target test environment, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating an environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
Further, the transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number, and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment further includes:
if the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment, the hash code corresponding to the target intelligent installation strategy package does not cover the hash code of the intelligent installation strategy package in the target test environment, and the target intelligent installation strategy package is a configuration file, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating an environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
Further, the transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number, and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment further includes:
if the hash code corresponding to the target intelligent installation strategy package is different from the hash code of the intelligent installation strategy package in the target test environment, judging whether the compilation version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compilation version number of the target intelligent installation strategy package;
if the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compiling version number of the target intelligent installation strategy package, and the compiling time of the target intelligent installation strategy package is longer than the compiling time of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
Further, the transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number, and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment further includes:
if the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is different from the compiling version number of the target intelligent installation strategy package, and the compiling version number of the target intelligent installation strategy package is larger than the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
In a second aspect, the present application provides a software version transmission apparatus, including:
the template generating module is used for generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information;
the strategy package creating module is used for packaging the target installation template and generating corresponding compiling time, compiling version number and hash code so as to obtain a target intelligent installation strategy package corresponding to the target software version;
and the version transmission module is used for transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
In a third aspect, the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the software version transmission method when executing the program.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the software version transmission method described.
According to the technical scheme, the method and the device for transmitting the software version provided by the application comprise the following steps: generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information; packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version; according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package, the target intelligent installation strategy package is transmitted to a target test environment to construct a corresponding target software version in the target test environment, and a corresponding target installation template is generated according to at least one strategy item corresponding to target strategy package information, so that different creating strategy configuration requirements of each software version file can be met, and the application universality and the comprehensiveness of software version transmission can be effectively improved; the target installation template is packaged, and corresponding compiling time, compiling version number and hash code are generated to obtain a target intelligent installation strategy package corresponding to the target software version, so that the effectiveness of generating the intelligent installation strategy package can be effectively improved, and a reliable and effective data base is provided for subsequent software version transmission; the target intelligent installation strategy package is transmitted to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, so that the problem of automatic installation of a server environment under parallel incremental version distribution of a plurality of software versions can be solved, differential incremental coverage of the software versions can be realized, and correct files can still be installed in the target environment under the condition that the version installation sequence is adjusted; that is to say, the method and the device can create the target software version which is not created according to the original installation sequence in the test environment with at least one software version installed, and further can meet the requirement of creating different software versions in one test environment for many times.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a connection relationship between a software version transmission apparatus and a client device in an embodiment of the present application.
Fig. 2 is a first flowchart of a software version transmission method in the embodiment of the present application.
Fig. 3 is a second flowchart of a software version transmission method in the embodiment of the present application.
Fig. 4 is a third flowchart illustrating a software version transmission method in an embodiment of the present application.
Fig. 5 is a fourth flowchart illustrating a software version transmission method in the embodiment of the present application.
Fig. 6 is a fifth flowchart illustrating a software version transmission method in an embodiment of the present application.
Fig. 7 is a sixth flowchart illustrating a software version transmission method in an embodiment of the present application.
Fig. 8 is a seventh flowchart illustrating a software version transmission method in an embodiment of the present application.
Fig. 9 is an eighth flowchart illustrating a software version transmission method in an embodiment of the present application.
Fig. 10 is a ninth flowchart illustrating a software version transmission method in an embodiment of the present application.
Fig. 11 is a schematic structural diagram of a software version transmission apparatus in an embodiment of the present application.
Fig. 12 is a functional diagram of a software version transmission method provided in an application example of the present application.
Fig. 13 is a schematic diagram of a correspondence relationship between a policy package table and a compilation policy table provided in an application example of the present application.
FIG. 14 is a logic diagram of an implementation of intelligent file transfer provided by an application example of the present application.
Fig. 15 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the software version transmission method and apparatus disclosed in the present application can be used in the field of financial technology, and can also be used in any field other than the field of financial technology.
Aiming at the problems that the existing software version transmission mode only supports the complete coverage of files, so that the situation that an original edition file is easily covered by errors occurs, a test environment is further unavailable, a new software version cannot be correctly created on a test switch, a service test cannot be smoothly carried out, the normal production environment of service requirements is influenced and the like, the embodiment of the application provides a software version transmission method, a corresponding target installation template is generated according to at least one strategy item corresponding to target strategy package information, the different creation strategy configuration requirements of each software version file can be met, and the application universality and the comprehensiveness of software version transmission can be effectively improved; the target installation template is packaged, and corresponding compiling time, compiling version number and hash code are generated to obtain a target intelligent installation strategy package corresponding to the target software version, so that the effectiveness of generating the intelligent installation strategy package can be effectively improved, and a reliable and effective data base is provided for subsequent software version transmission; the target intelligent installation strategy package is transmitted to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, so that the problem of automatic installation of a server environment under parallel incremental version distribution of a plurality of software versions can be solved, differential incremental coverage of the software versions can be realized, and correct files can still be installed in the target environment under the condition that the version installation sequence is adjusted; that is to say, the method and the device can create the target software version which is not created according to the original installation sequence in the test environment with at least one software version installed, and further can meet the requirement of creating different software versions in one test environment for many times.
Based on the above, the present application further provides a software version transmission apparatus for implementing the software version transmission method provided in one or more embodiments of the present application, where the software version transmission apparatus may be a server, see fig. 1, the software version transmission apparatus may be in communication connection with each client device by itself or through a third-party server, and the software version transmission apparatus may also be in communication connection with a target system in which a target test environment is disposed; the target system can be a production system, the software version transmission device can receive target strategy package information sent by the client equipment by itself or through a third-party server, and a corresponding target installation template is generated according to at least one strategy item corresponding to the target strategy package information; packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version; and transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, and then transmitting a software version transmission result to client equipment by a software version transmission device for displaying and the like.
In another practical application scenario, the aforementioned software version transmission apparatus may perform part of the software version transmission in the server as described above, or all operations may be performed in the user end device. Specifically, the selection may be performed according to the processing capability of the user end device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. If all the operations are completed in the customer premise equipment, the customer premise equipment may further include a processor for performing specific processing of the software version transmission.
It is understood that the mobile terminal may include any mobile device capable of loading an application, such as a smart phone, a tablet electronic device, a network set-top box, a portable computer, a Personal Digital Assistant (PDA), a vehicle-mounted device, a smart wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch, intelligent bracelet etc..
The mobile terminal may have a communication module (i.e., a communication unit), and may be communicatively connected to a remote server to implement data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.
The server and the mobile terminal may communicate using any suitable network protocol, including network protocols not yet developed at the filing date of this application. The network protocol may include, for example, a TCP/IP protocol, a UDP/IP protocol, an HTTP protocol, an HTTPS protocol, or the like. Of course, the network Protocol may also include, for example, an RPC Protocol (Remote Procedure Call Protocol), a REST Protocol (Representational State Transfer Protocol), and the like used above the above Protocol.
The following embodiments and application examples are specifically and individually described in detail.
In order to solve the problems that the existing software version transmission mode only supports the complete coverage of files, so that the original edition files are easily covered by errors, the test environment is further unavailable, a new software version cannot be correctly created in a test switch, the service test cannot be smoothly performed, the normal production environment of service requirements is influenced, and the like, the application provides an embodiment of a software version transmission method, and referring to fig. 2, the software version transmission method executed based on a software version transmission device specifically comprises the following contents:
step 100: and generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information.
In step 100, a policy item is created by a user in advance and stored in the software version transmission device or a database accessible by the software version transmission device, and the policy item refers to unit policy data required for installing the software version into the test environment, and is used for forming a complete intelligent installation policy package.
Step 200: and packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version.
In step 200, when the target installation template is packaged, corresponding contents such as compilation time, compilation version number, hash code and the like are generated at the same time, and the packaged target intelligent installation policy package includes all files corresponding to the contents generated during packaging and the target software version.
It is to be understood that the hash code may be the SHA1 code or the like.
Step 300: and transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
Specifically, before the target software version is manufactured, an installation strategy needs to be added to the intelligent file transmission, the purpose is to support the intelligent file transmission, and the purpose is to support the automatic installation of the version. For the source FILE of intelligent transmission, the source FILE is fixedly stored in a FILE directory such as 'version program/ATOMIC _ FILE' in the version. The strategy package is newly added in the step to be an intelligent strategy package, and the transmission of the intelligent file is realized.
As can be seen from the above description, in the software version transmission method provided in the embodiment of the present application, the corresponding target installation template is generated according to the at least one policy item corresponding to the target policy package information, so that different requirements for creating policy configuration of each software version file can be met, and the application universality and comprehensiveness of software version transmission can be effectively improved; the target installation template is packaged, and corresponding compiling time, compiling version number and hash code are generated to obtain a target intelligent installation strategy package corresponding to the target software version, so that the effectiveness of generating the intelligent installation strategy package can be effectively improved, and a reliable and effective data base is provided for subsequent software version transmission; the target intelligent installation strategy package is transmitted to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, so that the problem of automatic installation of a server environment under parallel incremental version distribution of a plurality of software versions can be solved, differential incremental coverage of the software versions can be realized, and correct files can still be installed in the target environment under the condition that the version installation sequence is adjusted; that is to say, the method and the device can create the target software version which is not created according to the original installation sequence in the test environment with at least one software version installed, and further can meet the requirement of creating different software versions in one test environment for many times.
In order to meet the requirement of different creation policy configuration for each software version file, in an embodiment of the software version transmission method provided in the present application, referring to fig. 3, step 100 of the software version transmission method specifically includes the following steps:
step 110: and receiving target strategy package information, wherein the target strategy package information comprises a strategy package name, a strategy package identification and informing information for indicating whether the target strategy package is an intelligent package.
Step 120: and if the notification information corresponding to the target policy package information indicates that the installation policy package corresponding to the target policy package information is an intelligent package, acquiring at least one policy item corresponding to the target policy package information from the corresponding relationship between each prestored policy package identifier and each policy item.
Step 130: and generating a target installation template corresponding to the target strategy package information according to at least one strategy item, the strategy package name and the strategy package identification corresponding to the target strategy package information.
Specifically, the system acquires newly added POLICY package information entered on a page, records the POLICY package information into a database POLICY package table (VACP _ insert _ POLICY _ PKG), which contains information such as "POLICY package ID", "POLICY package name", "intelligent package not" and the like, enters the newly added POLICY package information through the front end of the system, and can associate a compilation POLICY table (BUILD _ POLICY) with the "POLICY package ID", store the newly added POLICY package information as a template function, and quickly store the POLICY package as an installation template for compilation.
As can be seen from the above description, in the software version transmission method provided in this embodiment of the present application, if the notification information corresponding to the target policy package information indicates that the installation policy package corresponding to the target policy package information is an intelligent package, at least one policy item corresponding to the target policy package information is obtained from the correspondence between each pre-stored policy package identifier and each policy item, so that different requirements for creating policy configuration of each software version file can be met, individualized requirements for testing can be met, and the applicability and the comprehensiveness of software version transmission can be further improved.
In order to improve reliability and effectiveness of a target software version constructed in a test environment subsequently, in one embodiment of the software version transmission method provided by the application, the target policy package information further includes an initial version number of the target policy package; referring to fig. 4, before steps 100 and 200 of the software version transmission method, the following contents are specifically included:
step 140: and storing the initial version number of the target strategy package corresponding to the target installation template.
Specifically, the version number is an important judgment basis for intelligent file transmission, and the version number contains the version of the intelligent policy package, and the version is checked in the version construction process, and the version without the version number is failed to be constructed. The system writes the information into the VERSION information table (VACP _ BUILD _ VERSION _ INFO) through the application environment maintenance interface.
As can be seen from the above description, in the software version transmission method provided in the embodiment of the present application, the version number is an important judgment basis for intelligent file transmission, and contains the version of the intelligent policy package, and the version is to be verified in the version construction process, and the version without the version number is failed to be constructed; the system writes the information into the version information table through the application environment maintenance interface, and therefore reliability and effectiveness of the target software version constructed in the test environment are effectively improved.
In order to improve the effectiveness of generating the intelligent installation policy package, in an embodiment of the software version transmission method provided in the present application, referring to fig. 5, a step 200 of the software version transmission method specifically includes the following contents:
step 210: packaging the target installation template to generate a compiling version number corresponding to the initial version number of the target strategy package, and generating a corresponding label, compiling time and a hash code to obtain a target intelligent installation strategy package of the target software version corresponding to the target strategy package information; the target intelligent installation strategy package is further provided with an intelligent file list, and the intelligent file list is used for storing all file information and relative paths corresponding to the initial version number, the compiling time, the label, the compiling version number, the hash code and the target software version.
Specifically, the intelligent version building will generate an "ATOMIC _ file.zip" FILE under the "version program" path, open "ATOMIC _ file.zip", and "ATOMIC _ FILE _ list.txt" to automatically generate contents for writing to the first line: a version number; writing in the second row: compiling time; writing in the third row: base line/label, base line label information of all tasks corresponding to the task; fourth row write: compiling a version number; fifth row write: information of all files (not including directories) under the intelligent folder (including sub-directories), SHA1 code of relative path | file of file, one line per file. Zip is generated with added checking information, and the correctness of the zip package is checked when the version is imported, so that the content of the zip file cannot be manually modified.
As can be seen from the above description, in the software version transmission method provided in the embodiment of the present application, by setting the target intelligent installation policy package and the intelligent file list of the target software version corresponding to the target policy package information, the effectiveness of generating the intelligent installation policy package can be effectively improved, and a reliable and effective data basis is provided for subsequent software version transmission, so that the reliability and effectiveness of the software version transmission process can be further improved.
In order to improve the efficiency and convenience of software version transmission, in an embodiment of the software version transmission method provided in the present application, referring to fig. 6, before steps 200 and 300, the following contents are further included:
step 220: acquiring a current environment list of a target test environment;
step 230: and judging whether the environment list contains an intelligent installation strategy package with the same strategy package name and/or strategy package identification as the target intelligent installation strategy package, if not, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
As can be seen from the above description, the software version transmission method provided in the embodiment of the present application can effectively improve the efficiency and convenience of software version transmission by determining whether the target software version exists in the environment, and if not, directly performing the file overlay processing.
In order to overcome the problem of automatic installation of a server environment under parallel incremental version of multiple software versions, in an embodiment of the software version transmission method provided by the present application, referring to fig. 7, step 300 in the software version transmission method specifically includes the following contents:
step 310: and if the environment list is judged to contain the intelligent installation strategy package which is the same as the target intelligent installation strategy package, judging whether the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment.
Step 320: if the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment, and if the hash code corresponding to the target intelligent installation strategy package already covers the hash code of the intelligent installation strategy package in the target test environment, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating an environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
As can be seen from the above description, in the software version transmission method provided in this embodiment of the present application, by determining whether the hash code corresponding to the target intelligent installation policy package is the same as the hash code of the intelligent installation policy package in the target test environment, the problem of automatic installation of a server environment under parallel incremental version distribution of multiple software versions can be solved, differential incremental coverage of software versions can be implemented, and it is ensured that a correct file can still be installed in the target environment under the condition that the version installation order is adjusted.
In order to further overcome the problem of automatic installation of a server environment under parallel incremental version of multiple software versions, in an embodiment of the software version transmission method provided by the present application, referring to fig. 8, step 300 in the software version transmission method further includes the following steps:
step 330: if the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment, the hash code corresponding to the target intelligent installation strategy package does not cover the hash code of the intelligent installation strategy package in the target test environment, and the target intelligent installation strategy package is a configuration file, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating an environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
As can be seen from the above description, the software version transmission method provided in the embodiment of the present application can further solve the problem of automatic installation of a server environment under parallel incremental version distribution of multiple software versions by determining whether the target intelligent installation policy package is a configuration file, can implement differentiated incremental coverage of software versions, and ensures that a correct file can still be installed in a target environment under the condition that the version installation order is adjusted.
In order to further overcome the problem of automatic installation of a server environment under parallel incremental version of multiple software versions, in an embodiment of the software version transmission method provided by the present application, referring to fig. 9, step 300 in the software version transmission method further includes the following steps:
step 340: and if the hash code corresponding to the target intelligent installation strategy package is different from the hash code of the intelligent installation strategy package in the target test environment, judging whether the compilation version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compilation version number of the target intelligent installation strategy package.
Step 350: if the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compiling version number of the target intelligent installation strategy package, and the compiling time of the target intelligent installation strategy package is longer than the compiling time of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
As can be seen from the above description, in the software version transmission method provided in this embodiment of the present application, by determining whether the compiling version number of the intelligent installation policy package that is the same as the target intelligent installation policy package in the environment list is the same as the compiling version number of the target intelligent installation policy package, and determining whether the compiling time of the target intelligent installation policy package is greater than the compiling time of the intelligent installation policy package that is the same as the target intelligent installation policy package in the environment list, the problem of automatic installation of a server environment under parallel incremental version transmission of multiple software versions can be further solved, differential incremental coverage of software versions can be implemented, and it is ensured that a correct file can still be installed in a target environment under the condition that the version installation order is adjusted.
In order to further overcome the problem of automatic installation of a server environment under parallel incremental version of multiple software versions, in an embodiment of the software version transmission method provided by the present application, referring to fig. 10, step 300 in the software version transmission method further includes the following steps:
step 360: if the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is different from the compiling version number of the target intelligent installation strategy package, and the compiling version number of the target intelligent installation strategy package is larger than the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
As can be seen from the above description, in the software version transmission method provided in this embodiment of the present application, by determining whether the compilation version number of the target intelligent installation policy package is greater than the compilation version number of the intelligent installation policy package that is the same as the target intelligent installation policy package in the environment list, the problem of automatic installation of a server environment under parallel incremental version release of multiple software versions can be further overcome, differential incremental coverage of software versions can be realized, and it is ensured that a correct file can still be installed in a target environment under the condition that the version installation order is adjusted.
Based on the above, in an embodiment of the software version transmission method provided in the present application, the complete determination process of step 300 in the software version transmission method may specifically include the following steps:
step 1: judging whether an environment list of a target test environment contains an intelligent installation strategy package which is the same as the target intelligent installation strategy package;
if not, executing the step 2;
if yes, executing step 3;
step 2; transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to perform coverage processing of corresponding files, updating an environment list of the target test environment, and outputting corresponding file coverage results;
and step 3: judging whether the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment;
if yes, executing step 4;
if not, executing step 7;
step 4; judging whether the hash code corresponding to the target intelligent installation strategy package covers the hash code of the intelligent installation strategy package in the target test environment;
if yes, executing step 2: transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to perform coverage processing of corresponding files, updating an environment list of the target test environment, and outputting corresponding file coverage results;
if not, executing the step 5;
and 5: judging whether the target intelligent installation strategy package is a configuration file;
if yes, executing step 2: transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to perform coverage processing of corresponding files, updating an environment list of the target test environment, and outputting corresponding file coverage results;
if not, executing the step 6;
step 6: the file coverage processing is not carried out on the target test environment;
and 7: judging whether the compiling version number (such as the version number of an intelligent bank ecosystem) of an intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compiling version number of the target intelligent installation strategy package;
if yes, executing step 8;
if not, executing step 9;
and 8: judging whether the compiling time of an intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is longer than that of the target intelligent installation strategy package;
if yes, executing step 6: the file coverage processing is not carried out on the target test environment;
if not, executing the step 2: transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to perform coverage processing of corresponding files, updating an environment list of the target test environment, and outputting corresponding file coverage results;
and step 9: judging whether the compiling version number (such as the version number of an intelligent bank ecosystem) of an intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is greater than the compiling version number of the target intelligent installation strategy package;
if yes, executing step 6: the file coverage processing is not carried out on the target test environment;
if not, executing the step 2: and transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to perform coverage processing of corresponding files, updating an environment list of the target test environment, and outputting corresponding file coverage results.
In terms of software, in order to solve the problems that an original version file is easily covered by an error due to the fact that an existing software version transmission mode only supports full file coverage, so that a test environment is not usable, a new software version cannot be correctly created in a test switch, a service test cannot be smoothly performed, a normal production environment for service requirements is affected, and the like, in the existing software version transmission mode, the application provides an embodiment of a software version transmission device for executing all or part of contents in the software version transmission method, and referring to fig. 11, the software version transmission device specifically includes the following contents:
and the template generating module 10 is configured to generate a corresponding target installation template according to at least one policy item corresponding to the target policy package information.
And the policy package creating module 20 is configured to perform packaging processing on the target installation template, and generate corresponding compiling time, compiling version number, and hash code to obtain a target intelligent installation policy package corresponding to the target software version.
And the version transmission module 30 is configured to transmit the target intelligent installation policy package to a target test environment according to the compiling time, the compiling version number, and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment.
The embodiment of the software version transmission apparatus provided in the present application may be specifically configured to execute the processing procedure of the embodiment of the software version transmission method in the foregoing embodiment, and the functions of the embodiment are not described herein again, and refer to the detailed description of the embodiment of the method.
As can be seen from the above description, the software version transmission apparatus provided in the embodiment of the present application generates the corresponding target installation template according to the at least one policy item corresponding to the target policy package information, so that different requirements for creating policy configuration of each software version file can be met, and the application universality and comprehensiveness of software version transmission can be effectively improved; the target installation template is packaged, and corresponding compiling time, compiling version number and hash code are generated to obtain a target intelligent installation strategy package corresponding to the target software version, so that the effectiveness of generating the intelligent installation strategy package can be effectively improved, and a reliable and effective data base is provided for subsequent software version transmission; the target intelligent installation strategy package is transmitted to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, so that the problem of automatic installation of a server environment under parallel incremental version distribution of a plurality of software versions can be solved, differential incremental coverage of the software versions can be realized, and correct files can still be installed in the target environment under the condition that the version installation sequence is adjusted; that is to say, the method and the device can create the target software version which is not created according to the original installation sequence in the test environment with at least one software version installed, and further can meet the requirement of creating different software versions in one test environment for many times.
How to maintain the testability and stability of the test environment and ensure the consistency of the running states of the test environment and the production environment is a pain point of the current testers.
The traditional versions are automatically installed, file transmission only supports complete coverage of files, files on a code level coverage environment cannot be automatically judged and realized according to version numbers, compiling time and the like, under the condition that multiple versions are parallel, the situation that original version files are mistakenly covered due to different installation sequences of the versions appears for multiple times in a test environment, so that service test cannot be smoothly carried out, and normal input of service requirements into a production environment is influenced.
In order to solve the problems, the application example of the application designs a code-level software version transmission method, belongs to the technical field of automatic deployment file transmission of a server environment, overcomes the problem of automatic installation of the server environment under multi-version parallel incremental version sending, realizes version differentiation increment coverage, ensures that correct files can still be installed in a target environment under the condition of adjusting version installation sequence, tries to solve the problem of automatic installation error reporting of the current server environment, and improves environment testability.
Referring to fig. 12, the software version transmission method provided by the application example of the present application includes four parts, which are respectively: the method comprises the following steps of modifying an installation strategy, configuring a version number, constructing an automatic version and transmitting an intelligent file, wherein main modules and functions of each part are as follows:
1. and (3) modification of an installation strategy:
before the version is manufactured, an installation strategy needs to be newly added for intelligent file transmission, the purpose is to support intelligent file transmission, and the purpose is to support automatic version installation. For the source FILE of intelligent transmission, the source FILE is fixedly stored in the directory of 'version program/ATOMIC _ FILE' in the version. The strategy package is newly added in the step to be an intelligent strategy package, and the transmission of the intelligent file is realized.
The system acquires newly added strategy package information recorded on a page, records the strategy package information into a database strategy package table (VACP _ INSTALL _ POLICY _ PKG), records the newly added strategy package information through the front end of the system, correlates and compiles the strategy table (BUILD _ POLICY) through the strategy package ID, and stores the strategy package as a template function, so that the strategy package can be quickly stored as an installation template for compiling. The correspondence between the policy package table and the compilation policy table is shown in fig. 13.
2. Configuration version number
The version number is an important judgment basis for intelligent file transmission, the version number contains the version of the intelligent strategy package, the version is checked in the version construction process, and the version without the version number cannot be constructed. The system writes the information into the VERSION information table (VACP _ BUILD _ VERSION _ INFO) through the application environment maintenance interface.
3. Version construction
The intelligent version construction generates an 'ATOMIC _ file.zip' FILE under a 'version program' path, opens the 'ATOMIC _ file.zip', and writes the automatically generated content into a first row: a version number; writing in the second row: compiling time; writing in the third row: base line/label, base line label information of all tasks corresponding to the task; fourth row write: compiling a version number; fifth row write: information of all files (not including directories) under the intelligent folder (including sub-directories), SHA1 code of relative path | file of file, one line per file. Zip is generated with added checking information, and the correctness of the zip package is checked when the version is imported, so that the content of the zip file cannot be manually modified.
4. Intelligent file transfer
The device records an installation file list of each environment, including information such as SHA1 code, compilation version number, compilation time, version number and the like of each file, and referring to fig. 14, the execution logic of the intelligent file transmission is as follows:
a. if the environment does not have the current file, covering;
b. if the current version file is the same as the SHA1 code of the environment file;
if the partition parameter AtomicSHA1SameCoverFlag is true, then coverage is returned, otherwise no coverage is performed.
If the partition parameter AtomicSHA1SameCoverFlag is false and is a configuration file, returning to be covered, otherwise, not covering.
c. If the current version file is not the same as the SHA1 code of the file of the environment
The version number of the file in the environment list is larger than that of the version list and is not covered;
the version number of the file in the environment list is smaller than the version number of the version list;
and thirdly, judging whether the version number of the file in the environment list is equal to the version number of the version list according to the compiling time: if the compiling time of the environment list is less than or equal to that of the version list, the environment list is covered, otherwise, the environment list is not covered.
And after each intelligent transmission item is completed, updating the file information in the environment for the covered files, and covering the file information in the environment by using the file information in the version.
And for the installation task containing intelligent file transmission, after the installation task is successfully executed, downloading an intelligent file coverage list. The list content comprises information of each intelligent file related to the task, information of files with the same name in the environment and a coverage result.
To further explain the present disclosure, the present application further provides an example 1 of a software version transmission method, which specifically includes the following contents:
the testing environment is always consistent with the production, and the correctness of the business testing process can be ensured. Taking a 5-month-version temporary service group of a personal mobile phone bank in Asia gray level of a certain bank as an example, the group completes intelligent file transmission transformation. The server environment has now installed the version for 5 months V1.16.0425.0, and the device records environment information, looks at the ATOMIC _ FILE _ list. On the same day, 4 months release production patch V1.15.06001.0 was delivered. If not, the installation and the error report can be carried out, the environmental information is inconsistent with the production, and the service test can not be carried out. After transformation, the device can automatically implement intelligent file transmission. For example, SUSE/WEB server (four overseas)/xxBCWAPUS/abroadperbank/downLoad/abroadperbank. zip, the version 5 of V1.16.0425.0 is consistent with the file marked by the version 4 month production patch V1.15.06001.0, but the SHA1 code is not the same, and the version 5 month of V1.16.0425.0 is the version 4 month version number of the file with the version 5 month server environment installed greater than the version 4 month production patch V1.15.06001.0, so the file will not be transmitted, and the server environment always keeps the code level up to date. Files that do not exist in the environment are transmitted.
To further explain the present disclosure, the present application further provides an example 2 of a software version transmission method, which specifically includes the following contents:
because the versions are delivered according to the required item versions, the testing environment always faces the versions of a plurality of production points, the environment testing of testing patch versions on different production days is met, namely, the multi-version parallel testing is carried out, and the intelligent file transmission device can meet the requirement of service testing sufficiency.
The software version transmission method provided by the application example of the application example has the following beneficial effects:
1. the technical method aims at the problem of environment installation of the multi-version parallel increment version-sending server, the provided code-level intelligent file transmission design is very flexible, and the situation of file coverage caused by different version installation sequences is avoided.
2. The technical method greatly improves the testability of the server environment, and only after technical personnel are modified according to the technical scheme, the subsequent whole process is completely automatically realized by the system without manual intervention in the case of continuously increasing the version level.
3. The technical scheme is a universal method and idea for version testing, can be widely popularized and used, is used for improving the environmental testing efficiency and quality, and provides the automation level of version installation.
In terms of hardware, in order to solve the problems that an original version file is easily covered by an error due to the fact that an existing software version transmission method only supports full file coverage, so that a test environment is not usable, a new software version cannot be correctly created in a test switch, a service test cannot be smoothly performed, a normal production environment for service requirements is affected, and the like, in the existing software version transmission method, the electronic device specifically includes the following contents:
fig. 15 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 15, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 15 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.
In one embodiment, the software version transfer function may be integrated into the central processor. Wherein the central processor may be configured to control:
step 100: and generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information.
Step 200: and packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version.
Step 300: and transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
As can be seen from the above description, according to the electronic device provided in the embodiment of the present application, the corresponding target installation template is generated according to the at least one policy item corresponding to the target policy package information, so that different requirements for creating policy configuration of each software version file can be met, and the application universality and comprehensiveness of software version transmission can be effectively improved; the target installation template is packaged, and corresponding compiling time, compiling version number and hash code are generated to obtain a target intelligent installation strategy package corresponding to the target software version, so that the effectiveness of generating the intelligent installation strategy package can be effectively improved, and a reliable and effective data base is provided for subsequent software version transmission; the target intelligent installation strategy package is transmitted to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, so that the problem of automatic installation of a server environment under parallel incremental version distribution of a plurality of software versions can be solved, differential incremental coverage of the software versions can be realized, and correct files can still be installed in the target environment under the condition that the version installation sequence is adjusted; that is to say, the method and the device can create the target software version which is not created according to the original installation sequence in the test environment with at least one software version installed, and further can meet the requirement of creating different software versions in one test environment for many times.
In another embodiment, the software version transmission device may be configured separately from the central processor 9100, for example, the software version transmission device may be configured as a chip connected to the central processor 9100, and the software version transmission function is realized by the control of the central processor.
As shown in fig. 15, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 15; further, the electronic device 9600 may further include components not shown in fig. 15, which can be referred to in the related art.
As shown in fig. 15, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.
The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.
The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.
The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.
The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).
The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.
Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.
Embodiments of the present application further provide a computer-readable storage medium capable of implementing all steps in the software version transmission method in the foregoing embodiments, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements all steps of the software version transmission method in which an execution subject is a server or a client, for example, when the processor executes the computer program, the processor implements the following steps:
step 100: and generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information.
Step 200: and packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version.
Step 300: and transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
As can be seen from the above description, the computer-readable storage medium provided in the embodiment of the present application, by generating the corresponding target installation template according to the at least one policy item corresponding to the target policy package information, can meet different requirements for creating policy configuration of each software version file, and can effectively improve the application universality and comprehensiveness of software version transmission; the target installation template is packaged, and corresponding compiling time, compiling version number and hash code are generated to obtain a target intelligent installation strategy package corresponding to the target software version, so that the effectiveness of generating the intelligent installation strategy package can be effectively improved, and a reliable and effective data base is provided for subsequent software version transmission; the target intelligent installation strategy package is transmitted to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, so that the problem of automatic installation of a server environment under parallel incremental version distribution of a plurality of software versions can be solved, differential incremental coverage of the software versions can be realized, and correct files can still be installed in the target environment under the condition that the version installation sequence is adjusted; that is to say, the method and the device can create the target software version which is not created according to the original installation sequence in the test environment with at least one software version installed, and further can meet the requirement of creating different software versions in one test environment for many times.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims (12)

1. A method for transmitting a software version, comprising:
generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information;
packaging the target installation template, and generating corresponding compiling time, compiling version number and hash code to obtain a target intelligent installation strategy package corresponding to the target software version;
and transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
2. The method for transmitting software versions according to claim 1, wherein the generating a target installation template including a target software version according to at least one policy item corresponding to the target policy package information includes:
receiving target strategy package information, wherein the target strategy package information comprises a strategy package name, a strategy package identification and informing information for indicating whether the target strategy package is an intelligent package;
if the notification information corresponding to the target policy package information indicates that the installation policy package corresponding to the target policy package information is an intelligent package, acquiring at least one policy item corresponding to the target policy package information from the corresponding relationship between each pre-stored policy package identifier and each policy item;
and generating a target installation template corresponding to the target strategy package information according to at least one strategy item, the strategy package name and the strategy package identification corresponding to the target strategy package information.
3. The software version transmission method according to claim 1, wherein the target policy package information further contains an initial version number of the target policy package;
correspondingly, before the packaging processing of the target installation template, the method further includes:
and storing the initial version number of the target strategy package corresponding to the target installation template.
4. The method for transmitting software versions according to claim 3, wherein the step of packaging the target installation template and generating corresponding compilation time, compilation version number and hash code to obtain a target intelligent installation policy package corresponding to a target software version includes:
packaging the target installation template to generate a compiling version number corresponding to the initial version number of the target strategy package, and generating a corresponding label, compiling time and a hash code to obtain a target intelligent installation strategy package of the target software version corresponding to the target strategy package information;
the target intelligent installation strategy package is further provided with an intelligent file list, and the intelligent file list is used for storing all file information and relative paths corresponding to the initial version number, the compiling time, the label, the compiling version number, the hash code and the target software version.
5. The method for transmitting software version according to claim 4, wherein before transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number and the hash code of the target intelligent installation policy package to construct the corresponding target software version in the target test environment, the method further comprises:
acquiring a current environment list of a target test environment;
and judging whether the environment list contains an intelligent installation strategy package with the same strategy package name and/or strategy package identification as the target intelligent installation strategy package, if not, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
6. The method for transmitting software versions according to claim 5, wherein the transmitting the target intelligent installation policy package to a target test environment according to the compilation time, the compilation version number and the hash code of the target intelligent installation policy package to construct a corresponding target software version in the target test environment comprises:
if the environment list is judged to contain the intelligent installation strategy package which is the same as the target intelligent installation strategy package, judging whether the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment;
if the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment, and if the hash code corresponding to the target intelligent installation strategy package already covers the hash code of the intelligent installation strategy package in the target test environment, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating an environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
7. The method for transmitting software versions according to claim 6, wherein the transmitting the target smart installation policy package to a target test environment according to the compilation time, the compilation version number and the hash code of the target smart installation policy package to construct a corresponding target software version in the target test environment further comprises:
if the hash code corresponding to the target intelligent installation strategy package is the same as the hash code of the intelligent installation strategy package in the target test environment, the hash code corresponding to the target intelligent installation strategy package does not cover the hash code of the intelligent installation strategy package in the target test environment, and the target intelligent installation strategy package is a configuration file, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating an environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
8. The method for transmitting software versions according to claim 7, wherein the transmitting the target smart installation policy package to a target test environment according to the compilation time, the compilation version number and the hash code of the target smart installation policy package to construct a corresponding target software version in the target test environment further comprises:
if the hash code corresponding to the target intelligent installation strategy package is different from the hash code of the intelligent installation strategy package in the target test environment, judging whether the compilation version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compilation version number of the target intelligent installation strategy package;
if the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is the same as the compiling version number of the target intelligent installation strategy package, and the compiling time of the target intelligent installation strategy package is longer than the compiling time of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
9. The method for transmitting software versions according to claim 8, wherein the transmitting the target smart installation policy package to a target test environment according to the compilation time, the compilation version number and the hash code of the target smart installation policy package to construct a corresponding target software version in the target test environment further comprises:
if the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list is different from the compiling version number of the target intelligent installation strategy package, and the compiling version number of the target intelligent installation strategy package is larger than the compiling version number of the intelligent installation strategy package which is the same as the target intelligent installation strategy package in the environment list, transmitting the target intelligent installation strategy package to the target test environment based on the target intelligent installation strategy package to construct a corresponding target software version in the target test environment, updating the environment list of the target test environment based on the target software version, and outputting a corresponding target software version construction result.
10. A software version transmission apparatus, comprising:
the template generating module is used for generating a corresponding target installation template according to at least one strategy item corresponding to the target strategy package information;
the strategy package creating module is used for packaging the target installation template and generating corresponding compiling time, compiling version number and hash code so as to obtain a target intelligent installation strategy package corresponding to the target software version;
and the version transmission module is used for transmitting the target intelligent installation strategy package to a target test environment according to the compiling time, the compiling version number and the hash code of the target intelligent installation strategy package so as to construct a corresponding target software version in the target test environment.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the software version transmission method of any one of claims 1 to 9 when executing the computer program.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the software version transmission method of any one of claims 1 to 9.
CN202110793900.6A 2021-07-14 2021-07-14 Software version transmission method and device Pending CN113535558A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110793900.6A CN113535558A (en) 2021-07-14 2021-07-14 Software version transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110793900.6A CN113535558A (en) 2021-07-14 2021-07-14 Software version transmission method and device

Publications (1)

Publication Number Publication Date
CN113535558A true CN113535558A (en) 2021-10-22

Family

ID=78099002

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110793900.6A Pending CN113535558A (en) 2021-07-14 2021-07-14 Software version transmission method and device

Country Status (1)

Country Link
CN (1) CN113535558A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114268624A (en) * 2022-03-02 2022-04-01 上海豪承信息技术有限公司 Version file transmission method and device and server

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110647739A (en) * 2019-07-26 2020-01-03 平安科技(深圳)有限公司 Software installation detection method, device, terminal and storage medium
CN110659210A (en) * 2019-09-20 2020-01-07 深圳创维-Rgb电子有限公司 Information acquisition method and device, electronic equipment and storage medium
CN112799944A (en) * 2021-01-29 2021-05-14 中国工商银行股份有限公司 System performance testing method and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110647739A (en) * 2019-07-26 2020-01-03 平安科技(深圳)有限公司 Software installation detection method, device, terminal and storage medium
CN110659210A (en) * 2019-09-20 2020-01-07 深圳创维-Rgb电子有限公司 Information acquisition method and device, electronic equipment and storage medium
CN112799944A (en) * 2021-01-29 2021-05-14 中国工商银行股份有限公司 System performance testing method and system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114268624A (en) * 2022-03-02 2022-04-01 上海豪承信息技术有限公司 Version file transmission method and device and server
CN114268624B (en) * 2022-03-02 2022-06-03 上海豪承信息技术有限公司 Version file transmission method and device and server

Similar Documents

Publication Publication Date Title
US8612947B2 (en) System and method for remotely compiling multi-platform native applications for mobile devices
CN109739523B (en) Application program packaging method and device, storage medium and terminal
CN107979508A (en) Micro services test method and device
CN108255708B (en) Method, device, storage medium and equipment for accessing production file in test environment
CN111786885A (en) Distributed full-link gray level routing method and device
CN111459539A (en) Continuous integration pipeline operation method and device based on mirror layering
CN112463634A (en) Software testing method and device under micro-service architecture
US8527986B1 (en) System and method for automated identification of an application out-of-synchronization condition
CN112328293A (en) Differential upgrading method of embedded equipment and related components
CN113535558A (en) Software version transmission method and device
CN113485952A (en) Data batch transmission method and device
CN110675894B (en) HDCP key online burning method and device and electronic equipment
CN107479923A (en) Application program updating method, apparatus and display terminal
CN113452776B (en) PaaS platform service scheduling method and device and PaaS platform
CN113505076A (en) File coverage detection method and device
CN114285657A (en) Firewall security policy change verification method and device
CN113791984A (en) Automatic interface testing method and device
CN113377385A (en) Client automatic deployment method and device
CN113050985A (en) Front-end engineering dependence automatic registration method and device
CN109428936B (en) APP upgrading method, device, system, electronic equipment and storage medium
CN113268272A (en) Application delivery method, device and system based on private cloud
CN113127370A (en) Report system smoking test method, RPA robot and system
CN113347033A (en) Root cause positioning method and system based on block chain and verification node
CN111930624A (en) Test link message data processing method and device
CN113239297A (en) Message pushing method, system 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