A software product management method, device and medium for private cloud architecture

Abstract

The present application discloses a software product management method, device and medium for a private cloud architecture. The method includes: constructing a software product and uploading the software product to a software product library; the software product library determines the attribute information of the software product and displays the software product on a front-end interactive interface; when a project to be delivered needs to be delivered, the information of the work order to be executed is determined through the front-end interactive interface, and a work order to be executed is generated based on the information of the work order to be executed; based on the work order to be executed, the software product to be applied in the software product library is extracted, a mirror package to be deployed is generated, and the mirror package to be deployed is pushed to the target server to be deployed; based on a preset automatic deployment script, the target server to be deployed automatically deploys the mirror package to be deployed. The present application solves the problem that the existing software product library for private cloud architecture does not have a management solution for the project delivery version to manage software products through the above method.

Description

Technical Field

[0001] The present application relates to the field of microservice architecture technology, and in particular to a software product management method, device, and medium for a private cloud architecture. Background Art

[0002] Software artifacts are files or compressed packages generated by compiling and packaging source code. A software artifact library is a repository for storing and managing software artifacts, providing release capabilities and seamless integration with existing standardized build and release tools. Software artifact libraries are a crucial component of the DevOps toolchain. By managing software artifacts through a software artifact library, the quality and efficiency of software development and delivery are improved. With the development of microservices architecture and DevOps, the number of software artifacts and the speed of their iteration have increased exponentially, leading to increased deployment and update frequency.

[0003] As awareness of network and data security grows, project delivery methods are shifting from traditional public cloud architectures to more secure private cloud architectures. However, existing software artifact repositories lack a solution for managing project delivery versions for private cloud architectures, significantly impacting work efficiency. Summary of the Invention

[0004] The embodiments of the present application provide a software product management method, device and medium for a private cloud architecture to solve the following technical problem: for a private cloud architecture, the existing software product library does not have a management solution for project delivery versions to manage software products.

[0005] In a first aspect, an embodiment of the present application provides a software product management method for a private cloud architecture, characterized in that the method includes: constructing a software product and uploading the software product to a software product library; the software product library determines the attribute information of the software product, and displays the software product on the front-end interactive interface of the software product library based on the attribute information; wherein the attribute information at least includes a software product identifier; when the project delivery personnel need to deliver the project to be delivered, the to-be-delivered work order information is determined through the front-end interactive interface, and a to-be-delivered work order is generated based on the to-be-delivered work order information; wherein the to-be-delivered work order information includes: an identifier of a project to be deployed, an identifier of a destination server to be deployed, and an identifier of a software product to be applied; based on the to-be-deployed work order, the to-be-applied software product in the software product library is extracted, a to-be-deployed image package is generated, and the to-be-deployed image package is pushed to the destination server to be deployed; based on a preset automatic deployment script, the destination server to be deployed automatically deploys the to-be-deployed image package.

[0006] In one implementation of the present application, building a software product specifically includes: reading a source code library based on a preset software product building tool to determine the source code corresponding to the software product; compiling and packaging the source code to generate a software product; wherein the software product is a program file that can be run on a destination server.

[0007] In one implementation of the present application, after building the software product, the method further includes: publishing the software product to a preset test destination server through a preset automatic publishing tool; based on a preset automated testing tool, the test destination server performs automated testing on the software product to determine whether the software product is qualified; if the software product is unqualified, triggering the software product construction tool to re-read the source code corresponding to the software product to rebuild the software product.

[0008] In one implementation of the present application, the method further includes: a preset version management library collects release information of the software product; wherein the release information includes at least: software product identification, software product type, software product storage address, software product library version number, software product deployment project identification, and software product deployment destination server; based on preset release information analysis rules, the release information is analyzed to obtain a deployment architecture diagram of the software product; and the deployment architecture diagram is displayed through the front-end interactive interface of the version management library.

[0009] In one implementation of the present application, the method also includes: when it is necessary to perform replicated deployment of the project to be delivered, determining the identifier of the project to be replicated, the identifier of the destination server to be replicated, and the identifier of the software product to be applied corresponding to the project to be delivered in the front-end interactive interface of the version management library; based on the identifier of the software product to be applied, determining the storage address of the software product to be applied, and based on the storage address, extracting the software product to be applied in the software product library, generating a mirror package to be replicated, and pushing the mirror package to be replicated to the destination server to be replicated, so as to realize replicated deployment of the project to be delivered.

[0010] In one implementation of the present application, after the target server to be deployed automatically deploys the image package to be deployed, the method also includes: when it is necessary to upgrade the version of the software product to be applied in the target server to be deployed, determining the work order information to be upgraded through the front-end interactive interface, and generating the work order to be upgraded based on the work order information to be upgraded; wherein the work order information to be upgraded includes: the identifier of the project to be deployed, the identifier of the target server to be deployed, and the identifier of the software product to be upgraded; based on the work order to be upgraded, the software product library automatically upgrades the software product to be applied to the software product to be upgraded.

[0011] In one implementation of the present application, the attribute information also includes at least the source code address and branch, build record identifier, software product download address, software product configuration file, software product database upgrade script, and software product version number.

[0012] In one implementation of the present application, the deployment architecture diagram includes at least: a deployment architecture diagram of software product versions of a delivery project, a deployment architecture diagram of each version of a software product in a delivery project, and a deployment architecture diagram of software products in a project.

[0013] In a second aspect, an embodiment of the present application also provides a software product management device for a private cloud architecture, characterized in that the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: build a software product and upload the software product to a software product library; the software product library determines the attribute information of the software product and displays the software product on the front-end interactive interface of the software product library based on the attribute information; wherein the attribute information includes at least a software product identifier; when the project delivery personnel needs to deliver the project to be delivered, the work order information to be executed is determined through the front-end interactive interface, and a work order to be executed is generated based on the work order information to be executed; wherein the work order information to be executed includes: an identifier of a project to be deployed, an identifier of a destination server to be deployed, and an identifier of a software product to be applied; based on the work order to be executed, the software product to be applied in the software product library is extracted, a mirror package to be deployed is generated, and the mirror package to be deployed is pushed to the destination server to be deployed; based on a preset automatic deployment script, the destination server to be deployed automatically deploys the mirror package to be deployed.

[0014] On the third aspect, the embodiment of the present application also provides a non-volatile computer storage medium for software product management of a private cloud architecture, which stores computer-executable instructions, and is characterized in that the computer-executable instructions are set to: build a software product and upload the software product to a software product library; the software product library determines the attribute information of the software product, and displays the software product on the front-end interactive interface of the software product library based on the attribute information; wherein the attribute information at least includes a software product identifier; when the project delivery personnel need to deliver the project to be delivered, the work order information to be executed is determined through the front-end interactive interface, and a work order to be executed is generated based on the work order information to be executed; wherein the work order information to be executed includes: an identifier of a project to be deployed, an identifier of a destination server to be deployed, and an identifier of a software product to be applied; based on the work order to be executed, the software product to be applied in the software product library is extracted, a mirror package to be deployed is generated, and the mirror package to be deployed is pushed to the destination server to be deployed; based on a preset automatic deployment script, the destination server to be deployed automatically deploys the mirror package to be deployed.

[0015] The embodiments of the present application provide a software artifact management method, device, and medium for a private cloud architecture. By tracking software artifacts throughout the project delivery process based on a software artifact library, a version management method and system are established. The version management library records the delivered versions of software artifacts in each project, facilitating customized project deployment and traceability of software artifacts, providing a basis and guide for project version upgrades. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0017] Figure 1 A flowchart of a software product management method for a private cloud architecture provided in an embodiment of the present application;

[0018] Figure 2 A software product version deployment architecture diagram for a delivery project provided in an embodiment of the present application;

[0019] Figure 3 A schematic diagram of the internal structure of a software product management device for a private cloud architecture provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0021] The embodiments of the present application provide a software product management method, device and medium for a private cloud architecture to solve the following technical problem: for a private cloud architecture, the existing software product library does not have a management solution for project delivery versions to manage software products.

[0022] The technical solutions proposed in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0023] Figure 1 This is a flow chart of a software product management method for a private cloud architecture provided in an embodiment of the present application. Figure 1 As shown, the embodiment of the present application provides a software product management method for a private cloud architecture, which specifically includes the following steps:

[0024] Step 101: Build a software product and upload the software product to a software product library.

[0025] In one embodiment of the present application, in order to implement software product management for a private cloud architecture, it is first necessary to build a software product.

[0026] Specifically, a preset software product building tool is used to read a source code library to determine the source code corresponding to the software product, and the source code is compiled and packaged to generate a software product, wherein the software product is a program file that can be run on a destination server.

[0027] It should also be noted that optional build tools such as Jenkins and optional source code libraries such as git.

[0028] In one embodiment of the present application, in order to ensure that the software product can run normally on the destination server, after building the software product, the present application publishes the software product to a preset test destination server through a preset automatic publishing tool; based on the preset automated testing tool, the test destination server performs automated testing on the software product to determine whether the software product is qualified; if the software product is unqualified, the software product construction tool is triggered to re-read the source code corresponding to the software product to rebuild the software product.

[0029] In one embodiment of the present application, optional automatic publishing tools such as CI / CD tools and automated testing tools can be set up according to needs.

[0030] Furthermore, when the software product is tested and determined to be qualified, the software product is compressed to generate a compressed package, and uploaded to the software product library.

[0031] Step 102: The software product library determines attribute information of the software product and displays the software product on a front-end interactive interface of the software product library based on the attribute information.

[0032] In one embodiment of the present application, after the software product is uploaded to the software product library, the software product library will record the attribute information of the software product, including: software product identification, source code address and branch, build record identification, software product download address, software product configuration file, software product database upgrade script, software product version number, etc.

[0033] Furthermore, the software products are displayed on the front-end interactive interface of the software product library according to the attribute information of the software products, so that the project delivery personnel can select the required software products on the interactive interface.

[0034] Step 103: When the project delivery personnel need to deliver the project to be delivered, the to-be-delivered work order information is determined through the front-end interactive interface, and a to-be-delivered work order is generated based on the to-be-delivered work order information.

[0035] In one embodiment of the present application, the software artifact library provides the ability to publish software artifacts. When a project delivery person needs to deliver a pending project, the project delivery person selects the ID of the pending project and the ID of the target server to be deployed through the front-end interactive interface provided by the software artifact library, and selects the ID of the pending software artifact of the required version, thereby allowing the software artifact library to determine the work order information to be executed.

[0036] Furthermore, based on the information of the work order to be executed, a work order to be executed is generated.

[0037] Step 104: Based on the work order to be executed, extract the software products to be applied in the software product library, generate a mirror package to be deployed, and push the mirror package to be deployed to the target server to be deployed.

[0038] In one embodiment of the present application, after generating a work order to be executed, the software product library extracts the software products to be applied based on the identifier of the software products to be applied contained in the work order to be executed, and packages them to generate a mirror package to be deployed; then, based on the identifier of the target server to be deployed contained in the work order to be executed, the mirror package to be deployed is pushed to the target server to be deployed through a push tool.

[0039] In one embodiment of the present application, the optional push tool is, for example, a CI / CD tool.

[0040] Step 105: Based on the preset automatic deployment script, the target server to be deployed automatically deploys the image package 5 to be deployed.

[0041] In one embodiment of the present application, after the target server to be deployed receives the image package to be deployed, a preset automatic deployment script is run to automatically deploy the image package to be deployed.

[0042] It should be noted that in order to more clearly and intuitively display the versions of all software products in the project, this application also sets up a version management library.

[0043] In one embodiment of the present application, the version management library is used to track the entire delivery process.

[0044] Collect software product release information; wherein the release information at least includes: software product identification, software product type, software product storage address, software product library version number, software product deployment project identification, software product deployment destination server.

[0045] Furthermore, after collecting the release information of the software product, the release information can be analyzed based on the preset release information analysis rules to obtain the deployment architecture diagram of the software product; then

[0046] The front-end interactive interface of the version management library displays the deployment architecture diagram.

[0047] It should be noted that the types of deployment architecture diagrams include: software product version deployment architecture diagrams for the delivery project, deployment architecture diagrams of various versions of software products in the delivery project, and deployment architecture diagrams of software products in the project.

[0048] Composition, etc. For example Figure 2 The software product version deployment architecture diagram of a delivery project is shown in FIG. It can be understood that the deployment architecture diagram of each version of the software product in the delivery project can be understood as Figure 2 A row in

[0049] The deployment architecture diagram of the software products in the project can be understood as Figure 2 A column in .

[0050] In one embodiment of the present application, when a project to be delivered needs to be deployed in a replicated manner, it can be automatically completed directly through the version management library.

[0051] Specifically, in the front-end interactive interface of the version management library, determine the project ID to be copied, the server ID of the target to be copied, and the ID of the software product to be applied corresponding to the project to be delivered;

[0052] Software product identification determines the storage address of the software product to be applied, and based on the storage address, extracts the software product to be applied in the software product library, generates the image package to be copied, and pushes the image package to be copied to the destination server to be copied, so as to realize the replication deployment of the project to be delivered.

[0053] In one embodiment of the present application, when it is necessary to upgrade the version of the software product to be applied in the target server to be deployed, the work order information to be upgraded is determined through the front-end interactive interface, and based on the work order information to be upgraded, an upgrade work order is generated; wherein the work order information to be upgraded includes: the identifier of the project to be deployed, the identifier of the target server to be deployed, and the identifier of the software product to be upgraded; based on the work order to be upgraded, the software product library automatically upgrades the software product to be applied to the software product to be upgraded.

[0054] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, this application embodiment also provides a software product management device for private cloud architecture, whose structure is as follows: Figure 3 shown.

[0055] Figure 3 This is a schematic diagram of the internal structure of a software product management device for a private cloud architecture provided in an embodiment of the present application. Figure 3 As shown, the equipment includes:

[0056] at least one processor 301;

[0057] and, a memory 302 in communication with the at least one processor;

[0058] The memory 202 stores instructions that can be executed by at least one processor, and the instructions are executed by the at least one processor 301 to enable the at least one processor 301 to:

[0059] Build software artifacts and upload them to the software artifact library;

[0060] The software product library determines attribute information of the software product and displays the software product on a front-end interactive interface of the software product library based on the attribute information; wherein the attribute information includes at least a software product identifier;

[0061] When a project delivery person needs to deliver a pending project, he or she determines the pending work order information through the front-end interactive interface and generates a pending work order based on the pending work order information; wherein the pending work order information includes: the identification of the pending project, the identification of the target server to be deployed, and the identification of the software product to be applied;

[0062] Based on the work orders to be executed, the software products to be applied in the software product library are extracted, the image packages to be deployed are generated, and the image packages to be deployed are pushed to the target server to be deployed;

[0063] Based on the preset automatic deployment script, the target server to be deployed automatically deploys the image package to be deployed.

[0064] Some embodiments of the present application provide corresponding Figure 1 A non-volatile computer storage medium for software product management in a private cloud architecture stores computer executable instructions, wherein the computer executable instructions are configured as follows:

[0065] Build software artifacts and upload them to the software artifact library;

[0066] The software product library determines attribute information of the software product and displays the software product on a front-end interactive interface of the software product library based on the attribute information; wherein the attribute information includes at least a software product identifier;

[0067] When a project delivery person needs to deliver a pending project, he or she determines the pending work order information through the front-end interactive interface and generates a pending work order based on the pending work order information; wherein the pending work order information includes: the identification of the pending project, the identification of the target server to be deployed, and the identification of the software product to be applied;

[0068] Based on the work orders to be executed, the software products to be applied in the software product library are extracted, the image packages to be deployed are generated, and the image packages to be deployed are pushed to the target server to be deployed;

[0069] Based on the preset automatic deployment script, the target server to be deployed automatically deploys the image package to be deployed.

[0070] The various embodiments in this application are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences from the other embodiments. In particular, the IoT device and media embodiments are generally similar to the method embodiments, so their description is relatively simple. For relevant portions, refer to the description of the method embodiments.

[0071] The system and medium provided in the embodiments of the present application correspond one-to-one to the method. Therefore, the system and medium also have similar beneficial technical effects to their corresponding methods. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the system and medium will not be repeated here.

[0072] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0073] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0074] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0075] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0076] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0077] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0078] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0079] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0080] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A software product management method for a private cloud architecture, characterized in that: The method comprises: Building software products and uploading the software products to a software product library; The software product library determines attribute information of the software product and displays the software product on a front-end interactive interface of the software product library based on the attribute information; wherein the attribute information includes at least a software product identifier; When a project delivery person needs to deliver a project to be delivered, the front-end interactive interface determines the work order information to be executed, and generates a work order to be executed based on the work order information to be executed; wherein the work order information to be executed includes: an identifier of the project to be deployed, an identifier of the target server to be deployed, and an identifier of the software product to be applied; Extracting the software products to be applied from the software product library based on the work orders to be executed, generating a mirror package to be deployed, and pushing the mirror package to be deployed to the target server to be deployed; Based on a preset automatic deployment script, the target server to be deployed automatically deploys the image package to be deployed; The method further includes: a preset version management library collecting release information of the software product; wherein the release information includes at least: a software product identifier, a software product type, a software product storage address, a software product library version number, a software product deployment project identifier, and a software product deployment destination server; Analyzing the release information based on preset release information analysis rules to obtain a deployment architecture diagram of the software product; The deployment architecture diagram is displayed through the front-end interactive interface of the version management library; The method further includes: when it is necessary to replicate the project to be delivered, determining, on a front-end interactive interface of the version management library, an identifier of the project to be replicated, an identifier of a target server to be replicated, and an identifier of the software product to be applied corresponding to the project to be delivered; Based on the identification of the software product to be applied, the storage address of the software product to be applied is determined, and based on the storage address, the software product to be applied in the software product library is extracted to generate a mirror package to be copied, and the mirror package to be copied is pushed to the destination server to be copied, so as to realize the replicated deployment of the project to be delivered.

2. A software product management method for a private cloud architecture according to claim 1, characterized in that: Build software artifacts, including: Reading a source code library based on a preset software product building tool to determine the source code corresponding to the software product; The source code is compiled and packaged to generate the software product; wherein the software product is a program file that can be run on a destination server.

3. A software product management method for a private cloud architecture according to claim 2, characterized in that: After building the software product, the method further includes: Publishing the software product to a preset test destination server through a preset automatic publishing tool; Based on a preset automated testing tool, the test target server performs automated testing on the software product to determine whether the software product is qualified; In the case that the software product fails to meet the standards, the software product construction tool is triggered to re-read the source code corresponding to the software product to reconstruct the software product.

4. A software product management method for a private cloud architecture according to claim 1, characterized in that: After the target server to be deployed automatically deploys the image package to be deployed, the method further includes: In the case where a version upgrade of the software product to be applied in the target server to be deployed is required, determining the work order information to be upgraded through the front-end interactive interface, and generating the work order to be upgraded based on the work order information to be upgraded; wherein the work order information to be upgraded includes: an identifier of the project to be deployed, an identifier of the target server to be deployed, and an identifier of the software product to be upgraded; Based on the work order to be upgraded, the software product library automatically upgrades the software product to be applied to the software product to be upgraded.

5. The software product management method for a private cloud architecture according to claim 1, characterized in that: The attribute information also includes at least the source code address and branch, build record identifier, software product download address, software product configuration file, software product database upgrade script, and software product version number.

6. A software product management method for a private cloud architecture according to claim 1, characterized in that: The deployment architecture diagram at least includes: a deployment architecture diagram of software product versions of a delivery project, a deployment architecture diagram of each version of a software product in a delivery project, and a deployment architecture diagram of software products in a project.

7. A software product management device for a private cloud architecture, characterized in that: The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: Building software products and uploading the software products to a software product library; The software product library determines attribute information of the software product and displays the software product on a front-end interactive interface of the software product library based on the attribute information; wherein the attribute information includes at least a software product identifier; When a project delivery person needs to deliver a project to be delivered, the front-end interactive interface determines the work order information to be executed, and generates a work order to be executed based on the work order information to be executed; wherein the work order information to be executed includes: an identifier of the project to be deployed, an identifier of the target server to be deployed, and an identifier of the software product to be applied; Extracting the software products to be applied from the software product library based on the work orders to be executed, generating a mirror package to be deployed, and pushing the mirror package to be deployed to the target server to be deployed; Based on a preset automatic deployment script, the target server to be deployed automatically deploys the image package to be deployed; The method further includes: a preset version management library collecting release information of the software product; wherein the release information includes at least: a software product identifier, a software product type, a software product storage address, a software product library version number, a software product deployment project identifier, and a software product deployment destination server; Analyzing the release information based on preset release information analysis rules to obtain a deployment architecture diagram of the software product; The deployment architecture diagram is displayed through the front-end interactive interface of the version management library; The method further includes: when the project to be delivered needs to be replicated and deployed, determining, on a front-end interactive interface of the version management library, an identifier of the project to be replicated, an identifier of a target server to be replicated, and an identifier of the software product to be applied corresponding to the project to be delivered; Based on the identification of the software product to be applied, the storage address of the software product to be applied is determined, and based on the storage address, the software product to be applied in the software product library is extracted to generate a mirror package to be copied, and the mirror package to be copied is pushed to the destination server to be copied, so as to realize the replicated deployment of the project to be delivered.

8. A non-volatile computer storage medium for connecting multiple databases online simultaneously, storing computer-executable instructions, characterized in that: The computer executable instructions are configured to: Building software products and uploading the software products to a software product library; The software product library determines attribute information of the software product and displays the software product on a front-end interactive interface of the software product library based on the attribute information; wherein the attribute information includes at least a software product identifier; When a project delivery person needs to deliver a project to be delivered, the front-end interactive interface determines the work order information to be executed, and generates a work order to be executed based on the work order information to be executed; wherein the work order information to be executed includes: an identifier of the project to be deployed, an identifier of the target server to be deployed, and an identifier of the software product to be applied; Extracting the software products to be applied from the software product library based on the work orders to be executed, generating a mirror package to be deployed, and pushing the mirror package to be deployed to the target server to be deployed; Based on a preset automatic deployment script, the target server to be deployed automatically deploys the image package to be deployed; The method further includes: a preset version management library collecting release information of the software product; wherein the release information includes at least: a software product identifier, a software product type, a software product storage address, a software product library version number, a software product deployment project identifier, and a software product deployment destination server; Analyzing the release information based on preset release information analysis rules to obtain a deployment architecture diagram of the software product; The deployment architecture diagram is displayed through the front-end interactive interface of the version management library; The method further includes: when the project to be delivered needs to be replicated and deployed, determining, on a front-end interactive interface of the version management library, an identifier of the project to be replicated, an identifier of a target server to be replicated, and an identifier of the software product to be applied corresponding to the project to be delivered; Based on the identification of the software product to be applied, the storage address of the software product to be applied is determined, and based on the storage address, the software product to be applied in the software product library is extracted to generate a mirror package to be copied, and the mirror package to be copied is pushed to the destination server to be copied, so as to realize the replicated deployment of the project to be delivered.

Images