CN113128197A

CN113128197A - Method and device for managing application production versions

Info

Publication number: CN113128197A
Application number: CN202110515921.1A
Authority: CN
Inventors: 许彦钊; 肖邦; 宋梦婷; 苏澳文; 周会军
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2021-05-12
Filing date: 2021-05-12
Publication date: 2021-07-16

Abstract

The invention discloses a method and a device for managing application production versions, and relates to the technical field of cloud computing. One embodiment of the method comprises: in response to receiving the production approval process submission information of the application version file, the development management platform sends the application version file to the transfer machine; sending a delivery message of the application version file to the version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path; the service objects of the public cloud and the private cloud respectively obtain the application version files to the corresponding version machines for use, network risks caused by the fact that production environments are not isolated from testing environments are effectively avoided, meanwhile, the requirements of clients of the public cloud and the private cloud are met, manual complex operations are reduced, labor cost is saved, safety and audit requirements are met, the production process processing efficiency is improved, and financial science and technology development transformation is supported.

Description

Method and device for managing application production versions

Technical Field

The invention relates to the technical field of cloud computing, in particular to a method and a device for managing application production versions.

Background

With the recent development of financial technology. Cloud computing resources of a large-scale financial enterprise data center are divided into public clouds of service set group companies, government affair clients and external enterprise clients on the basis of an original private cloud only serving internal businesses. And multiple cloud modes coexist, and new requirements are provided for application version change. The method is characterized in that more application version production scenes are provided, the process is more complex, and how to establish a uniform and efficient production version management mode becomes a difficult point.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:

in the existing technology for storing application version files by using a file server, the file server is deployed in a production environment, and when a test environment is developed and a version is pushed to the file server, the production environment is not isolated from the test environment, so that network risks exist; the file server only supports a private cloud and only serves an internal business system, and the production requirements of clients outside a public cloud cannot be met; the file server version package file flow is split with the production approval process, so that the manual operation is complicated, the risk of operation errors exists, automatic checking is not supported, and the requirements on safety and auditing can not be met.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method and an apparatus for managing application production versions, which design, develop, test and production environments, and design version management processes of different production objects in different scenarios, and combine the version management and the production processes, thereby providing a uniform and efficient version management manner for application production in a multi-cloud scenario of the financial industry, effectively avoiding network risks, satisfying customer requirements of public clouds and private clouds, reducing cumbersome manual operations, saving human costs, satisfying safety audit requirements, improving processing efficiency of production processes, and supporting financial science and technology development transformation.

To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method of application commissioning version management.

A method for managing an application production version is suitable for a scene of coexistence of a public cloud and a private cloud, and comprises the following steps: in response to receiving production approval process submission information of the application version file, the development management platform sends the application version file to a transfer machine; sending a delivery message of the application version file to a version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path; and respectively enabling the service objects of the public cloud and the private cloud to the corresponding version machines to acquire the application version files for use.

Optionally, the production approval process submission information includes an application version file and application version information, where the application version information includes the name, size, and storage path of the application version.

Optionally, before sending the application version file to the transfer machine, the method further includes:

setting an isolation area between a development test environment and a production environment, and setting a transfer machine in the isolation area;

wherein the isolation region is to prevent direct access between the development test environment and the production environment, and only allow one-way active request access from the production environment or the development test environment to the isolation region.

Optionally, the versioning machines include a private cloud versioning machine and a public cloud versioning machine, and are deployed in a production environment.

Optionally, sending, by the transfer machine, a delivery message of the application version file to a version machine includes:

identifying whether the application version file belongs to a public cloud version or a private cloud version through the transfer machine;

if the application version file belongs to the public cloud version, sending a delivery message of the application version file to a public cloud version machine;

and if the application version belongs to the private cloud version, sending a delivery message of the application version file to a private cloud version machine.

Optionally, after the version machine acquires the application version file from the transfer machine, before the version machine stores the application version file in the corresponding version machine according to the storage path, the method further includes:

and checking the acquired application version file through the version machine.

Optionally, verifying the acquired application version file by the version machine includes:

automatically checking the size, the saving path and the MD5 code of the application version file through the version machine according to the application version information;

and if the verification is passed, storing the application version file in a corresponding version machine according to a preset storage path.

Optionally, after the obtained application version file is verified by the version machine, the method further includes:

sending the checking result to the development management platform, and if the checking result passes, continuing to perform the production approval process of the application version;

and if the verification result does not pass, outputting prompt information and suspending the production approval process of the application version.

Optionally, after receiving the production approval process submission information of the application version file, the method further includes:

the development management platform sends the application version information to an operation and maintenance management platform and stores the application version information into an operation and maintenance management platform database; the version machine carries out unified management through the operation and maintenance management platform.

Optionally, the method further comprises:

and designing a saving path of the application version file in the version machine.

Optionally, the saving path includes a primary directory and a secondary directory;

the first-level catalog comprises a public cloud and a private cloud, the second-level catalog corresponding to the first-level catalog of the public cloud comprises a direct organization, a provincial branch organization, a group subsidiary company and an external client, and the second-level catalog corresponding to the first-level catalog of the private cloud comprises a direct organization, a provincial branch organization and a group subsidiary company.

Optionally, the method further comprises: and setting the access authority of the storage paths, wherein the storage directories corresponding to different storage paths only allow users meeting the requirements to access.

Optionally, the method further comprises: setting the access authority of the edition machine, wherein the access authority of the edition machine is controlled by an IP access list; the IP access list is added manually by a system administrator or through an administration page.

According to another aspect of the embodiments of the present invention, an apparatus for application commissioning version management is provided.

An apparatus for application commissioning version management, the apparatus being adapted for a scenario where a public cloud and a private cloud coexist, the apparatus comprising:

the file pushing module is used for responding to the received production approval process submission information of the application version file, and the development management platform sends the application version file to the transfer machine;

the file storage module is used for sending a delivery message of the application version file to a version machine through the transfer machine so that the version machine can acquire the application version file from the transfer machine and store the application version file in the corresponding version machine according to a storage path;

and the file acquisition module is used for respectively acquiring the application version files from the service objects of the public cloud and the private cloud to the corresponding version machines for use.

Optionally, the apparatus further comprises an isolation region module for: setting an isolation area between a development test environment and a production environment, and setting a transfer machine in the isolation area; wherein the isolation region is to prevent direct access between the development test environment and the production environment, and only allow one-way active request access from the production environment or the development test environment to the isolation region.

Optionally, the file saving module is further configured to: identifying whether the application version file belongs to a public cloud version or a private cloud version through the transfer machine; if the application version file belongs to the public cloud version, sending a delivery message of the application version file to a public cloud version machine; and if the application version belongs to the private cloud version, sending a delivery message of the application version file to a private cloud version machine.

Optionally, the apparatus further includes a version check module, configured to: and checking the acquired application version file through the version machine.

Optionally, the version check module is further configured to: automatically checking the size, the saving path and the MD5 code of the application version file through the version machine according to the application version information; and if the verification is passed, storing the application version file in a corresponding version machine according to a preset storage path.

Optionally, the apparatus further includes a result sending module, configured to: sending the checking result to the development management platform, and if the checking result passes, continuing to perform the production approval process of the application version; and if the verification result does not pass, outputting prompt information and suspending the production approval process of the application version.

Optionally, the apparatus further includes a version information storage module, configured to: the development management platform sends the application version information to an operation and maintenance management platform and stores the application version information into an operation and maintenance management platform database; the version machine carries out unified management through the operation and maintenance management platform.

In an embodiment of the invention, the apparatus further comprises a path design module configured to: and designing a saving path of the application version file in a version machine.

Optionally, the saving path includes a primary directory and a secondary directory; the first-level catalog comprises a public cloud and a private cloud, the second-level catalog corresponding to the first-level catalog of the public cloud comprises a direct organization, a provincial branch organization, a group subsidiary company and an external client, and the second-level catalog corresponding to the first-level catalog of the private cloud comprises a direct organization, a provincial branch organization and a group subsidiary company.

In an embodiment of the present invention, the apparatus further includes a path authority module, configured to: and setting the access authority of the storage paths, wherein the storage directories corresponding to different storage paths only allow users meeting the requirements to access.

Optionally, the apparatus further comprises a versioning authority module configured to: setting the access authority of the edition machine, wherein the access authority of the edition machine is controlled by an IP access list; the IP access list is added manually by a system administrator or through an administration page.

According to another aspect of the embodiment of the invention, an electronic device for application production version management is provided.

An electronic device for application commissioning version management, comprising: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method for managing the application production version provided by the embodiment of the invention.

According to yet another aspect of embodiments of the present invention, a computer-readable medium is provided.

A computer readable medium, on which a computer program is stored, which when executed by a processor implements a method for application commissioning version management provided by an embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: the development management platform sends the application version file to a transfer machine by adopting production approval process submission information responding to the received application version file; sending a delivery message of the application version file to a version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path; service objects of the public cloud and the private cloud respectively go to corresponding version machines to obtain the application version files for use, version management processes of different production objects in different scenes are designed by designing and developing an isolation area between a test environment and a production environment, and a uniform and efficient version management mode is provided for application production under the multi-cloud scene of the financial industry by combining the version management and the production processes, so that network risks caused by the fact that the production environment is not isolated from the test environment are effectively avoided, the requirements of clients of the public cloud and the private cloud are met, manual complex operation is reduced, labor cost is saved, safety and audit requirements are met, the processing efficiency of the production process is improved, and financial technology development transformation is supported.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a schematic diagram of the main steps of a method for application commissioning version management according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an isolation region according to one embodiment of the invention;

FIG. 3 is a version path diagram according to one embodiment of the invention;

FIG. 4 is a schematic diagram of version file circulation according to one embodiment of the invention;

FIG. 5 is a schematic diagram of a server deployment, according to one embodiment of the invention;

FIG. 6 is an overall flow diagram of a method of application commissioning version management according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of the main modules of an apparatus for application commissioning version management according to an embodiment of the present invention;

FIG. 8 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 9 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In the embodiments of the present invention, the terms are as follows:

IT operation and maintenance: the method is characterized in that a large commercial bank adopts related methods, means, technologies, systems, flows, documents and the like to comprehensively manage the whole bank organization in order to ensure that all branches, all systems, all application systems and the like of the bank can normally work all day long;

a cloudy scene: the cloud computing mode refers to a cloud computing use mode with coexistence of public cloud and private cloud of a large IT enterprise, wherein the private cloud is used by an enterprise internal system, and the public cloud is provided for external customers, tenants and subsidiaries;

application production version: the method comprises the steps of deploying a software change package from a development environment to a production environment in various application system iteration processes in enterprise-level IT management;

isolation region: the method is characterized in that a large IT enterprise is designed to be an effective isolation area for the internal interaction between a development test environment and a production environment in order to meet the specific service requirement of the online real-time data interaction between the internal development test environment and the production system;

a transfer machine: the master and the slave are arranged in the isolation area and are communicated with a version file transfer server of a development test network to a production network segment;

version machine: and the version file storage server is deployed in the production area.

Fig. 1 is a schematic diagram of main steps of a method for managing an application commissioning version according to an embodiment of the present invention, and as shown in fig. 1, the method for managing an application commissioning version according to an embodiment of the present invention mainly includes the following steps S101 to S103.

Step S101: in response to receiving the production approval process submission information of the application version file, the development management platform sends the application version file to the transfer machine; the production approval process submission information comprises an application version file and application version information, and the application version information comprises an application version name, size and the like.

According to an embodiment of the present invention, before sending the application version file to the transfer machine, the method further includes: setting an isolation area between a development test environment and a production environment, and setting a transfer machine in the isolation area; the isolation region is used for preventing direct access between the development test environment and the production environment, and only allowing the one-way active access request of the production environment or the development test environment to the isolation region.

FIG. 2 is a schematic diagram of an isolation area according to an embodiment of the present invention, in order to meet specific business requirements of data interaction between an internal development test environment and a production system on the premise that the development test environment is effectively isolated from the production environment, an effective isolation area of the internal interaction between the development test environment and the production environment is designed, as shown in FIG. 2, in the isolation area, only one-way active request access from the production environment to the isolation area and from the development test environment to the isolation area is allowed, one-way active request access from the isolation area to the production environment and from the isolation area to the development test environment is prohibited, direct access from the production environment to the development test environment beyond the isolation area is prohibited, a transfer is deployed in the isolation area, a version is pushed from a development test network to a transfer machine, and a version is obtained from the production network to a version machine, the safe and efficient version production process under the production environment and the development and test environment is realized.

Step S102: sending a delivery message of the application version file to the version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path; the version machine comprises a private cloud version machine and a public cloud version machine, and is deployed in a production environment.

In an embodiment of the present invention, sending, by the transfer machine, an arrival message of the application version file to the version machine includes: identifying whether the application version file belongs to a public cloud version or a private cloud version through a transfer machine; if the application version file belongs to the public cloud version, sending a delivery message of the application version file to a public cloud version machine; and if the application version belongs to the private cloud version, sending a delivery message of the application version file to a private cloud version machine.

According to another embodiment of the invention, the method further comprises: designing a storage path of the application version file in the version machine; the saving path comprises a first-level directory and a second-level directory; the first-level catalogs comprise public clouds and private clouds, the second-level catalogs corresponding to the first-level catalogs of the public clouds comprise directly affiliated organizations, provincial branches, group subsidiaries and external clients, and the second-level catalogs corresponding to the first-level catalogs of the private clouds comprise directly affiliated organizations, provincial branches and group subsidiaries. Fig. 3 is a schematic diagram of a version path according to an embodiment of the present invention, wherein the version path is designed according to a public cloud, a private cloud and respective service objects, and as shown in fig. 3, the first-level directory of the storage path includes a public cloud and a private cloud, and the second-level directory includes a direct organization corresponding to the public cloud, a provincial branch organization, a corporate sub-company, an external client, and a direct organization corresponding to the private cloud, a provincial branch organization, and a corporate sub-company.

In the embodiment of the present invention, after the version engine acquires the application version file from the transfer engine, before the application version file is stored in the corresponding version engine according to the storage path, the method further includes: verifying the obtained application version file through a version machine; the verification of the acquired application version file through the version machine comprises the following steps: automatically checking the size, the saving path and the MD5 code of the application version file through a version machine according to the application version information; and if the verification is passed, storing the application version file in the corresponding version machine according to a preset storage path.

In the embodiment of the present invention, after the obtained application version file is verified by the version machine, the method further includes: sending the checking result to a development management platform; if the verification result passes, continuing to perform the production approval process of the application version; and if the verification result does not pass, outputting prompt information and suspending the production approval process of the application version.

According to another embodiment of the present invention, after receiving the production approval process submission information of the application version file, the method further comprises: the development management platform sends the application version information to the operation and maintenance management platform and stores the application version information into an operation and maintenance management platform database; the version machine carries out unified management through the operation and maintenance management platform.

According to a further embodiment of the invention, the method further comprises: setting the access authority of the storage paths, wherein the storage directories corresponding to different storage paths only allow users meeting the requirements to access; setting the access authority of the edition machine, wherein the access authority of the edition machine is controlled by an IP access list; the IP access list is added by the system administrator either manually or through an administration page. The version access authority is controlled according to a version storage path, different storage directories are accessed by corresponding users, access to a version machine is controlled through an IP white list, a production network segment is defaulted in the access white list, special conditions support adding of the white list, manual physical examination is conducted by a system administrator or adding is conducted through a management page, and different version file streams are designed according to a public cloud and a private cloud.

Step S103: and respectively enabling the service objects of the public cloud and the private cloud to the corresponding version machines to acquire the application version files for use. Fig. 4 is a schematic view illustrating a version file transfer according to an embodiment of the present invention, and as shown in fig. 4, a public cloud version file is stored in a public cloud version local machine, a private cloud version file is stored in a private cloud version local machine, and service objects of the public cloud and the private cloud are respectively located in corresponding version areas to obtain the version files.

Fig. 5 is a schematic diagram of server deployment according to an embodiment of the present invention, which is mainly divided into three modules, namely, a transfer machine, a version machine, and an operation and management platform, and as shown in fig. 5, a transfer machine (for example, 2) is deployed in an isolation region as a master and a slave, and communicates a development test network to a production network segment, and a version machine (for example, 3) is deployed in a production region, and a cluster is deployed in the production region, and a public cloud version file and a private cloud version file are uniformly managed by the version machine, and after receiving version flow submission information, application version information in the version flow submission information is stored in an operation and management platform database, and the version machine is managed by an operation and maintenance management platform.

Fig. 6 is an overall flowchart of a method for managing an application delivery version according to an embodiment of the present invention, where the method for managing an application delivery version automatically connects a version pushing process and a delivery approval error correction, and as shown in fig. 6, the overall flowchart of the method for managing an application delivery version mainly includes: after a development project group finishes a development test approval process and submits a production approval process to a data center production management department, synchronously triggering and pushing versions to a production environment version machine to realize online synchronization of the production versions, automatically checking the size, path and MD5 code of a version file according to production approval process information, and sending checking result information to the production approval process, wherein the requirements of financial level safety and audit are met, and the detailed steps mainly comprise the following steps:

1. in response to receiving production approval process submission information of the application version file, the development management platform sends the application version file to the transfer machine, and the development management platform pushes the application version file to the isolation area transfer machine;

2. sending a delivery message of the application version file to the version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path, sending the version delivery message to the version machine by the transfer machine, acquiring the application version file from the transfer machine after the version machine receives the message and verifying the application version file, and storing the application version file in the corresponding version machine if the verification is passed;

3. the version machine sends version checking result information to the development management platform;

4. and the public cloud and the private cloud respectively obtain the application version file from the corresponding version machine for production change.

Fig. 7 is a schematic diagram of main modules of an apparatus for managing application delivery versions according to an embodiment of the present invention, and as shown in fig. 7, the apparatus 700 for managing application delivery versions according to an embodiment of the present invention mainly includes a file pushing module 701, a file saving module 702, and a file obtaining module 703.

The file pushing module 701 is used for responding to the received production approval process submission information of the application version file, and the development management platform sends the application version file to the transfer machine;

the file saving module 702 is configured to send a delivery message of the application version file to the version machine through the transfer machine, so that the version machine obtains the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a saving path;

the file obtaining module 703 is configured to obtain the application version file from the service object of the public cloud and the service object of the private cloud to the corresponding version machine respectively for use.

In the embodiment of the invention, the production approval process submission information comprises the application version file and the application version information, and the application version information comprises the name, the size, the storage path and the like of the application version.

In an embodiment of the present invention, the apparatus 700 further comprises an isolation region module (not shown in the figures) for: setting an isolation area between a development test environment and a production environment, and setting a transfer machine in the isolation area; the isolation region is used for preventing direct access between the development test environment and the production environment, and only allowing the one-way active access request of the production environment or the development test environment to the isolation region.

In an embodiment of the invention, the version machines comprise a private cloud version machine and a public cloud version machine, and are deployed in a production environment.

According to an embodiment of the present invention, the file saving module 702 is further configured to: identifying whether the application version file belongs to a public cloud version or a private cloud version through a transfer machine; if the application version file belongs to the public cloud version, sending a delivery message of the application version file to a public cloud version machine; and if the application version belongs to the private cloud version, sending a delivery message of the application version file to a private cloud version machine.

According to another embodiment of the present invention, the apparatus 700 further comprises a version check module (not shown in the figures) for: and verifying the acquired application version file through the version machine.

In an embodiment of the present invention, the version check module is further configured to: automatically checking the size, the saving path and the MD5 code of the application version file through a version machine according to the application version information; and if the verification is passed, storing the application version file in the corresponding version machine according to a preset storage path.

In an embodiment of the present invention, the apparatus 700 further includes a result sending module (not shown in the figure) configured to: sending the checking result to a development management platform, and if the checking result passes, continuing to perform the production approval process of the application version; and if the verification result does not pass, outputting prompt information and suspending the production approval process of the application version.

According to another embodiment of the present invention, the apparatus 700 further comprises a version information storage module (not shown in the figure) for: the development management platform sends the application version information to the operation and maintenance management platform and stores the application version information into an operation and maintenance management platform database; the version machine carries out unified management through the operation and maintenance management platform.

In an embodiment of the present invention, the apparatus 700 further comprises a path design module (not shown in the figures) for: and designing a saving path of the application version file in the version machine.

In an embodiment of the invention, the save path comprises a primary directory and a secondary directory; the first-level catalogs comprise public clouds and private clouds, the second-level catalogs corresponding to the first-level catalogs of the public clouds comprise directly affiliated organizations, provincial branches, group subsidiaries and external clients, and the second-level catalogs corresponding to the first-level catalogs of the private clouds comprise directly affiliated organizations, provincial branches and group subsidiaries.

In an embodiment of the present invention, the apparatus 700 further comprises a path authority module (not shown in the figure) for: and setting the access authority of the storage paths, wherein the storage directories corresponding to different storage paths only allow users meeting the requirements to access.

In an embodiment of the present invention, the apparatus 700 further comprises a version authority module (not shown in the figures) for: setting the access authority of the edition machine, wherein the access authority of the edition machine is controlled by an IP access list; the IP access list is added by the system administrator either manually or through an administration page.

Fig. 8 illustrates an exemplary system architecture 800 of a method of application commissioning version management or an apparatus of application commissioning version management to which embodiments of the present invention may be applied.

As shown in fig. 8, the system architecture 800 may include

terminal devices

801, 802, 803, a network 804, and a server 805. The network 804 serves to provide a medium for communication links between the

terminal devices

801, 802, 803 and the server 805. Network 804 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

801, 802, 803 to interact with a server 805 over a network 804 to receive or send messages or the like. Various communication client applications, such as management applications, operation and maintenance applications, development and test applications, etc. (for example only), may be installed on the

terminal devices

801, 802, 803.

The

terminal devices

801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 805 may be a server that provides various services, such as a back-office management server (for example only) that provides support for administrative type websites browsed by users using the

terminal devices

801, 802, 803. The background management server may analyze and perform other processing on the received data such as the version file, and feed back a processing result (for example, store the processing result in a corresponding version machine — only an example) to the terminal device.

It should be noted that the method for managing the application delivery version provided by the embodiment of the present invention is generally executed by the server 805, and accordingly, the apparatus for managing the application delivery version is generally disposed in the server 805.

It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 9, a block diagram of a computer system 900 suitable for use with a terminal device or server implementing an embodiment of the invention is shown. The terminal device or the server shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are executed when the computer program is executed by a Central Processing Unit (CPU) 901.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units or modules described in the embodiments of the present invention may be implemented by software, or may be implemented by hardware. The described units or modules may also be provided in a processor, and may be described as: a processor comprises a file pushing module, a file storing module and a file acquiring module. The names of the units or modules do not limit the units or modules themselves under certain conditions, for example, the file pushing module may also be described as a module that sends the application version file to the transfer machine in response to receiving the production approval process submission information of the application version file.

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: in response to receiving production approval process submission information of the application version file, the development management platform sends the application version file to a transfer machine; sending a delivery message of the application version file to a version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path; respectively acquiring the application version files from the service objects of the public cloud and the private cloud to the corresponding version machines for use

According to the technical scheme of the embodiment of the invention, the development management platform sends the application version file to the transfer machine by adopting the production approval process submission information responding to the received application version file; sending a delivery message of the application version file to a version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path; service objects of the public cloud and the private cloud respectively go to corresponding version machines to obtain the application version files for use, version management processes of different production objects in different scenes are designed by designing and developing an isolation area between a test environment and a production environment, and a uniform and efficient version management mode is provided for application production under the multi-cloud scene of the financial industry by combining the version management and the production processes, so that network risks caused by the fact that the production environment is not isolated from the test environment are effectively avoided, the requirements of clients of the public cloud and the private cloud are met, manual complex operation is reduced, labor cost is saved, safety and audit requirements are met, the processing efficiency of the production process is improved, and financial technology development transformation is supported.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for managing application commissioning versions is applicable to a scenario where a public cloud and a private cloud coexist, and comprises the following steps:

in response to receiving production approval process submission information of the application version file, the development management platform sends the application version file to a transfer machine;

sending a delivery message of the application version file to a version machine through the transfer machine so that the version machine acquires the application version file from the transfer machine and stores the application version file in the corresponding version machine according to a storage path;

and respectively enabling the service objects of the public cloud and the private cloud to the corresponding version machines to acquire the application version files for use.

2. The method of claim 1, wherein the production approval process submission information includes an application version file and application version information, and wherein the application version information includes the application version name, size, and save path.

3. The method of claim 1, wherein sending the application version file to a transfer machine further comprises:

4. The method of claim 3, wherein the versioning machines comprise a private cloud versioning machine and a public cloud versioning machine, and are deployed in a production environment.

5. The method of claim 1 or 4, wherein sending, by the transfer machine, a delivery message for the application version file to a version machine comprises:

6. The method of claim 1, wherein after the version engine obtains the application version file from the transfer engine, before the application version file is stored in the corresponding version engine according to the saving path, the method further comprises:

and checking the acquired application version file through the version machine.

7. The method of claim 6, wherein verifying the retrieved application version file by the version machine comprises:

8. The method of claim 6, after the verifying the obtained application version file by the version machine, further comprising:

9. The method of claim 2, wherein after receiving the production approval process submission information for the application version file, further comprising:

10. The method of claim 1, further comprising:

11. The method of claim 1, wherein the save path comprises a primary directory and a secondary directory;

12. The method of claim 1, further comprising: and setting the access authority of the storage paths, wherein the storage directories corresponding to different storage paths only allow users meeting the requirements to access.

13. The method of claim 1, further comprising: setting the access authority of the edition machine, wherein the access authority of the edition machine is controlled by an IP access list; the IP access list is added manually by a system administrator or through an administration page.

14. An apparatus for application commissioning version management, the apparatus being adapted to a scenario where a public cloud and a private cloud coexist, comprising:

15. An electronic device for application commissioning version management, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-13.

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