CN114064073A

CN114064073A - Software version upgrading method and device, computer equipment and storage medium

Info

Publication number: CN114064073A
Application number: CN202111299697.3A
Authority: CN
Inventors: 王金余; 丁文定; 徐平; 张雯
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-11-04
Filing date: 2021-11-04
Publication date: 2022-02-18

Abstract

The application relates to a software version upgrading method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring a configuration file to be upgraded of software to be upgraded, and storing the version identification and the preset upgrading time of the configuration file to be upgraded in a database; the database also stores the actual upgrade time of a plurality of historical configuration files of the software to be upgraded; acquiring an input target version identifier and target upgrading time corresponding to the target version identifier; when the version identification of the configuration file to be upgraded is matched with the target version identification, updating the preset upgrading time of the configuration file to be upgraded to the target upgrading time to obtain the actual upgrading time of the updated configuration file to be upgraded; and screening out the configuration file with the latest actual upgrading time from the updated configuration file to be upgraded and a plurality of historical configuration files to be used as a target configuration file of the software to be upgraded. The method can improve the flexibility of software version upgrading.

Description

Software version upgrading method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for upgrading a software version, a computer device, a storage medium, and a computer program product.

Background

With the development of banking business, the number of application systems in a bank is increasing, and the scale of data exchange among a plurality of systems is also increasing, and the scale of data exchange per day can reach hundreds of TBs (terabytes). In order to maintain the performance of the internal system of the bank, the version of the data exchange system needs to be updated regularly, however, the number of files involved in the version updating process of the data exchange system can reach tens of thousands, which greatly increases the complexity of software version updating. In addition, as the development cycle of the data exchange system is continuously shortened, the requirement on the production time of the system is shorter and shorter.

The traditional software version upgrading is generally a software version with fixed upgrading time, and the software version with fixed upgrading time is not suitable for a data exchange system with flexible change of current production time. If the software version with fixed upgrading time is continuously adopted, when the upgrading time is suddenly changed in the research and development process in the bank, the released software version can only be backed off, and the software version is released after the upgrading time is modified, so that the upgrading efficiency of the software version is reduced, and the upgrading time of the software is also limited.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a software version upgrade method, apparatus, computer device, storage medium, and computer program product capable of improving flexibility of software version upgrade.

In a first aspect, the present application provides a software version upgrading method, including:

acquiring a configuration file to be upgraded of software to be upgraded, and storing the version identification and the preset upgrading time of the configuration file to be upgraded in a database; the database also stores the actual upgrading time of a plurality of historical configuration files of the software to be upgraded;

acquiring an input target version identifier and target upgrading time corresponding to the target version identifier;

when the version identification of the configuration file to be upgraded is matched with the target version identification, updating the preset upgrading time of the configuration file to be upgraded to the target upgrading time to obtain the actual upgrading time of the updated configuration file to be upgraded;

and screening out the configuration file with the latest actual upgrading time from the updated configuration file to be upgraded and the plurality of historical configuration files to be used as the target configuration file of the software to be upgraded.

In one embodiment, acquiring a configuration file to be upgraded of software to be upgraded, and storing a version identifier of the configuration file to be upgraded and a preset upgrade time in a database includes:

acquiring a configuration file of the software to be upgraded, and modifying the configuration file for multiple times to obtain multiple modified configuration files of the configuration file;

screening the configuration files to be upgraded from the plurality of modified configuration files; the configuration file to be upgraded is a modified configuration file obtained by the last modification;

and reading the version identification and the preset upgrading time of the configuration file to be upgraded, and storing the version identification and the preset upgrading time to the database.

In one embodiment, acquiring an input target version identifier and a target upgrade time corresponding to the target version identifier includes:

receiving an upgrading task of the software to be upgraded;

and extracting the target version identification and the target upgrading time corresponding to the target version identification from the upgrading task.

In one embodiment, when the version identifier of the configuration file to be upgraded is matched with the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and before obtaining the actual upgrade time of the configuration file to be upgraded, the method further includes:

inquiring to obtain a version identification matched with the target version identification from the database;

updating the actual upgrading time corresponding to the version identification matched with the target version identification in the database into the target upgrading time;

when the version identifier of the configuration file to be upgraded is matched with the target version identifier, updating the preset upgrading time of the configuration file to be upgraded to the target upgrading time, including:

and when the version identification of the configuration file to be upgraded is matched with the target version identification, updating the preset upgrading time of the configuration file to be upgraded to the target upgrading time stored in the database.

In one embodiment, after obtaining the actual upgrade time of the updated configuration file to be upgraded, the method further includes:

inquiring to obtain a historical configuration file matched with the updated configuration file to be upgraded from the plurality of historical configuration files;

and adjusting the effective time of the historical configuration file matched with the updated configuration file to be upgraded to be the difference between the actual upgrading time of the updated configuration file to be upgraded and a preset threshold value.

In one embodiment, screening out a configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the plurality of historical configuration files, as a target configuration file of the software to be upgraded, includes:

inquiring actual upgrade time stored in the database and obtaining latest actual upgrade time and a version identification corresponding to the latest actual upgrade time;

and inquiring the configuration file matched with the version identification corresponding to the latest actual upgrading time from the updated configuration file to be upgraded and the plurality of historical configuration files to be used as the target configuration file of the software to be upgraded.

In one embodiment, after screening out a configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the plurality of historical configuration files, as a target configuration file of the software to be upgraded, the method further includes:

when the target configuration file is detected to be the actual upgrade file of the software to be upgraded, generating operation data corresponding to the target configuration file;

and upgrading the software to be upgraded according to the running data corresponding to the target configuration file.

In a second aspect, the present application further provides a software version upgrading apparatus, including:

the file acquisition module is used for acquiring a configuration file to be upgraded of software to be upgraded and storing the version identification and the preset upgrading time of the configuration file to be upgraded to a database; the database also stores the actual upgrading time of a plurality of historical configuration files of the software to be upgraded;

the time acquisition module is used for acquiring an input target version identifier and target upgrading time corresponding to the target version identifier;

the update time module is used for updating the preset update time of the configuration file to be updated to the target update time when the version identification of the configuration file to be updated is matched with the target version identification, so as to obtain the actual update time of the configuration file to be updated;

and the file screening module is used for screening out the configuration file with the latest actual upgrading time from the configuration file to be upgraded and the plurality of historical configuration files to be used as the target configuration file of the software to be upgraded.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:

In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:

In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:

According to the software version upgrading method, the device, the computer equipment and the storage medium, the version identification and the preset upgrading time of the configuration file to be upgraded are stored in the database according to the acquired configuration file to be upgraded of the software to be upgraded, then the input target version identification and the target upgrading time corresponding to the target version identification are acquired, when the version identification of the configuration file to be upgraded is matched with the target version identification, the preset upgrading time of the configuration file to be upgraded is updated to the target upgrading time, the actual upgrading time of the updated configuration file to be upgraded is acquired, and finally the configuration file with the latest actual upgrading time is screened out from the updated configuration file to be upgraded and a plurality of historical configuration files and serves as the target configuration file of the software to be upgraded. By adopting the method, the actual upgrading time of the configuration file to be upgraded is not required to be determined in advance, and the upgrading time of the configuration file to be upgraded is updated to the actual upgrading time, so that the upgrading time of the configuration file to be upgraded can be changed in real time according to the actual development requirement, and the flexibility of software version upgrading is improved.

Drawings

FIG. 1 is a diagram of an application environment of a software version upgrade method in one embodiment;

FIG. 2 is a flowchart illustrating a software version upgrade method according to an embodiment;

FIG. 3 is a flowchart illustrating a software version upgrade method according to another embodiment;

FIG. 4 is a flowchart illustrating a software version upgrade method according to yet another embodiment;

FIG. 5 is a flow diagram that illustrates the steps of the data verification module and the version configuration module in one embodiment;

FIG. 6 is a block diagram showing the configuration of a software version-up apparatus according to an embodiment;

FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The software version upgrading method provided by the application can be applied to the application environment shown in fig. 1. The server 101 communicates with the terminal 102 and the database 103 through a network, and the database 103 is used for storing version identifiers, preset upgrading time and actual upgrading time of each configuration file of software to be upgraded. Specifically, referring to fig. 1, a server 101 obtains a to-be-upgraded configuration file of software to be upgraded, and stores a version identifier and preset upgrade time of the to-be-upgraded configuration file to a database 103, the server 101 receives a target version identifier input by a terminal 102 and target upgrade time corresponding to the target version identifier, when the version identifier of the to-be-upgraded configuration file matches the target version identifier, the server 101 updates the preset upgrade time of the to-be-upgraded configuration file to the target upgrade time to obtain actual upgrade time of the updated to-be-upgraded configuration file, and the server 101 screens out a configuration file with the latest actual upgrade time from the updated to-be-upgraded configuration file and a plurality of historical configuration files to serve as the target configuration file of the software to be upgraded. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like. The server 101 may be implemented as a stand-alone server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, a software version upgrading method is provided, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:

step S201, acquiring a configuration file to be upgraded of software to be upgraded, and storing the version identification and the preset upgrading time of the configuration file to be upgraded in a database; the database also stores actual upgrade times for a plurality of historical configuration files of software to be upgraded.

The software to be upgraded is software which needs to be upgraded in an internal system of the banking industry. The configuration file to be upgraded is a configuration file which is newly developed according to an upgrading task of the software to be upgraded, the configuration file to be upgraded comprises a sealing plate configuration file and a daily patch configuration file of the software to be upgraded, and the upgrading time of the configuration file to be upgraded can be adjusted along with the actual upgrading task. The shrouding configuration file is a configuration file of a software upgrading version obtained after the development of a preset period and is used for the periodic upgrading of the software to be upgraded. The daily patch configuration file refers to a patch upgrading configuration file of the software to be upgraded and is used for daily upgrading of the software to be upgraded.

The historical configuration file refers to a configuration file of software to be upgraded which is upgraded. The version identifier is version number information of the configuration file and is used for distinguishing the version of the configuration file, and the version identifier comprises a version number. The preset upgrading time refers to a virtual upgrading time timestamp and is used for setting a temporary virtual timestamp for the configuration file to be upgraded. And the database stores various historical configuration files of the software to be upgraded, version identifications of the configuration files to be upgraded, preset upgrading time, actual upgrading time and demand numbers.

Specifically, the server derives file information of software to be upgraded from the metadata database, generates a corresponding configuration file to be upgraded according to the file information of the software to be upgraded, and stores the configuration file to be upgraded in a preset directory; the file format, the basic information and the configuration information of the configuration file to be upgraded are obtained from the configuration file to be upgraded, the server obtains the version identification and the preset upgrading time of the configuration file to be upgraded, and then the version identification and the preset upgrading time are stored in a table of a database.

For example, the file format of the acquired configuration file to be upgraded is: the configuration file to be upgraded comprises basic information of configuration contents such as file source interface and target interface, file newly added (deleted) identification, field information, field filtering information, upstream downloading information, file transmission approval id and the like.

Step S202, the input target version identification and the target upgrading time corresponding to the target version identification are obtained.

The target version identification refers to a version identification of a target upgrading version set by a research and development worker or a management worker according to an upgrading task of software to be upgraded. The target upgrading time refers to a timestamp of the upgrading time of the target upgrading version set by a research and development worker or a management worker according to the upgrading task of the software to be upgraded.

Specifically, a research and development person or a manager inputs a target version identifier and target upgrade time corresponding to the target version identifier into a server through a terminal, and the server receives the target version identifier and the target upgrade time corresponding to the target version identifier. Therefore, after the server obtains the target version identification and the target upgrading time corresponding to the target version identification, the server executes the subsequent software version upgrading step by taking the target version identification and the target upgrading time corresponding to the target version identification as matching bases.

Step S203, when the version identification of the configuration file to be upgraded is matched with the target version identification, updating the preset upgrading time of the configuration file to be upgraded to the target upgrading time to obtain the actual upgrading time of the updated configuration file to be upgraded.

Specifically, the server judges whether the version identification of the configuration file to be upgraded stored in the database is matched with the target version identification, if the version identification of the configuration file to be upgraded stored in the database is matched with the target version identification, the target upgrading time is stored to the actual upgrading time of the configuration file to be upgraded in the database, then the configuration file to be upgraded is updated, the preset upgrading time of the configuration file to be upgraded is updated to the target upgrading time, and the updated configuration file to be upgraded is obtained.

And step S204, screening out the configuration file with the latest actual upgrading time from the updated configuration file to be upgraded and a plurality of historical configuration files, and taking the configuration file as a target configuration file of the software to be upgraded.

Specifically, the database screens out the latest actual upgrade time from the stored updated configuration files to be upgraded and the actual upgrade time corresponding to the plurality of historical configuration files, acquires the version identification corresponding to the latest actual upgrade time, then sends the latest actual upgrade time and the version identification corresponding to the latest actual upgrade time to the server, and the server receives and inquires the version identification to obtain the corresponding configuration files as target configuration files of the software to be upgraded, stores the target configuration files to a preset directory, and upgrades the version of the software to be upgraded when the actual upgrade time of the target configuration files is reached.

According to the software version upgrading method, the version identification and the preset upgrading time of the configuration file to be upgraded are stored in a database according to the acquired configuration file to be upgraded of the software to be upgraded, then the input target version identification and the target upgrading time corresponding to the target version identification are acquired, when the version identification of the configuration file to be upgraded is matched with the target version identification, the preset upgrading time of the configuration file to be upgraded is updated to the target upgrading time, the actual upgrading time of the updated configuration file to be upgraded is obtained, and finally the configuration file with the latest actual upgrading time is screened out from the updated configuration file to be upgraded and a plurality of historical configuration files and serves as the target configuration file of the software to be upgraded. By adopting the method, the actual upgrading time of the configuration file to be upgraded is not required to be determined in advance, and the upgrading time of the configuration file to be upgraded is updated to the actual upgrading time, so that the upgrading time of the configuration file to be upgraded can be changed in real time according to the actual development requirement, and the flexibility of software version upgrading is improved.

In an embodiment, in step S201, obtaining a configuration file to be upgraded of software to be upgraded, and storing a version identifier of the configuration file to be upgraded and a preset upgrade time in a database, the method specifically includes the following steps: acquiring a configuration file of software to be upgraded, and modifying the configuration file for multiple times to obtain multiple modified configuration files of the configuration file; screening a configuration file to be upgraded from a plurality of modified configuration files; the configuration file to be upgraded is a modified configuration file obtained by the last modification; and reading the version identification and the preset upgrading time of the configuration file to be upgraded, and storing the version identification and the preset upgrading time into a database.

Specifically, the server uses an export tool to export data information of software to be upgraded from a metadata base to obtain a configuration file of the software to be upgraded, the configuration file is stored in a temporary directory, the configuration file is subjected to addition, modification or deletion according to an upgrade task of the software to be upgraded, a modification configuration file is generated after each processing, a file transmission approval id of the modification configuration file is recorded, and a plurality of modification configuration files are obtained after the processing; detecting file transmission approval ids of the plurality of modified configuration files, reserving the modified configuration file obtained by the last modification, namely the configuration file corresponding to the last file transmission approval id, as a configuration file to be upgraded, setting a timestamp of preset upgrading time of the configuration file to be upgraded, and storing the configuration file to be upgraded in a preset directory; and performing data reading processing on the configuration file to be upgraded through the file reading instruction, reading the version identification and the preset upgrading time of the configuration file to be upgraded, and storing the version identification and the preset upgrading time of the configuration file to be upgraded into a table of the database.

For example, the version identifier and the preset upgrade time of the configuration file to be upgraded are stored in a table cfg _ validTime in the database, and the field structure of the table is shown in table 1:

TABLE 1

Name of field	Type of field	Use of
			APPVER	VARchar2	And the version number is used for distinguishing the production time of different configuration files.
DEPLOYDATE	VARchar2	And the production time corresponding to the version number.
			YTIME	VARchar2	And presetting production time corresponding to the version number.
REITEMID	VARchar2	Requirement number, reserved field.

It should be noted that, due to the fast iteration of the upgrade requirement in the development process of the software to be upgraded, the configuration file to be upgraded may not have obtained the actual upgrade time, or the configuration file to be upgraded may have obtained the actual upgrade time but needs to be modified later with the change of the upgrade task, so a virtual preset upgrade time (YTIME) is set for the configuration file to be upgraded, assuming that the actual upgrade time of the current configuration file to be upgraded is T, the preset upgrade time may be set to T, T-1, T-2, T +1, T +2, and the like, and may of course be adjusted according to the actual situation, and is not specifically limited herein. If the actual upgrade time (DEPLOYDATE) of the configuration file to be upgraded is not obtained yet, the actual upgrade time corresponding to the version identifier (APPVER) of the configuration file to be upgraded in the database may be set to T, or a NULL value (NULL), or a random number is filled.

In the embodiment, the configuration file to be upgraded of the software to be upgraded is obtained, and the version identifier and the preset upgrading time are stored in the database, by adopting the method, the fixed upgrading time does not need to be preset in the configuration file to be upgraded, the timestamp of the preset upgrading time is set for the configuration file to be upgraded, and the preset upgrading time of the configuration file to be upgraded is updated to the actual upgrading time, so that the upgrading time of the configuration file to be upgraded can be changed in real time according to the actual development requirement, the flexibility of software version upgrading is improved, the actual upgrading time of the configuration file to be upgraded does not need to be changed back, the subsequent actual upgrading time is quickly updated through a table structure of the database, the updating processing time of the target configuration file is reduced, and the flexibility of software version upgrading is further improved.

In an embodiment, the step S202 of obtaining the input target version identifier and the target upgrade time corresponding to the target version identifier specifically includes the following steps: receiving an upgrading task of software to be upgraded; and extracting the target version identification and the target upgrading time corresponding to the target version identification from the upgrading task.

Specifically, a developer or a manager needs to upgrade a software version of software to be upgraded, an upgrade request is sent from a terminal, the terminal responds to the request to generate an upgrade task of the software to be upgraded and sends the upgrade task to a server, and then the server receives the upgrade task and performs data extraction processing on the upgrade task to obtain a target version identifier in the upgrade task and target upgrade time corresponding to the target version identifier. Therefore, after the server obtains the target version identification and the target upgrading time corresponding to the target version identification, the server executes the subsequent software version upgrading step by taking the target version identification and the target upgrading time corresponding to the target version identification as updating bases. For example, the server acquires configuration information in a format of 'version number _ preset timestamp _ actual timestamp, TXT', extracts a version number and an actual timestamp from the configuration information, stores the extracted version number and the extracted actual timestamp into a database for version upgrade of software to be upgraded, and updates the configuration information along with the change of an upgrade task.

In this embodiment, the server acquires the upgrade task sent for the software to be upgraded, extracts the target version identifier and the target upgrade time corresponding to the target version identifier from the upgrade task, and by adopting the method, the actual upgrade time of the configuration file to be upgraded does not need to be predetermined, the configuration file to be upgraded is matched according to the target version identifier, and the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time, so that the upgrade time of the configuration file to be upgraded can be changed in real time according to the actual development requirement, and the flexibility of software version upgrade is improved.

In one embodiment, when the version identifier of the configuration file to be upgraded is matched with the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and before obtaining the actual upgrade time of the configuration file to be upgraded, the method further includes: inquiring to obtain a version identification matched with the target version identification from a database; updating the actual upgrading time corresponding to the version identification matched with the target version identification in the database into target upgrading time; in step S203, when the version identifier of the configuration file to be upgraded is matched with the target version identifier, the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time, so as to obtain the actual upgrade time of the updated configuration file to be upgraded, which specifically includes the following contents: and when the version identification of the configuration file to be upgraded is matched with the target version identification, updating the preset upgrading time of the configuration file to be upgraded into the target upgrading time stored in the database.

Specifically, the server generates a version identification query instruction, queries in a database to obtain a version identification matched with the target version identification, then generates a data modification instruction, and modifies actual upgrading time corresponding to the version identification matched with the target version identification in the database into target upgrading time; the method comprises the steps of obtaining version identification of configuration files stored in a preset directory through a judgment tool, wherein the version identification comprises version identification of the configuration files to be upgraded and version identification of historical configuration files, generating corresponding identification matching instructions according to target version identification, matching all the configuration files stored in the preset directory through the identification matching instructions, and updating preset upgrading time of the configuration files to be upgraded in the preset directory to target upgrading time stored in a database when the version identification of the configuration files to be upgraded is matched with the target version identification.

For example, the original file format of the configuration file to be upgraded is: the BIN updates the preset upgrading time of the configuration file to be upgraded into the target upgrading time stored in the database to obtain the file format of the updated configuration file to be upgraded: file name _ source interface _ target interface _ version number _ target upgrade time.

In this embodiment, the version identifier in the database that matches the target version identifier is obtained through query, the actual upgrade time corresponding to the version identifier in the database is updated to the target upgrade time, and when the version identifier of the configuration file to be upgraded in the preset directory matches the target version identifier in the database, the preset upgrade time of the configuration file to be upgraded in the preset directory is updated to the target upgrade time stored in the database. By adopting the method, the configuration file to be upgraded does not need to be retroverted and modified, the timestamp of the actual upgrading time of the configuration file to be upgraded is updated through the connected database, the updating processing time of the actual upgrading time is reduced, and the flexibility of software version upgrading is improved.

In one embodiment, after obtaining the actual upgrade time of the configuration file to be upgraded, the method further includes: inquiring to obtain a historical configuration file matched with the updated configuration file to be upgraded from the plurality of historical configuration files; and adjusting the effective time of the historical configuration file matched with the updated configuration file to be upgraded to the difference between the actual upgrading time of the updated configuration file to be upgraded and the preset threshold value.

The historical configuration file matched with the updated configuration file to be upgraded refers to a configuration file of which the file name, the source interface and the target interface are matched with the updated configuration file to be upgraded, for example, a configuration file of a current version of software to be upgraded.

Specifically, after the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time stored in the database, the server queries and obtains a historical configuration file of which the file name, the source interface and the target interface are all matched with the updated configuration file to be upgraded from a plurality of historical configuration files, then adjusts the effective time of the historical configuration file matched with the updated configuration file to be upgraded to the difference between the actual upgrade time of the updated configuration file to be upgraded and a preset threshold value, and obtains the historical configuration file of the adjusted configuration file to be upgraded, wherein the historical configuration file is used as a historical configuration file of subsequent services of the software to be upgraded, and is convenient for service personnel to check or use historical data of the software to be upgraded. The preset threshold may be set to 1, 2, 3, etc., and may be adjusted according to actual situations, which is not specifically limited herein.

For example, the effective time of the history configuration file of the adjusted configuration file to be upgraded is reduced by one day from the actual upgrade time of the configuration file to be upgraded, when the history configuration file of the configuration file to be upgraded is invalid, the configuration file to be upgraded is upgraded, and meanwhile, the history configuration file of the configuration file to be upgraded can also be stored as the history version data of the software to be upgraded.

In this embodiment, a historical configuration file matched with the updated configuration file to be upgraded is obtained by querying from a plurality of historical configuration files, and the effective time of the historical configuration file matched with the updated configuration file to be upgraded is adjusted. By adopting the method, the configuration file of the current version of the software to be upgraded does not need to be manually replaced, the method can automatically stop when the effective date of the configuration file expires, and can carry out upgrading processing when the actual upgrading time of the configuration file to be upgraded is reached, so that the labor and time cost required by upgrading the software to be upgraded is reduced, and the flexibility of upgrading the software version is improved.

In an embodiment, in step S204, the configuration file with the latest actual upgrade time is screened from the updated configuration file to be upgraded and the plurality of historical configuration files, and the screened configuration file is used as the target configuration file of the software to be upgraded, and specifically includes the following contents: inquiring actual upgrade time stored in a database and obtaining latest actual upgrade time and a version identification corresponding to the latest actual upgrade time; and inquiring the configuration file matched with the version identification corresponding to the latest actual upgrading time from the updated configuration file to be upgraded and the plurality of historical configuration files to be used as the target configuration file of the software to be upgraded.

Specifically, the server generates a time judgment instruction, transmits the time judgment instruction to the database, the database judges the latest actual upgrade time in the relevant data table of the configuration file of the software to be upgraded, and then the database obtains the latest actual upgrade time and the version identification corresponding to the latest actual upgrade time, then the database sends the version identification corresponding to the latest actual upgrade time to the server, the server receives the version identification, and acquiring version identifications of all configuration files in a preset directory through a judgment tool, matching the acquired version identifications of all the configuration files with the version identification corresponding to the latest actual upgrading time, and taking the updated configuration file to be upgraded as a target configuration file of the software to be upgraded if the version identification of the updated configuration file to be upgraded is matched with the version identification corresponding to the latest actual upgrading time.

In addition, when a developer or a manager needs to perform version rollback of software to be upgraded or re-online (i.e. reconfiguration) of a historical version, the developer or the manager may set a target version identifier as a version identifier of a historical configuration file of a corresponding version, set a target upgrade time as an actual upgrade time of the historical configuration file that needs to be re-online, send the target version identifier and the target upgrade time to a server through a terminal, receive the target version identifier and the target upgrade time by the server, modify the corresponding actual upgrade time in a database, judge to obtain a historical configuration file matched with the target version identifier in a preset directory, update the actual upgrade time of the historical configuration file to obtain an updated historical configuration file, when the updated historical configuration file is matched with the version identifier corresponding to the latest actual upgrade time, and taking the updated historical configuration file as a target configuration file of the software to be upgraded.

In this embodiment, the configuration file matched with the version identifier corresponding to the latest actual upgrade time is used as the target configuration file of the software to be upgraded, and by adopting the method, the actual upgrade time of the configuration file to be upgraded is not required to be determined in advance, and the preset upgrade time of the configuration file to be upgraded is updated to the actual upgrade time, so that the upgrade time of the configuration file to be upgraded can be changed in real time according to the actual development requirement, thereby improving the flexibility of upgrading the software version, and meanwhile, the reconfiguration of the historical configuration file can be performed according to the upgrade task, thereby realizing the flexible switching of the upgrade version of the software to be upgraded, and further improving the flexibility of upgrading the software version.

In one embodiment, after screening out a configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and a plurality of historical configuration files, as a target configuration file of the software to be upgraded, the method further includes: when the target configuration file is detected to be an actual upgrade file of the software to be upgraded, generating operation data corresponding to the target configuration file; and upgrading the software to be upgraded according to the running data corresponding to the target configuration file.

And the actual upgrade file is the determined upgrade configuration file of the software to be upgraded. The operation data refers to pre-installation data of software to be upgraded.

Specifically, the server sends a target configuration file from an upstream application to a SOURCE directory (SOURCE directory), detects the actual upgrade time of all files in the SOURCE directory again, confirms that the target configuration file is the actual upgrade file of the software to be upgraded when detecting that the actual upgrade time of the target configuration file is the latest upgrade time of the software to be upgraded, moves the target configuration file to the target upgrade directory, scans files under the target upgrade directory to generate real-time running data, then performs operations such as decoding, distribution, splitting, file transcoding and the like on the real-time running data according to a version configuration instruction, finally generates an upgrade file required by the downstream application, and performs related operations of version upgrading when judging that the actual upgrade time of the target configuration file is reached; and when the target configuration file is detected not to be the actual upgrade file of the software to be upgraded, moving the target configuration file to the error directory.

In the embodiment, the upgrade time of the file in the source directory is detected again, so that the configuration file of the software to be upgraded, which is generated after the target configuration file, is avoided being ignored, errors in upgrading the software version can be effectively reduced, and the accuracy of upgrading the software version is improved.

In one embodiment, as shown in fig. 3, another software version upgrading method is provided, which is described by taking the application of the method to the server in fig. 1 as an example, and includes the following steps:

step S301, acquiring a configuration file of software to be upgraded, and modifying the configuration file for multiple times to obtain multiple modified configuration files of the configuration file; screening a configuration file to be upgraded from a plurality of modified configuration files; the configuration file to be upgraded is the modified configuration file obtained by the last modification.

Step S302, reading the version identification and the preset upgrading time of the configuration file to be upgraded, and storing the version identification and the preset upgrading time into a database.

Step S303, receiving an upgrading task of software to be upgraded; and extracting a target version identification and target upgrading time corresponding to the target version identification from the upgrading task.

Step S304, inquiring to obtain a version identification matched with the target version identification from a database; and updating the actual upgrading time corresponding to the version identification matched with the target version identification in the database into the target upgrading time.

Step S305, when the version identification of the configuration file to be upgraded is matched with the target version identification, updating the preset upgrading time of the configuration file to be upgraded to the target upgrading time stored in the database.

Step S306, inquiring historical configuration files matched with the upgrade configuration files to be updated from the plurality of historical configuration files; and adjusting the effective time of the historical configuration file matched with the updated configuration file to be upgraded to the difference between the actual upgrading time of the updated configuration file to be upgraded and the preset threshold value.

Step S307, the latest actual upgrade time and the version identification corresponding to the latest actual upgrade time are obtained by inquiring from the actual upgrade time stored in the database.

Step S308, inquiring the configuration file matched with the version identification corresponding to the latest actual upgrading time from the updated configuration file to be upgraded and a plurality of historical configuration files, and using the configuration file as the target configuration file of the software to be upgraded.

Step S309, when detecting that the target configuration file is the actual upgrade file of the software to be upgraded, generating operation data corresponding to the target configuration file; and upgrading the software to be upgraded according to the running data corresponding to the target configuration file.

According to the software version upgrading method, the actual upgrading time of the configuration file to be upgraded is not required to be determined in advance, the preset upgrading time of the configuration file to be upgraded is updated to the actual upgrading time, the upgrading time of the configuration file to be upgraded can be changed in real time according to actual development requirements, and therefore the flexibility of software version upgrading is improved.

In order to clarify the software version upgrading method provided by the embodiment of the present disclosure more clearly, the software version upgrading method is specifically described below with a specific embodiment. In an embodiment, as shown in fig. 4, the present disclosure further provides a software version upgrading method, which specifically includes the following steps:

step S401, the data dependence module: storing basic information such as file information, source interface and target interface information, field information, upstream download information, version production time and the like which need to be transmitted, and exporting the stored basic information by using a special tool to generate a configuration file.

Step S402, the data checking module: and according to the time sequence of adding, deleting or modifying the revision file corresponding to the upgrading task of the software to be upgraded, correspondingly processing the configuration file, reserving the configuration file modified for the last time as the configuration file to be upgraded, and in the modification process, acquiring the preset timestamp of the configuration file to be upgraded, the target version identification and the target upgrading time of the software to be upgraded and storing the preset timestamp and the target version identification and the target upgrading time of the software to be upgraded in a database.

Step S403, the version configuration module: and calling a timestamp configuration instruction, switching the preset upgrading time of the configuration file to be upgraded to target upgrading time to obtain a target configuration file, and adjusting the effective time of a file in the historical configuration file, which is the same as the file name, the source interface and the target interface of the configuration file to be upgraded, to be less than 1 day of the actual upgrading time of the configuration file to be upgraded.

Step S404, the file scanning module: and transmitting the upstream application to the file under the source directory, matching according to the actual upgrading time in the configuration information of the file to obtain the configuration file with the latest actual upgrading time, moving the configuration file with the latest actual upgrading time to the processing directory, and moving the configuration file which is not in line with the latest actual upgrading time to the error directory.

Step S405, the file scheduling module: and generating real-time running data which is moved to the file under the processing directory through the version configuration instruction.

Step S406, the file processing module: and performing file decoding processing related operation on the generated real-time running data through the version configuration instruction to generate an upgrade file required by the final downstream application.

In the embodiment, the target configuration file which is released does not need to be returned, re-modified and re-released according to the actual requirement of the upgrading task, the updating of the actual upgrading time can be quickly realized through the table structure of the database, the updating processing time of the target configuration file is reduced, so that the upgrading time of the configuration file to be upgraded can be changed in real time according to the actual development requirement, the flexibility of software version upgrading is improved, the historical version data which is required by a business system can be automatically upgraded or extracted for use, additional configuration operation is not needed, and the flexibility of software version upgrading is further improved.

In an embodiment, as shown in fig. 5, the above steps S402 and S403 further provide another implementation, which specifically includes the following steps:

step 501, firstly, obtaining an original configuration file of software to be upgraded by an export tool, where the format of the original configuration file is as follows: the configuration content of the BIN comprises basic information such as file source interface target interface basic information, file addition (deletion) identification, field information, field filtering information, upstream downloading information, file transmission approval id and the like, and simultaneously obtains the version number _ preset timestamp _ actual timestamp.

Step 502, placing the closing board configuration file and the daily patch configuration file of the software to be upgraded in a temporary directory for multiple modifications, reading file information by an importing tool, keeping the configuration file corresponding to the last file transmission approval id of the same file in the current version under the condition that the closing board configuration file and the daily patch configuration file are modified for multiple times in the current version to obtain the configuration file to be upgraded, and importing the configuration file to a base table cfg _ validTime according to a determined time correspondence while modifying the file, wherein the field structure of the table is as follows:

Step 503, presetting T, T-1 and T-2 with the production time of the current version, expanding to T +1 and T +2 as required, judging the version identification of the configuration file to be upgraded by the import tool, switching the timestamp of the preset production time of the configuration file to be upgraded to the timestamp of the production time corresponding to the version, and updating the format in the configuration file to be upgraded: the original format "filename _ source interface _ target interface _ version number _ preset timestamp" BIN "is updated to" filename _ source interface _ target interface _ version number _ production time.

Step 504, after the timestamp of the preset production time of the configuration file to be upgraded corresponding to the current version is switched to the new production time, the timestamp of the effective time of the configuration file in the historical configuration file, which is the same as the file name of the configuration file to be upgraded, the source interface and the target interface, is adjusted to be the current production time minus 1, the adjusted historical configuration file is used for downloading the data of the historical version of the subsequent service, and the data of the historical version is prevented from being obtained by manual adjustment when the subsequent service is needed.

It should be understood that although the various steps in the flow charts of fig. 2-5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-5 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.

Based on the same inventive concept, the embodiment of the application also provides a software version upgrading device for realizing the software version upgrading method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the method, so specific limitations in one or more embodiments of the software version upgrading device provided below can be referred to the limitations of the software version upgrading method in the foregoing, and details are not described herein again.

In one embodiment, as shown in fig. 6, there is provided a software version upgrade apparatus 600, including: a file obtaining module 601, a time obtaining module 602, an update time module 603, and a file screening module 604, wherein:

the file obtaining module 601 is configured to obtain a configuration file to be upgraded of software to be upgraded, and store a version identifier of the configuration file to be upgraded and preset upgrade time in a database; the database also stores the actual upgrading time of a plurality of historical configuration files of the software to be upgraded;

an obtaining time module 602, configured to obtain an input target version identifier and target upgrade time corresponding to the target version identifier;

an update time module 603, configured to update a preset update time of the configuration file to be updated to the target update time when the version identifier of the configuration file to be updated matches the target version identifier, so as to obtain an actual update time of the configuration file to be updated;

a screening file module 604, configured to screen out, from the configuration file to be upgraded and the plurality of historical configuration files, a configuration file with the latest actual upgrade time as a target configuration file of the software to be upgraded.

In an embodiment, the file obtaining module 601 is further configured to obtain a configuration file of the software to be upgraded, and modify the configuration file multiple times to obtain multiple modified configuration files of the configuration file; screening a configuration file to be upgraded from a plurality of modified configuration files; the configuration file to be upgraded is a modified configuration file obtained by the last modification; and reading the version identification and the preset upgrading time of the configuration file to be upgraded, and storing the version identification and the preset upgrading time into a database.

In one embodiment, the obtaining time module 602 is further configured to receive an upgrade task of software to be upgraded; and extracting the target version identification and the target upgrading time corresponding to the target version identification from the upgrading task.

In one embodiment, the software version upgrading apparatus 600 further includes a database updating module, configured to query a database to obtain a version identifier matching the target version identifier; and updating the actual upgrading time corresponding to the version identification matched with the target version identification in the database into the target upgrading time.

The update time module 603 is further configured to update the preset upgrade time of the configuration file to be upgraded to the target upgrade time stored in the database when the version identifier of the configuration file to be upgraded matches the target version identifier.

In an embodiment, the software version upgrading apparatus 600 further includes a time adjustment module, configured to query, from the plurality of historical configuration files, a historical configuration file that matches an upgrade configuration file to be updated; and adjusting the effective time of the historical configuration file matched with the updated configuration file to be upgraded to be the difference between the actual upgrading time of the updated configuration file to be upgraded and a preset threshold value.

In an embodiment, the screening file module 604 is further configured to query actual upgrade time stored in the database to obtain latest actual upgrade time and a version identifier corresponding to the latest actual upgrade time; and inquiring the configuration file matched with the version identification corresponding to the latest actual upgrading time from the updated configuration file to be upgraded and the plurality of historical configuration files to be used as the target configuration file of the software to be upgraded.

In one embodiment, the software version upgrading apparatus 600 further includes a software upgrading module, configured to generate operating data corresponding to a target configuration file when it is detected that the target configuration file is an actual upgrade file of software to be upgraded; and upgrading the software to be upgraded according to the running data corresponding to the target configuration file.

The modules in the software version upgrading device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer equipment is used for storing data such as version identification, preset upgrading time, actual upgrading time and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a software version upgrade method.

Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In an embodiment, a computer program product is provided, comprising a computer program which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A method for upgrading a software version, the method comprising:

2. The method according to claim 1, wherein the obtaining a configuration file to be upgraded of software to be upgraded and storing a version identifier of the configuration file to be upgraded and a preset upgrade time in a database comprises:

3. The method of claim 1, wherein the obtaining the input target version identifier and the target upgrade time corresponding to the target version identifier comprises:

receiving an upgrading task of the software to be upgraded;

4. The method according to claim 1, wherein when the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and before obtaining the actual upgrade time of the configuration file to be upgraded, the method further comprises:

5. The method of claim 4, after obtaining the actual upgrade time of the updated configuration file to be upgraded, further comprising:

inquiring to obtain a historical configuration file matched with the upgrade configuration file to be updated from the plurality of historical configuration files;

6. The method according to claim 1, wherein the screening out a configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the plurality of historical configuration files as a target configuration file of the software to be upgraded comprises:

7. The method according to claim 6, wherein after screening out a configuration file with the latest actual upgrade time from the configuration file to be upgraded and the plurality of historical configuration files as a target configuration file of the software to be upgraded, the method further comprises:

8. An apparatus for upgrading a software version, the apparatus comprising:

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 7 when executed by a processor.