CN117632188A

CN117632188A - Version package updating method, device, equipment and readable storage medium

Info

Publication number: CN117632188A
Application number: CN202311655267.XA
Authority: CN
Inventors: 钱永春
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2023-12-05
Filing date: 2023-12-05
Publication date: 2024-03-01

Abstract

The application discloses a version package updating method, device and equipment and a readable storage medium, and relates to the technical field of big data. The version package updating method is applied to a version machine, the version machine is provided with a target scheduling script, and the version package updating method comprises the following steps: acquiring an update script on a target server based on the target scheduling script; traversing the version package name list, and judging whether a first version package of a target type exists or not; traversing the first version package of the target type under the condition that the judging result is that the first version package of the target type exists, and updating the first version package of the target type based on the updating script to generate a second version package; and sending the second version package to the target server. According to the method and the device for deploying the version package, the problem that the version package is too long in time consumption for deploying the version package to the target server can be solved, meanwhile, the accuracy of deployment is improved, and positioning is easy after deployment errors occur.

Description

Version package updating method, device, equipment and readable storage medium

Technical Field

The application belongs to the technical field of big data, and particularly relates to a version package updating method, device and equipment and a readable storage medium.

Background

Typically, with hundreds of version packages deployed to the production environment of hundreds of target servers, existing solutions manually deploy version packages to each server in turn according to the deployment server list of each version package.

However, this approach is too time consuming due to the too many version packages and servers; and is very error-prone due to manual operation, and has the problem of being extremely difficult to locate after error.

Disclosure of Invention

The embodiment of the application provides a version package updating method, device and equipment and a readable storage medium, which can solve the problem that the version package is too long in time consumption for being deployed to a target server, improve the accuracy of deployment, and facilitate positioning after deployment errors.

In a first aspect, an embodiment of the present application provides a method for updating a version package, which is applied to a version machine, where the version machine is provided with a target scheduling script, and the method for updating the version package includes: acquiring an update script on a target server based on the target scheduling script; traversing the version package name list, and judging whether a first version package of a target type exists or not; traversing the first version package of the target type under the condition that the judging result is that the first version package of the target type exists, and updating the first version package of the target type based on the updating script to generate a second version package; and sending the second version package to the target server.

According to an embodiment of the first aspect of the present application, based on the target scheduling script, obtaining an update script on the target server includes: based on the target scheduling script, acquiring an updating script on the target server through a first command of the encryption-free protocol.

According to any of the foregoing embodiments of the first aspect of the present application, sending the second version package to the target server includes: the second version package is sent to the target server based on a second command of the encryption-free protocol.

According to any of the foregoing embodiments of the first aspect of the present application, the sending of the second version package to the target server is parallel.

According to any one of the foregoing embodiments of the first aspect of the present application, after the second version package is sent to the target server based on the second command of the encryption-free protocol, the method for updating the version package further includes: changing the authority of the second version package into an updated user; restarting the second version package after the modification authority.

According to any one of the foregoing embodiments of the first aspect of the present application, before updating the first version package on the version machine based on the update script and generating the second version package, the method for updating the version package further includes:

based on the update script, the first configuration of the first version package is updated to generate a second configuration, and the second configuration is adapted to the environment of the target server.

According to any of the foregoing embodiments of the first aspect of the present application, updating the first configuration of the first version package, generating the second configuration includes: the method comprises the steps of obtaining a version package catalog of a first version package, wherein the version package catalog comprises a first version package extension; classifying the first version package based on the version package extension name to generate a version package name list; traversing each version package name list, and updating the first configuration of the first version package to the second configuration.

In a second aspect, an embodiment of the present application provides an update apparatus for a version package, where the update apparatus for a version package includes: the acquisition module is used for acquiring an update script on the target server based on the target scheduling script; the judging module is used for traversing the version package name list and judging whether a first version package of the target type exists or not; the updating module is used for traversing the first version package of the target type under the condition that the judging result is present, updating the first version package of the target type based on the updating script, and generating a second version package; and the sending module is used for sending the second version packet to the target server.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements a method for updating version packages as in the first aspect of the embodiments of the present application.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement a method for updating a version package as in the first aspect of embodiments of the present application.

According to the version package updating method, device and equipment and the readable storage medium, the version package on the version machine is updated by setting the target scheduling script on the version machine and scheduling the updating script on the target server through the target scheduling script, and finally the updated version package is sent to the target server to update the version package on the target server. On one hand, the scheduling script is adopted to automatically update the version package without manually updating the version package to the target server in turn, so that the updating efficiency of the version package is improved, the updating time consumption of the version machine is reduced, and the updating is not easy to make mistakes. On the other hand, since the script has an operation log when executed, all operations are recorded in the operation log, even if an update is made, an error problem is easily located.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described, and it is possible for a person skilled in the art to obtain other drawings according to these drawings without inventive effort.

Fig. 1 is a flow chart of a method for updating version packages according to an embodiment of the present application;

FIG. 2 is a flow chart of another method for updating version packages according to an embodiment of the present application;

FIG. 3 is a flow chart of a method for updating a version package according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an updating device of a version package according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Features and exemplary embodiments of various aspects of the present application are described in detail below to make the objects, technical solutions and advantages of the present application more apparent, and to further describe the present application in conjunction with the accompanying drawings and the detailed embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative of the application and are not intended to be limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by showing examples of the present application.

The data acquisition, storage, use, processing and the like in the technical scheme meet the relevant regulations of national laws and regulations.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

It should be understood that the term "and/or" as used herein is merely one relationship describing the association of the associated objects, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Accordingly, this application is intended to cover such modifications and variations of this application as fall within the scope of the appended claims (the claims) and their equivalents. The embodiments provided in the examples of the present application may be combined with each other without contradiction.

In order to solve the problems of long time consumption, easy error and difficult positioning after error in the related technology, the embodiment of the application provides a version package updating method, device and equipment and a readable storage medium. The following first describes a version package updating method provided in the embodiments of the present application.

Fig. 1 is a flow chart of a method for updating version packages according to an embodiment of the present application. The version package updating method is applied to a version machine, and a target scheduling script is set on the version machine, as shown in fig. 1, the version package updating method 100 may include: s101 to S104.

In some embodiments, the version package may include jar package, war package, and front-end folders (front-end static files including js, html, css files and font pictures). The version machine is a server for storing version packages to be updated.

S101, acquiring an update script on a target server based on a target scheduling script.

In some embodiments, the target scheduling script may include a shell-based scheduling script for invoking an update script of the target server according to a network interconnection protocol (Internet Protocol, IP) of the target server. The target server is the server that updates the version package. Each target server is provided with an update script which is responsible for copying version package source files of the target server, receiving updated version packages sent by the version machine and restarting the updated version packages. For jar packets, direct restarting is all right; only reloading an Nginx server for front-end files deployed on a reverse proxy server (Nginx); the Tomcat server may be restarted for war packages deployed on Tomcat server (Apache Tomcat).

In some embodiments, when the version package includes a jar package, a war package and a zip package, the execution steps of the target scheduling script are to input the version package catalog, generate a version package list, update the configuration of the jar package and the war package, and finally update the jar package, the war package and the zip package sequentially. The zip package may update the new version package directly without updating the new version package configuration.

S102, traversing the version package name list, and judging whether a first version package of the target type exists or not.

The version package name list is generated from a version package directory that contains version package extensions.

Illustratively, the version package extension may include: the entire front-end file is compressed into a zip package, which can be classified according to the package extensions of the three versions to generate three files: war.list, jar.list and zip.list. The three files are respectively a jar package, a war package and a name list of a front-end file. If there is no version package of a certain type in the version package directory, the name list file for that type package will not be generated. When the version package of the war type is to be updated, firstly traversing all the version package name lists, and detecting whether the version package name list of the war. When jar and zip type version packages are to be updated, the steps are similar to those of updating the jar type version package, and will not be described again.

And S103, traversing the first version package of the target type under the condition that the judging result is present, updating the first version package of the target type based on the updating script, and generating a second version package.

Continuing with the above example, this step may be understood as traversing all the first version packages under war.list and based on the update script, updating all the first version packages under war.list in turn and generating a second version package if war.list is detected as present.

And S104, sending the second version package to the target server.

According to the version package updating method, the target scheduling script is set on the version machine, the version package on the version machine is updated through the target scheduling script scheduling the updating script on the target server, and finally the updated version package is sent to the target server, so that the version package on the target server is updated. On one hand, the scheduling script is adopted to automatically update the version package without manually updating the version package to the target server in turn, so that the updating efficiency of the version package is improved, the updating time consumption of the version machine is reduced, and the updating is not easy to make mistakes. On the other hand, since the script has an operation log when executed, all operations are recorded in the operation log, even if an update is made, an error problem is easily located.

In some embodiments, S101, based on the target scheduling script, acquiring the update script on the target server may include: step one.

Step one, based on a target scheduling script, acquiring an updating script on a target server through a first command of a secret-free protocol.

In some embodiments, the first command of the secret-free protocol may include a SSH command of a Secure Shell protocol (SSH), and the command line always prompts the user to enter a server password when executing the SSH protocol-based command (e.g., SSH and scp commands). The sshpass is open source software, and a user can avoid inputting a password when acquiring an update script of a target server by combining a sshpass command with a command based on a ssh protocol, so that automation is realized when acquiring the update script of the target server.

The specific usage of sshpass is: sshpass-p "$ { password }" $ { ssh_cmd }, wherein $ { password } is the password of the server side and $ { ssh_cmd } is the command specific form based on the ssh protocol. For example: use of sshpass commands to secure ssh:

sshpass-p“${password}”ssh-o StrictHostKeyChecking＝no${user}@${ip}

wherein, $ { user }, $ { ip }, and $ { password }, are the server user, ip, and password, respectively.

There are two uses for using sshpass commands to secure scp, the first of which is used when copying client server files to a server directory: sshpass-p "$ { password }" scp-oStrictHostKeyChecking = no $ { file $ { user } @ { ip }: $ { dir }, where $ { user }, $ { password }, $ { ip }, $ { dir and $ { file $ are server users, passwords, ips, directories and client files, respectively.

When copying a server file to a client directory: sshpass-p "$ { password }" scp-o StrictHostKeyChecking = no $ { user @ { ip }: $ { file } $ { dir }, where $ { user }, $ { password }, $ { file }, $ { dir are server users, passwords, ips, files, and client directories, respectively; o StrictHostKeyChecking is an ssh protocol configuration option, which is added in the command based on the ssh protocol because if the server is connected for the first time, the public key digest of the server is displayed, the user is prompted whether to trust the server, if the user is not confirmed, the prompt is not skipped, thus the automation task is interrupted, and the addition of this option can automatically accept a new public key when the server is connected for the first time.

For example, sshpass secret-free authentication may be replaced with ssh public key secret-free authentication or expect secret-free authentication. ssh public key secret-free authentication means that when commands based on the ssh protocol (such as commands of ssh and scp) are used among all servers, the copy of the public key $ { HOME }. Ssh/id_rsa.pub on the client server can be added to $ { HOME }/. Ssh/authorized_keys on the server, and then when commands based on the ssh protocol (such as commands of ssh, scp) are used from the client server, the user can be prevented from entering a password on the command line. In the expect secret-free authentication, expect is an open-source automatic interaction suite, so that automatic and interactive communication can be realized without human intervention, and therefore, commands based on the ssh protocol can be realized through expect, and a user is free from inputting passwords.

In some embodiments, S104, sending the second version package to the target server may include: and step two, performing step two.

And step two, based on a second command of the encryption-free protocol, sending a second version packet to the target server.

In some embodiments, the second command of the secret-free protocol may include a Secure copy command (SCP) of the ssh protocol, and likewise, the SCP command may be combined with an expect command, or a sshpass command, so that when the second version packet is sent to the target server, the password is omitted from being input, thereby realizing automation.

In some embodiments, the method for updating the version package before the second step may further include: the source file of the target server version package is backed up.

In some embodiments, S104, sending the second version package to the target server is a parallel sending.

Since one version package may be deployed to a plurality of target servers and/or a plurality of version packages may be deployed to one server when deploying the version package to the target servers, one version package may be simultaneously transmitted to a plurality of target servers and/or a plurality of version packages may be simultaneously transmitted to one server when transmitting, as to how many version packages may be simultaneously transmitted at most depends on the performance of the version machine, the better the performance of the version machine, the more version packages may be simultaneously transmitted.

After the second version packet is sent to the target server based on the second command of the encryption-free protocol, the updating method may further include: step three to step four.

And step three, changing the authority of the second version package into an updated user.

Since all update procedures are using root user operations, the version package owner needs to be modified to be the update user.

And step four, restarting the second version package after the permission is changed.

In some embodiments, at S103, based on the update script, updating the first version package on the version machine, before generating the second version package, the method 100 for updating the version package may further include: and step five.

And fifthly, updating the first configuration of the first version package based on the updating script, and generating a second configuration which is suitable for the environment of the target server.

The first configuration of the first version package refers to related parameters of the first version package, and before updating the first version package, the configuration of the first version package needs to be updated, so that after the second version package is sent to the target server, the configuration of the second version package can also adapt to the environment of the target server.

In combination with all the foregoing embodiments, a flowchart of another version package update method provided in the embodiments of the present application may be obtained, and fig. 2 is a schematic flow diagram of another version package update method provided in the embodiments of the present application, where, as shown in fig. 2, the version package update method 100 may include: s201 to S207.

S201, based on the target scheduling script, acquiring an updating script on the target server through a first command of the encryption-free protocol.

S202, traversing the version package name list, and judging whether a first version package of the target type exists or not.

S203, updating the first configuration of the first version package based on the updating script, and generating a second configuration, wherein the second configuration is suitable for the environment of the target server.

It should be understood that, when the configuration of the version package can adapt to the environment of the target server, the corresponding version package can adapt to the target server without messy codes or other situations.

And S204, traversing the first version package of the target type to generate a second version package under the condition that the judging result is that the target type exists.

S205, a second version packet is sent to the target server based on a second command of the encryption-free protocol.

S206, changing the authority of the second version package into an updated user.

S207, restarting the second version package after the modification authority.

For a detailed analysis of S201 to S207, refer to the detailed description of the first to fifth steps in the above embodiment, and are not described herein.

In some embodiments, updating the first configuration of the first version package based on the update script in S203, generating the second configuration may include: s301 to S303.

S301, a version package catalog of a first version package is obtained, wherein the version package catalog comprises a first version package extension.

S302, classifying the first version package based on the version package extension name to generate a version package name list.

Illustratively, the version package extension may include: the entire front-end file is compressed into a zip package, which can be classified according to the package extensions of the three versions to generate three files: war.list, jar.list and zip.list. The three files are respectively a jar package, a war package and a name list of a front-end file. If there is no version package of a certain type in the version package directory, the name list file for that type package will not be generated.

S303, traversing each version package name list, and updating the first configuration of the first version package into the second configuration.

When the configuration of the version package of the war type is to be updated, firstly traversing all version package name lists, detecting whether the version package name list of the war.list exists or not, judging whether the war.list exists and is not empty, traversing the war.list under the condition that the war.list exists and is not empty, and simultaneously calling an updating script of the single version package configuration to finish updating the first configuration of the first version package under the war.list into the second configuration.

Based on the same technical conception as the version package updating method provided by the embodiment, the application also provides a version package updating device. See the examples below.

Fig. 4 is a schematic structural diagram of a version package updating device according to an embodiment of the present application, and as shown in fig. 4, the version package updating device 400 may include: the device comprises an acquisition module 410, a judgment module 420, an update module 430 and a sending module 440.

An obtaining module 410, configured to obtain an update script on a target server based on a target scheduling script;

a judging module 420, configured to traverse the version package name list and judge whether a first version package of the target type exists;

the updating module 430 is configured to traverse the first version package of the target type, update the first version package of the target type based on the update script, and generate a second version package if the determination result is that the first version package of the target type exists;

and a sending module 440, configured to send the second version packet to the target server.

In some embodiments, the obtaining module 410 is specifically configured to obtain, based on the target scheduling script, an update script on the target server through a first command of the privacy-free protocol.

In some embodiments, the sending module 440 is specifically configured to send the second version packet to the target server based on the second command of the encryption-free protocol.

In some embodiments, the sending module 440 is specifically configured to send the second version package to the target server as a parallel sending.

In some embodiments, the updating device of the version package may further include a modification module and a restart module, where the modification module is specifically configured to modify the rights of the second version package to the update user, and the restart module is specifically configured to restart the second version package after the rights are modified.

In some embodiments, the update module 430 is specifically configured to update the first configuration of the first version package based on the update script, and generate a second configuration that is adapted to the environment of the target server.

In some embodiments, the version package updating device further includes a classification module and a traversal module, where the obtaining module 410 is specifically configured to obtain a version package directory of the first version package, and the version package directory includes a first version package extension; the classification module is specifically used for classifying the first version package based on the version package extension name to generate a version package name list; the traversing module is specifically configured to traverse each version package name list and update the first configuration of the first version package to the second configuration.

According to the version package updating device, the version package on the version machine is updated by setting the target scheduling script on the version machine and scheduling the updating script on the target server through the target scheduling script, and finally the updated version package is sent to the target server to update the version package on the target server. On one hand, the scheduling script is adopted to automatically update the version package without manually updating the version package to the target server in turn, so that the updating efficiency of the version package is improved, the updating time consumption of the version machine is reduced, and the updating is not easy to make mistakes. On the other hand, since the script has an operation log when executed, all operations are recorded in the operation log, even if an update is made, an error problem is easily located.

Fig. 5 is a schematic diagram of an electronic device provided in an embodiment of the present application, where, as shown in fig. 5, the electronic device includes: a processor 501 and a memory 502 storing computer program instructions.

In particular, the processor 501 may include a central processing unit (Central Processing Unit, CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.

Memory 502 may include mass storage for data or instructions. By way of example, and not limitation, memory 502 may comprise a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, magnetic tape, or universal serial bus (Universal Serial Bus, USB) Drive, or a combination of two or more of the foregoing. Memory 502 may include removable or non-removable (or fixed) media, where appropriate. Memory 502 may be internal or external to the electronic device, where appropriate. In a particular embodiment, the memory 502 is a non-volatile solid state memory.

The Memory may include Read Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory comprises one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described with reference to the method according to the first aspect of the present application.

The processor 501 implements the method of updating the version package of any of the above embodiments by reading and executing the computer program instructions stored in the memory 502.

In one example, an electronic device may also include a communication interface 503 and a bus 510. As shown in fig. 3, the processor 501, the memory 502, and the communication interface 503 are connected to each other by a bus 510 and perform communication with each other.

The communication interface 503 is mainly used to implement communication between each module, apparatus, unit and/or device in the embodiments of the present application.

Bus 510 includes hardware, software, or both that couple the components of the terminal services device to each other. By way of example, and not limitation, the buses may include an accelerated graphics port (Accelerated Graphics Port, AGP) or other graphics Bus, an enhanced industry standard architecture (Extended Industry Standard Architecture, EISA) Bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (Industry Standard Architecture, ISA) Bus, an Infiniband interconnect, a low pin count (Linear Predictive Coding, LPC) Bus, a memory Bus, a micro channel architecture (MicroChannel Architecture, MCa) Bus, a peripheral component interconnect (Peripheral Component Interconnect, PCI) Bus, a PCI-Express (Peripheral Component Interconnect-X, PCI-X) Bus, a serial advanced technology attachment (Serial Advanced Technology Attachment, SATA) Bus, a video electronics standards association Local Bus (VLB) Bus, or other suitable Bus, or a combination of two or more of these. Bus 510 may include one or more buses, where appropriate. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

The device can execute the version package updating method in the embodiment of the application based on each unit/component in the version package updating device, thereby realizing the version package updating method described in fig. 1

In addition, in combination with the method for updating the version package in the above embodiment, the embodiment of the application may be implemented by providing a computer readable storage medium. The computer readable storage medium has stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement the version package updating method in the above-described embodiments.

It should be clear that the present application is not limited to the particular arrangements and processes described above and illustrated in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions, or change the order between steps, after appreciating the spirit of the present application.

The functional blocks shown in the above-described structural block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor Memory devices, read-Only Memory (ROM), flash Memory, erasable Read-Only Memory (Erasable Read Only Memory, EROM), floppy disks, compact discs (Compact Disc Read-Only Memory, CD-ROM), optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.

It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be different from the order in the embodiments, or several steps may be performed simultaneously.

Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In the foregoing, only the specific embodiments of the present application are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, which are intended to be included in the scope of the present application.

Claims

1. A method for updating a version package, applied to a version machine, the version machine being provided with a target scheduling script, the method comprising:

acquiring an update script on a target server based on the target scheduling script;

traversing the version package name list, and judging whether a first version package of a target type exists or not;

traversing the first version package of the target type under the condition that the judging result is that the first version package of the target type exists, updating the first version package of the target type based on the updating script, and generating a second version package;

and sending the second version package to the target server.

2. The method for updating a version package according to claim 1, wherein the obtaining an update script on a target server based on the target scheduling script comprises:

and acquiring an update script on the target server through a first command of the encryption-free protocol based on the target scheduling script.

3. The method for updating the version package according to claim 1, wherein the sending the second version package to the target server comprises:

and sending the second version package to the target server based on a second command of a secret-free protocol.

4. The method for updating a version package according to claim 3, wherein the sending the second version package to the target server is parallel sending.

5. The method for updating a version package according to claim 3, wherein after the second command based on the encryption-free protocol sends the second version package to the target server, the method further comprises:

changing the authority of the second version package into an updated user;

restarting the second version package after changing the authority.

6. The method for updating a version package according to claim 1, wherein before the updating the first version package on the version machine based on the update script and generating the second version package, the method further comprises:

based on the update script, updating a first configuration of the first version package, and generating a second configuration, wherein the second configuration is adapted to the environment of the target server.

7. The method of updating a version package according to claim 6, wherein the updating the first configuration of the first version package generates a second configuration comprising:

the method comprises the steps of obtaining a version package catalog of the first version package, wherein the version package catalog comprises a first version package extension;

classifying the first version package based on the version package extension name to generate a version package name list;

and traversing each version package name list, and updating the first configuration of the first version package into the second configuration.

8. An apparatus for updating a version package, the apparatus comprising:

the acquisition module is used for acquiring an update script on the target server based on the target scheduling script;

the judging module is used for traversing the version package name list and judging whether a first version package of the target type exists or not;

the updating module is used for traversing the first version package of the target type under the condition that the judging result is present, updating the first version package of the target type based on the updating script, and generating a second version package;

and the sending module is used for sending the second version packet to the target server.

9. An electronic device, the electronic device comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a version package updating method as claimed in any one of claims 1-7.

10. A computer readable storage medium, having stored thereon computer program instructions, which when executed by a processor, implement a method of updating a version package according to any of claims 1-7.