Third-party software package backup method, device and computer-readable storage medium

Abstract

The present invention discloses a method, device and computer-readable storage medium for backing up a third-party software package. The method comprises: obtaining and storing the organization name and package name of the third-party software package; determining the reference path of the third-party software package according to the stored organization name and package name; and downloading the third-party software package according to the reference path. The present invention can improve the stability of the program.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method and device for backing up a third-party software package and a computer-readable storage medium. Background Art

[0002] Currently, many companies need to use a large number of third-party software packages when developing programs. If third-party software packages are to be used, the existing technology is to directly call the third-party software packages, and the stability of the program is subject to the third-party software packages. Summary of the invention

[0003] The embodiments of the present invention provide a method and device for backing up a third-party software package, and a computer-readable storage medium, aiming to solve the technical problem of how to improve program stability.

[0004] An embodiment of the present invention provides a method for backing up a third-party software package, and the method for backing up a third-party software package includes the following steps:

[0005] Get the organization name and package name of the third-party software package and store them;

[0006] Determining a reference path of the third-party software package according to the stored organization name and the package name;

[0007] The third-party software package is downloaded according to the reference path.

[0008] In one embodiment, the method for backing up the third-party software package further includes:

[0009] Detecting whether the third-party software package is updated;

[0010] When the third-party software package is detected to be updated, the step of obtaining and storing the organization name and package name of the third-party software package is performed.

[0011] In one embodiment, the step of detecting whether the third-party software package is updated includes:

[0012] It is detected whether the suffix of the third-party software package is changed, wherein when it is detected that the suffix of the third-party software package is changed, it is determined that the third-party software package is updated.

[0013] In one embodiment, after the step of detecting whether the third-party software package is updated, the method further includes:

[0014] When no update of the third-party software package is detected, determining whether a historical organization name and a historical package name are stored;

[0015] If the historical organization name and the historical package name are stored;

[0016] Determine a reference path of the third-party software package according to the historical organization name and the historical package name;

[0017] The step of downloading the third-party software package according to the reference path is executed.

[0018] In one embodiment, the step of detecting whether the third-party software package is updated includes:

[0019] It is detected whether the source code of the third-party software package is changed, wherein if it is detected that the source code of the third-party software package is changed, it is determined that the third-party software package is updated.

[0020] In one embodiment, before the step of downloading the third-party software package according to the reference path, the method further includes:

[0021] Determine whether the path type of the reference path is a preset type;

[0022] When the path type is a preset type, the step of downloading the third-party software package according to the reference path is performed.

[0023] In one embodiment, after the step of determining whether the path type of the reference path is a preset type, the method further includes:

[0024] When the path type of the referenced path is not the preset type, a prompt message for manually downloading the third-party software package is output.

[0025] In one embodiment, after the step of downloading the third-party software package according to the reference path, the method further includes:

[0026] Determining whether a historical version of the third-party software package is stored;

[0027] When the third-party software package does not have the historical version, storing the third-party software package;

[0028] When a historical version of the third-party software package is stored, the historical version is deleted and stored as the third-party software package.

[0029] An embodiment of the present invention further provides a backup device for a third-party software package, the backup device for the third-party software package comprising: a memory, a processor, and a backup program for the third-party software package stored in the memory and executable on the processor, wherein the processor implements the steps of the backup method for the third-party software package as described above when executing the backup program for the third-party software package.

[0030] An embodiment of the present invention further provides a computer-readable storage medium on which a backup program of a third-party software package is stored. When the backup program of the third-party software package is executed by a processor, each step of the third-party software package backup method described above is implemented.

[0031] In the technical solution of this embodiment, the backup device of the third-party software package obtains and stores the organization name and package name of the third-party software package; determines the reference path of the third-party software package based on the stored organization name and package name; and downloads the third-party software package according to the reference path. Since the backup device of the third-party software package can obtain the organization name and package name of the third-party software package, and can determine the reference path of the third-party software package based on the organization name and package name, and then download the third-party software package to the local according to the reference path, after completing the above operations, the local third-party software package can be modified and referenced locally. When the program needs to use the third-party software package, the local third-party software package is used, and the developed program will not be subject to the server of the third-party software package. Therefore, the present invention can improve the stability of the program. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 A schematic diagram of the hardware architecture of a backup device for a third-party software package according to an embodiment of the present invention;

[0034] Figure 2 It is a flowchart of a first embodiment of a method for backing up a third-party software package of the present invention;

[0035] Figure 3 It is a flowchart of a second embodiment of the method for backing up a third-party software package of the present invention;

[0036] Figure 4 It is a flowchart of a third embodiment of the method for backing up a third-party software package of the present invention;

[0037] Figure 5 It is a flowchart diagram of a fourth embodiment of the method for backing up a third-party software package of the present invention. DETAILED DESCRIPTION

[0038] In order to better understand the above technical solution, exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0039] The main solution of the present invention is: the backup device of the third-party software package obtains and stores the organization name and package name of the third-party software package; determines the reference path of the third-party software package according to the stored organization name and package name; and downloads the third-party software package according to the reference path.

[0040] Since the backup device of the third-party software package can obtain the organization name and package name of the third-party software package, and can determine the reference path of the third-party software package based on the organization name and the package name, and then download the third-party software package to the local according to the reference path, after completing the above operations, the local third-party software package can be modified and referenced locally. When the program needs to use the third-party software package, the local third-party software package is used, and the developed program will not be subject to the server of the third-party software package. Therefore, the present invention can improve the stability of the program.

[0041] As an implementation, the backup device of the third-party software package can be as follows Figure 1 .

[0042] The embodiment of the present invention relates to a backup device for a third-party software package, which includes: a processor 101, such as a CPU, a memory 102, and a communication bus 103. The communication bus 103 is used to realize connection and communication between these components.

[0043] The memory 102 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. Figure 1 , the memory 102 as a computer-readable storage medium may include a detection program; and the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0044] Get the organization name and package name of the third-party software package and store them;

[0045] Determining a reference path of the third-party software package according to the stored organization name and the package name;

[0046] The third-party software package is downloaded according to the reference path.

[0047] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0048] Detecting whether the third-party software package is updated;

[0049] When the third-party software package is detected to be updated, the step of obtaining and storing the organization name and package name of the third-party software package is performed.

[0050] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0051] It is detected whether the suffix of the third-party software package is changed, wherein when it is detected that the suffix of the third-party software package is changed, it is determined that the third-party software package is updated.

[0052] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0053] When no update of the third-party software package is detected, determining whether a historical organization name and a historical package name are stored;

[0054] If the historical organization name and the historical package name are stored;

[0055] Determine a reference path of the third-party software package according to the historical organization name and the historical package name;

[0056] The step of downloading the third-party software package according to the reference path is executed.

[0057] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0058] It is detected whether the source code of the third-party software package is changed, wherein if it is detected that the source code of the third-party software package is changed, it is determined that the third-party software package is updated.

[0059] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0060] Determine whether the path type of the reference path is a preset type;

[0061] When the path type is a preset type, the step of downloading the third-party software package according to the reference path is performed.

[0062] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0063] When the path type of the referenced path is not the preset type, a prompt message for manually downloading the third-party software package is output.

[0064] In one embodiment, the processor 101 may be used to call the detection program stored in the memory 102 and perform the following operations:

[0065] Determining whether a historical version of the third-party software package is stored;

[0066] When the third-party software package does not have the historical version, storing the third-party software package;

[0067] When a historical version of the third-party software package is stored, the historical version is deleted and stored as the third-party software package.

[0068] In the technical solution of this embodiment, the backup device of the third-party software package obtains and stores the organization name and package name of the third-party software package; determines the reference path of the third-party software package based on the stored organization name and package name; and downloads the third-party software package according to the reference path. Since the backup device of the third-party software package can obtain the organization name and package name of the third-party software package, and can determine the reference path of the third-party software package based on the organization name and package name, and then download the third-party software package to the local according to the reference path, after completing the above operations, the local third-party software package can be modified and referenced locally. When the program needs to use the third-party software package, the local third-party software package is used, and the developed program will not be subject to the server of the third-party software package. Therefore, the present invention can improve the stability of the program.

[0069] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0070] Reference Figure 2 , Figure 2 The first embodiment of the method for backing up a third-party software package of the present invention comprises the following steps:

[0071] Step S10, obtaining and storing the organization name and package name of the third-party software package.

[0072] In this embodiment, the organization name and package name of the third-party software package are obtained by interacting with a remote server of the third-party software package.

[0073] Optionally, for the acquisition timing, it is possible to detect whether the third-party software package has been updated; when the third-party software package is detected to be updated, the steps of obtaining the organization name and package name of the third-party software package and storing them are performed. It is easy to understand that if there is no trigger condition for backing up the third-party software package, it is necessary to manually perform active backup or set a timer for automatic backup; if manual active backup is performed, it will take manpower; if a timer is set for automatic backup, the best backup time cannot be controlled, because the third-party software has not been updated, but the timer has triggered the backup operation, resulting in the backup being useless; if the third-party software package update is used as a trigger condition, the steps of backing up the third-party software package are performed, and no human intervention is required, and the automatic backup of the third-party software package can be achieved at the right time.

[0074] Optionally, for detecting whether the third-party software package is updated, it is possible to detect whether the suffix name of the third-party software package has changed, wherein, when the suffix name of the third-party software package is detected to have changed, it is determined that the third-party software package is updated. Since the backup device of the third-party software package can obtain the organization name and package name of the third-party software package and store them, the suffix name of the third-party software package can be further obtained, thereby determining whether the third-party software has been updated according to the change of the suffix name, wherein, when the suffix name of the third-party software package is detected to have changed, it is determined that the third-party software package is updated, and the steps of obtaining the organization name and package name of the third-party software package and storing them are performed to start backing up the third-party software package. In the technical solution of the present embodiment, it is determined whether the third-party software package is updated based on the detection of the suffix name of the third-party software package. In view of the fact that the computing power required for the suffix name detection is less, the efficiency of the present invention in backing up the third-party software package can be indirectly improved.

[0075] Optionally, to detect whether a third-party software package is updated, it is possible to detect whether the source code of the third-party software package has changed, wherein if it is detected that the source code of the third-party software package has changed, it is determined that the third-party software package is updated. It is possible to directly detect whether the source code of the third-party software package has changed. Optionally, it is determined whether the source code of the third-party software package has changed based on the update status of the source code sent by the server. Optionally, it is possible to detect whether the source code of the third-party software package has changed, and if it is determined that the source code of the third-party software package has not changed or the change status does not require an update, it is determined that the third-party software package has not been updated. In the technical solution of this embodiment, it is directly determined whether an update has been performed based on the change status of the source code. Compared with detecting whether the third-party software package is updated according to the suffix name, detecting whether the source code of the third-party software package has changed can obtain an update result with a higher accuracy rate.

[0076] Step S20: determining a reference path of the third-party software package according to the stored organization name and the package name.

[0077] In this embodiment, when it is determined that a third-party software package needs to be backed up, the reference path of the third-party software package can be determined based on the organization name and package name of the obtained third-party software package. Specifically, the source code path of the third-party software package is queried on the server side of the third-party software package or in the Maven repository according to the recorded organization name and package name to obtain the above-mentioned reference path.

[0078] Step S30: download the third-party software package according to the reference path.

[0079] In this embodiment, a request for obtaining the third-party software package is generated according to the reference path and sent to the server of the third-party software package, wherein the third-party server responds to the request for obtaining the third-party software package and sends the third-party software package to the local server, so that the backup device of the third-party software package completes the backup operation of the third-party software package.

[0080] Specifically, a hook trigger tool is set on the server side of the third-party software package. Once the build.gradle or pom.xml files on the server side are changed or a package with a .jar suffix is ​​added, the hook trigger tool is triggered to download or update the jar package source code.

[0081] Optionally, when no update of the third-party software package is detected, determine whether the historical organization name and the historical package name are stored; if the historical organization name and the historical package name are stored; determine the reference path of the third-party software package according to the historical organization name and the historical package name; execute the step of downloading the third-party software package according to the reference path, and further, when no update of the third-party software package is detected within a preset time period, execute the step of determining whether the historical organization name and the historical package name are stored. In the technical scheme of the optional embodiment, considering that the update status of the software package is determined based on the suffix name or the source code, therefore, this embodiment can perform the operation of backing up the third-party software package when one of the internal source code or the suffix name of the third-party software package changes and the other does not change, for example: in the first case, when the source code does not change, it is determined that the third-party software package is not updated, but the suffix name changes; in the second case, when the suffix name changes, it is determined that the third-party software package is not updated, but the source code does not change.

[0082] In the technical solution of the present embodiment, since the backup device of the third-party software package can obtain the organization name and package name of the third-party software package, and can determine the reference path of the third-party software package based on the organization name and the package name, and then download the third-party software package to the local according to the reference path, after completing the above operations, the local third-party software package can be modified and referenced locally. When the program needs to use the third-party software package, the local third-party software package is used, and the developed program will not be subject to the server of the third-party software package. Therefore, the present invention can improve the stability of the program.

[0083] Reference Figure 3 , Figure 3 The second embodiment of the method for backing up a third-party software package of the present invention is based on the first embodiment and, before step S30, further includes:

[0084] Step S40: Determine whether the path type of the reference path is a preset type.

[0085] In this embodiment, considering that some types of path types have download permission issues, it is necessary to first determine whether the path type is a preset type before determining whether the backup can be completed. For example, the preset types include git path type, GitHub path type, and SVN path type, etc., where GitHub is a hosting platform for open source and private software projects. It is named GitHub because it only supports Git as the only version library format for hosting; SVN is the abbreviation of Subversion, an open source version control system that uses a branch management system S. It is easy to understand that SVN is used for multiple people to jointly develop the same project and share resources.

[0086] Step S50, when the path type is a preset type, executing the step of downloading the third-party software package according to the reference path.

[0087] In the technical solution of this embodiment, by identifying the type of the referenced path, it can be determined in advance that the path type can be used to complete the backup of the third-party software package, thereby preventing the backup failure caused by the path type.

[0088] Reference Figure 4 , Figure 4 The third embodiment of the method for backing up a third-party software package of the present invention is based on any one of the first to second embodiments, and after step S40, further includes:

[0089] Step S60: When the path type of the referenced path is not the preset type, output prompt information for manually downloading the third-party software package.

[0090] In the technical solution of this embodiment, when it is determined that the reference path type will cause the automatic download of the third-party software package to fail, the user can be prompted to download manually through a prompt message, thereby improving the user experience.

[0091] Reference Figure 5 , Figure 5 The fourth embodiment of the method for backing up a third-party software package of the present invention is based on any one of the first to third embodiments, and after step S30, further includes:

[0092] Step S70: Determine whether a historical version of the third-party software package is stored.

[0093] In this embodiment, after a third-party software package is newly downloaded, it can be determined whether a corresponding historical version of the software package is stored. Specifically, it can be determined based on the version number, organization name, and package name of the newly downloaded third-party software package and the stored old software package. For example, when the version number of the old software package is 1.1 and the version number of the newly downloaded software package is 1.2, and the organization name and package name of the newly downloaded third-party software package are the same as those of the old software package, the old software package is considered to be a historical version of the newly downloaded third-party software package.

[0094] Step S80: When the third-party software package does not have the historical version, store the third-party software package.

[0095] Step S90: When a historical version of the third-party software package is stored, the historical version is deleted and stored as the third-party software package.

[0096] In this embodiment, when a historical version of the third-party software package is stored, the historical version is deleted and stored as the third-party software package, or the historical version is overwritten by the third-party software package.

[0097] Optionally, when the path type is a git path, determine whether the third-party software source code already exists in the local repository. If so, execute git pull to update the source code to the latest version. If not, execute git clone to back it up locally.

[0098] Optionally, when the path type is svn path, determine whether the third-party software source code already exists in the local repository. If it does, use the svn update command to update it to the latest version. If it does not exist, use svn checkout to back it up locally.

[0099] In the technical solution of this embodiment, by deleting the old software package of the historical version and then storing the new third-party software package, waste of storage space can be avoided.

[0100] To achieve the above-mentioned purpose, an embodiment of the present invention further provides a backup device for a third-party software package, wherein the backup device for the third-party software package comprises: a memory, a processor, and a backup program for the third-party software package stored in the memory and executable on the processor, wherein the processor implements the steps of the backup method for the third-party software package as described above when executing the backup program for the third-party software package.

[0101] To achieve the above objectives, an embodiment of the present invention further provides a computer-readable storage medium, on which a backup program of a third-party software package is stored. When the backup program of the third-party software package is executed by a processor, each step of the third-party software package backup method described above is implemented.

[0102] Those skilled in the art will appreciate that embodiments of the present invention may be provided as a backup program product of a method, system, or third-party software package. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a network configuration product program implemented on one or more computer-usable computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0103] The present invention is described with reference to flowcharts and / or block diagrams of backup program products of methods, devices (systems), and third-party software packages according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as a combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by the backup program instructions of the third-party software package. The backup program instructions of these third-party software packages 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 generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the backup program instructions in the flowchart and / or block diagram. 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.

[0104] The backup program instructions of these third-party software packages can also be stored in a computer-readable memory that can guide 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 a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0105] The backup program instructions of these third-party software packages can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0106] It should be noted that in the claims, any reference signs placed between brackets shall not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claim. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention may be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.

[0107] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0108] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for backing up a third-party software package, characterized in that: The backup method of the third-party software package comprises the following steps: Get the organization name and package name of the third-party software package and store them; Determining a reference path of the third-party software package according to the stored organization name and the package name; Download the third-party software package according to the reference path; Before the step of obtaining and storing the organization name and package name of the third-party software package, the method further includes: Determining whether the third-party software package is updated based on detecting the suffix name of the third-party software package or the change of the source code of the third-party software package; If yes, then execute the step of obtaining the organization name and package name of the third-party software package and storing them; Before the step of downloading the third-party software package according to the reference path, the method further includes: Determine whether the path type of the reference path is a preset type, where the preset type includes a git path type, a GitHub path type, and an SVN path type; When the path type is a preset type, executing the step of downloading the third-party software package according to the reference path; The step of downloading the third-party software package according to the reference path includes: generating an acquisition request for the third-party software package according to the reference path, and sending the request to a server of the third-party software package, wherein the server of the third-party software package responds to the acquisition request and sends the third-party software package to a local server, so that the backup device of the third-party software package completes the backup operation of the third-party software package; A hook trigger tool is set on the server of the third-party software package. If the build.gradle or pom.xml file in the server of the third-party software package is changed or a package with a .jar suffix is ​​added, the hook trigger tool is triggered to download or update the jar package source code; After the step of downloading the third-party software package according to the reference path, the method further includes: Determining whether a historical version of the third-party software package is stored; When the third-party software package does not have the historical version, storing the third-party software package; When a historical version of the third-party software package is stored, deleting the historical version and storing it as the third-party software package, or overwriting the historical version with the third-party software package; When the path type is a git path, determine whether the third-party software source code already exists in the local repository. If so, execute git pull to update the source code to the latest version. If not, execute git clone to back it up locally. When the path type is svn path, determine whether the third-party software source code already exists in the local repository. If it does, use the svn update command to update it to the latest version. If it does not exist, use svn checkout to back it up locally.

2. The method for backing up a third-party software package according to claim 1, characterized in that: The backup method of the third-party software package further includes: Detecting whether the third-party software package is updated; When the third-party software package is detected to be updated, the step of obtaining and storing the organization name and package name of the third-party software package is performed.

3. The method for backing up a third-party software package according to claim 1, wherein: The step of detecting whether the third-party software package is updated comprises: It is detected whether the suffix of the third-party software package is changed, wherein when it is detected that the suffix of the third-party software package is changed, it is determined that the third-party software package is updated.

4. The method for backing up a third-party software package according to claim 2, wherein: After the step of detecting whether the third-party software package is updated, the method further includes: When no update of the third-party software package is detected, determining whether a historical organization name and a historical package name are stored; If the historical organization name and the historical package name are stored; Determine a reference path of the third-party software package according to the historical organization name and the historical package name; The step of downloading the third-party software package according to the reference path is executed.

5. The method for backing up a third-party software package as claimed in claim 2, characterized in that: The step of detecting whether the third-party software package is updated comprises: It is detected whether the source code of the third-party software package is changed, wherein if it is detected that the source code of the third-party software package is changed, it is determined that the third-party software package is updated.

6. The method for backing up a third-party software package according to claim 1, wherein: After the step of determining whether the path type of the reference path is a preset type, the method further includes: When the path type of the referenced path is not the preset type, a prompt message for manually downloading the third-party software package is output.

7. A backup device for a third-party software package, characterized in that: The backup device of the third-party software package includes: a memory, a processor, and a backup program of the third-party software package stored in the memory and executable on the processor, wherein the processor implements the steps of the backup method of the third-party software package according to any one of claims 1 to 6 when executing the backup program of the third-party software package.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a backup program of the third-party software package. When the backup program of the third-party software package is executed by the processor, the steps of the method for backing up the third-party software package according to any one of claims 1 to 6 are implemented.

Images