CN117807043A - Method, device, computer equipment and storage medium for synchronizing Nexus warehouse products - Google Patents
Method, device, computer equipment and storage medium for synchronizing Nexus warehouse products Download PDFInfo
- Publication number
- CN117807043A CN117807043A CN202311696740.9A CN202311696740A CN117807043A CN 117807043 A CN117807043 A CN 117807043A CN 202311696740 A CN202311696740 A CN 202311696740A CN 117807043 A CN117807043 A CN 117807043A
- Authority
- CN
- China
- Prior art keywords
- nexus
- data
- product
- library
- synchronizing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000001360 synchronised effect Effects 0.000 claims abstract description 50
- 230000004044 response Effects 0.000 claims abstract description 12
- 238000004590 computer program Methods 0.000 claims description 15
- 238000012216 screening Methods 0.000 claims description 7
- 238000004519 manufacturing process Methods 0.000 claims 3
- 238000012545 processing Methods 0.000 abstract description 6
- 238000013508 migration Methods 0.000 abstract description 5
- 230000005012 migration Effects 0.000 abstract description 5
- 230000002159 abnormal effect Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012856 packing Methods 0.000 description 2
- 101001134276 Homo sapiens S-methyl-5'-thioadenosine phosphorylase Proteins 0.000 description 1
- 102100022050 Protein canopy homolog 2 Human genes 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000011148 porous material Substances 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Abstract
The application relates to the technical field of data synchronization and discloses a method, a device, computer equipment and a storage medium for synchronizing a Nexus warehouse product, wherein the method comprises the steps of determining context data of a current product path by receiving a Select command; determining, in response to the List command, in a Nexus source artifacts library, artifacts data of the context data; and under the condition that a Sync command is received, synchronizing target data in the product data from a Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products. By means of the method, the target data in the Nexus source product library and the Nexus target product library are configured according to the user definition, and different processing is carried out on the target data according to different commands such as Select commands, list commands and Sync commands, so that the target data can be synchronized from the Nexus source product library to the Nexus target product library, and the problem that the Nexus private library is large in legacy data quantity, and a remote machine room network is not enabled to cause abnormal migration of the private library product data is solved.
Description
Technical Field
The present disclosure relates to the field of data synchronization technologies, and in particular, to a method, an apparatus, a computer device, and a storage medium for synchronizing a Nexus warehouse product.
Background
The Nexus private library has wide application and main functions: store company binary, proxy central warehouse, store warehouse image data, etc. Thus, the inventory of the private parts of large companies is very large over time, which can be a very tricky matter if private parts data migration is involved. Therefore, how to solve the problem that the private library product data cannot be normally migrated due to large amount of the Nexus private library legacy data and the non-local computer room network is urgent to be solved.
Disclosure of Invention
The application provides a method, a device, computer equipment and a storage medium for synchronizing a Nexus warehouse product, which are used for solving the problem that the data of the private warehouse product cannot be normally migrated due to large data quantity of a Nexus private warehouse and non-communication of a machine room network in a different place.
In a first aspect, the present application provides a method of synchronizing a Nexus warehouse article, the method comprising:
receiving a Select command through a synchronous program request control layer, and determining context data of a current product path;
determining the product data of the context data in a Nexus source product library through the synchronous program request control layer in response to a List command;
and under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products.
Further, in response to the List command, before determining the artifact data of the context data in the Nexus source artifact library by the synchronization program request control layer further comprises:
detecting whether the current product path is a real effective path;
and under the condition that the current product path is the real effective path, enumerating all product data in the current product path, and screening all product data to remove useless product data in all product data.
Further, before detecting whether the current product path is a true valid path, the method further comprises:
and configuring a corresponding account number and password based on the List command.
Further, after detecting whether the current product path is a true valid path, the method includes:
in case the current product path is not the true valid path, and/or
And sending a back command to return to a preset path under the condition that the target data does not exist in the current product path.
Further, the preset path includes a root directory or a higher-level directory.
Further, under the condition that the Sync program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing synchronization of Nexus warehouse products, including:
converting the target data into source product data corresponding to a Nexus OpenAPI interface based on the Sync command;
synchronizing the source artifact data from the Nexus source artifact library to a Nexus target artifact library.
Further, the Nexus source product library and the Nexus target product library are connected through a 4A springboard machine.
In a second aspect, the present application also provides a synchronizing device for a Nexus warehouse article, the device comprising:
the context data determining module is used for receiving the Select command through the synchronous program request control layer and determining the context data of the current product path;
the product data determining module is used for responding to the List command, requesting a control layer to determine product data of the context data in a Nexus source product library through the synchronous program;
and the synchronization module is used for synchronizing the target data in the product data from the Nexus source product library to the Nexus target product library under the condition that the synchronization program request control layer receives a Sync command, so as to complete the synchronization of the Nexus warehouse products.
In a third aspect, the present application also provides a computer device comprising a memory and a processor; the memory is used for storing a computer program; the processor is configured to execute the computer program and implement the method for synchronizing the Nexus warehouse product as described above when the computer program is executed.
In a fourth aspect, the present application also provides a computer readable storage medium storing a computer program which, when executed by a processor, causes the processor to implement a method of synchronizing a Nexus warehouse article as described above.
The application discloses a method, a device, computer equipment and a storage medium for synchronizing a Nexus warehouse product, wherein the method for synchronizing the Nexus warehouse product comprises the steps of receiving a Select command through a synchronous program request control layer and determining context data of a current product path; determining the product data of the context data in a Nexus source product library through the synchronous program request control layer in response to a List command; and under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products. By means of the method, the target data in the Nexus source product library and the Nexus target product library are configured according to the user definition, and different processing is carried out on the target data according to different commands such as Select commands, list commands and Sync commands, so that the target data can be synchronized from the Nexus source product library to the Nexus target product library, and the problem that the Nexus private library is large in legacy data quantity, and a remote machine room network is not enabled to cause abnormal migration of the private library product data is solved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a method of synchronizing Nexus warehouse articles provided in a first embodiment of the present application;
FIG. 2 is a schematic flow chart of a method of synchronizing Nexus warehouse articles provided in a second embodiment of the present application;
FIG. 3 is a schematic block diagram of a synchronizing device for Nexus warehouse articles provided in an embodiment of the present application;
fig. 4 is a schematic block diagram of a computer device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The flow diagrams depicted in the figures are merely illustrative and not necessarily all of the elements and operations/steps are included or performed in the order described. For example, some operations/steps may be further divided, combined, or partially combined, so that the order of actual execution may be changed according to actual situations.
It is to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
The embodiment of the application provides a method, a device, computer equipment and a storage medium for synchronizing Nexus warehouse products. The method for synchronizing the Nexus warehouse products can be applied to a server, target data in a Nexus source product library and a Nexus target product library are configured according to user definition, and the target data are processed differently according to different commands such as a Select command, a List command and a Sync command, so that the target data are synchronized from the Nexus source product library to the Nexus target product library, and the problem that the private library product data cannot be normally migrated due to large legacy data quantity of a Nexus private library and incapacity of a machine room network in different places is solved. The server may be an independent server or a server cluster.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
Referring to fig. 1, fig. 1 is a schematic flow chart of a method for synchronizing Nexus warehouse products according to a first embodiment of the present application. The method for synchronizing the Nexus warehouse products can be applied to a server, target data in a Nexus source product library and a Nexus target product library are configured according to user definition, and the target data are processed differently according to different commands such as Select commands, list commands and Sync commands, so that the target data are synchronized from the Nexus source product library to the Nexus target product library, and the problem that the private library product data cannot be normally migrated due to large amount of legacy data of the Nexus private library and the situation that a remote computer room network is not enabled is solved.
As shown in fig. 1, the synchronization method of the Nexus warehouse product specifically includes steps S10 to S30.
Step S10, a control layer receives a Select command through a synchronous program request, and the context data of the current product path is determined;
in one embodiment, the Select command is context data used to determine the current artifact path, and is used to tell the user about the starting path of the synchronized data, so that the user can perform the next operation, such as Select com/ctg/defaps, in the sense that: the current path selected by the user is $ { resource.url }/com/ctg/vops, and the subsequent user inquiry and synchronous data are all under the path; the largest function of the command is to determine a synchronous path, reduce the data volume of synchronous products, meet the synchronous requirement according to the requirement, and be an original command of MSAP products, and specially solve the problem of MAVEN warehouse product synchronization.
Step S20, responding to a List command, and requesting a control layer to determine the product data of the context data in a Nexus source product library through the synchronous program;
in one embodiment, the List command is used to enumerate subdirectory or product data under the currently selected directory, for example, list, and when the List command is executed, it needs to ensure that the current path is truly valid first, and then the corresponding List data is acquired through the Nexus openapi to return; if the account number and password are needed, the corresponding warehouse account number and password are needed to be configured in the device; the largest function of the command is to enumerate which product data are in the current directory, and further filter the data which the user needs to synchronize.
And step S30, under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of Nexus warehouse products.
In one embodiment, the Sync command is used to synchronize the artifacts, by which a particular artifact in the NexusB source repository can be synchronized to the target artifact repository NexusA; comprises the following steps: -Dfolder, -Dfile, -DgroupId, -DartifactId, -Dversion, -Dpackaging, -DpomFile, e.g. Sync-Dfolder = org/apache; the use of Dfolder for synchronizing the entire directory and Dfile for synchronizing specific products, together with the use of five entries-DgroupID, -Dartificid, -Dversion, -Dpackaging, -DposFile, cannot be used simultaneously. The command is the key of synchronizing the product, the operation command of the user is converted into data required by a corresponding Nexus openapi interface, and the source product library data is uploaded to a target product library to complete a corresponding synchronization flow; the command is a synchronous product key command, is the autonomous realization capability, is not influenced by other MAVEN private library versions, and is flexible, simple and compatible with MAVEN native commands.
The embodiment discloses a method, a device, a computer device and a storage medium for synchronizing a Nexus warehouse product, wherein the method for synchronizing the Nexus warehouse product comprises the steps of receiving a Select command through a synchronous program request control layer and determining context data of a current product path; determining the product data of the context data in a Nexus source product library through the synchronous program request control layer in response to a List command; and under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products. By means of the method, the target data in the Nexus source product library and the Nexus target product library are configured according to the user definition, and different processing is carried out on the target data according to different commands such as Select commands, list commands and Sync commands, so that the target data can be synchronized from the Nexus source product library to the Nexus target product library, and the problem that the Nexus private library is large in legacy data quantity, and a remote machine room network is not enabled to cause abnormal migration of the private library product data is solved.
Referring to fig. 2, fig. 2 is a schematic flowchart of a method for synchronizing Nexus warehouse products according to a second embodiment of the present application. The method for synchronizing the Nexus warehouse products can be applied to a server, target data in a Nexus source product library and a Nexus target product library are configured according to user definition, and the target data are processed differently according to different commands such as Select commands, list commands and Sync commands, so that the target data are synchronized from the Nexus source product library to the Nexus target product library, and the problem that the private library product data cannot be normally migrated due to large amount of legacy data of the Nexus private library and the situation that a remote computer room network is not enabled is solved.
Based on the embodiment shown in fig. 1, in this embodiment, as shown in fig. 2, step S20 is preceded by steps S11 to S12.
Step S11, detecting whether the current product path is a real effective path;
and step S12, when the current product path is the real effective path, enumerating all product data in the current product path, and screening all product data to remove useless product data in all product data.
In one embodiment, take the example of a synchronous folder com/ctg/itrdc/cache, its synchronous command is:
| Sync-Dfolder＝com/ctg/itrdc/cache |
the synchronous folder firstly confirms that the product data exists in the current user Select com/ctg/itrdc/cache path, namely, the product data is queried by utilizing a/v 1/search interface, if yes, the product data is returned to the user, if no, the product data is empty, and the synchronous folder needs to be shielded for shielding some check files such as md5 and sha1 files, so that the synchronous workload is reduced.
Considering that the number of manufactured files may be relatively large, or that there is a single large file, the following four techniques are used:
1. pre-reading the stream size of the network file stream;
2. reading network file stream data in segments;
3. merging the files;
java multithreading.
The file size is pre-read according to the value of the return response message header field Content-Length. The method is convenient to use for judging whether the file needs to be cut, and if the product exceeds 512m, the reading of the product by a single file stream is very time-consuming;
the streaming data is read in sections, the source product data is obtained in an accelerated mode by using a similar random access file, and the source product data is written into a tmp file, so that the synchronization speed is improved;
merging the files, merging the segmented tmp files into a source file, checking the correctness of the merged files, and facilitating the next uploading flow;
java multithreading is used for reading network file stream data in a segmented mode, uploading multi-product data, accelerating synchronous flow and reducing waiting time of users.
The embodiment discloses a method, a device, a computer device and a storage medium for synchronizing a Nexus warehouse product, wherein the method for synchronizing the Nexus warehouse product comprises the steps of receiving a Select command through a synchronous program request control layer and determining context data of a current product path; detecting whether the current product path is a real effective path; when the current product path is the real effective path, enumerating all product data in the current product path, screening all product data, and removing useless product data in all product data; determining the product data of the context data in a Nexus source product library through the synchronous program request control layer in response to a List command; and under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products. By means of the method, the target data in the Nexus source product library and the Nexus target product library are configured according to the user definition, and different processing is carried out on the target data according to different commands such as Select commands, list commands and Sync commands, so that the target data can be synchronized from the Nexus source product library to the Nexus target product library, and the problem that the Nexus private library is large in legacy data quantity, and a remote machine room network is not enabled to cause abnormal migration of the private library product data is solved.
Based on the embodiment shown in fig. 2, before step S12, the method further includes:
and configuring a corresponding account number and password based on the List command.
Based on the embodiment shown in fig. 2, before step S11, the method includes:
in case the current product path is not the true valid path, and/or
And sending a back command to return to a preset path under the condition that the target data does not exist in the current product path.
In one embodiment, the restore command is used to return to the specified directory, and when the command is used, the validity of the target path is checked, for example, restore. The largest function of the command is to return to the corresponding target path when no product is needed under the current path issued by the user.
Based on the above embodiments, in one embodiment, the preset path includes a root directory or a previous layer directory.
Based on the embodiment shown in fig. 1, in this embodiment, step S30 includes:
converting the target data into source product data corresponding to a Nexus OpenAPI interface based on the Sync command;
synchronizing the source artifact data from the Nexus source artifact library to a Nexus target artifact library.
Based on any of the above embodiments, in this embodiment, the Nexus source product library and the Nexus target product library are connected by a 4A springboard machine.
In one embodiment, engineering application properties configuration samples such as the following
The Nexus OpenApi is referred to as follows,
taking the synchronous ctg-cache-ncline-2.8.2. Jar product as an example, its maven dependence is as follows:
the synchronization command is as follows:
-two parameters of dpacking, -DpomFile are optional parameters, the default value of packing is jar, if of war type, -dpacking=war; the pomFile is a synchronous Maven pom file, and if synchronization is needed, this parameter needs to be added, for example: dpomFile = ctg-cache-nclient-2.8.2. Pore.
The embodiment supports on-demand synchronization, avoids total synchronization time consumption, has more redundant data and serious disc waste, and supports the functions of synchronizing according to folders and according to single files at present;
the synchronization speed is high, the multi-thread is utilized to rapidly read stream data aiming at a single cut file stream of a large file, then the file correctness is checked by a merging technology, and finally a plurality of product data are synchronized to a target product library by utilizing the multi-thread;
the expansibility is high, firstly, the company self-researches, and the customization requirement of users is supported; secondly, although only Maven products are developed and supported at present, the Nexus openapi also supports uploading of other mainstream products such as docker, npm and the like, and can support product type synchronization required by a plurality of users only by developing according to the specifications of the products;
the method is simple and flexible in deployment and operation, few in hardware resources are used, the method is built based on the Springboot scaffold frame, and the development, compiling and packing are very simple;
in the prior art or tools on the market, nexus is taken as an example, firstly, quantitative synchronization is not supported, and only full-quantity synchronization is realized; and secondly, nexus3 can be directly copied to the target product library, but the storage structure is encrypted, not the traditional folder and file structure, and if metadata of the source product library is not available, the metadata cannot be normally analyzed, which is equivalent to wasting storage space and doing idle work. The invention aims to solve the two problems, and considers that most of file data of private libraries are mainly public packages and private products are limited, because only the file data of the private products are needed to be synchronized under most conditions, the synchronous working content is greatly reduced, and the process of synchronizing the product data is quickened.
Referring to fig. 3, fig. 3 is a schematic block diagram of a synchronizing device for a Nexus warehouse product, which is configured to perform the foregoing method for synchronizing a Nexus warehouse product according to an embodiment of the present application. Wherein, the synchronization device of the Nexus warehouse product can be configured on a server.
As shown in fig. 3, the synchronizing device for the Nexus warehouse product comprises:
a context data determining module 410, configured to determine context data of a current product path by receiving a Select command by the synchronization program request control layer;
a artifact data determining module 420, configured to request, by the synchronization program, a control layer to determine, in a Nexus source artifact library, an artifact data of the context data in response to a List command;
and the synchronization module 430 is configured to synchronize target data in the artifact data from the Nexus source artifact library to a Nexus target artifact library to complete synchronization of Nexus warehouse artifacts when the Sync program request control layer receives a Sync command.
Further, the synchronizing device of the Nexus warehouse product further comprises:
the real effective path detection module is used for detecting whether the current product path is a real effective path or not;
and the product data screening module is used for enumerating all product data in the current product path and screening all product data to remove useless product data in all product data under the condition that the current product path is the real effective path.
Further, the synchronizing device of the Nexus warehouse product further comprises:
and the account number and password configuration module is used for configuring the corresponding account number and password based on the List command.
Further, the synchronizing device of the Nexus warehouse product further comprises:
a Reback command back module for, in the event that the current product path is not the true valid path, and/or
And sending a back command to return to a preset path under the condition that the target data does not exist in the current product path.
Further, the synchronization module 430 includes:
the source product data conversion unit is used for converting the target data into source product data corresponding to a Nexus OpenAPI interface based on the Sync command;
and the source product data synchronizing unit is used for synchronizing the source product data from the Nexus source product library to a Nexus target product library.
It should be noted that, for convenience and brevity of description, the specific working process of the apparatus and each module described above may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The apparatus described above may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 4.
Referring to fig. 4, fig. 4 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device may be a server.
With reference to FIG. 4, the computer device includes a processor, memory, and a network interface connected by a system bus, where the memory may include a non-volatile storage medium and an internal memory.
The non-volatile storage medium may store an operating system and a computer program. The computer program comprises program instructions that, when executed, cause the processor to perform any of the methods of synchronizing a Nexus warehouse article.
The processor is used to provide computing and control capabilities to support the operation of the entire computer device.
The internal memory provides an environment for the execution of a computer program in a non-volatile storage medium that, when executed by the processor, causes the processor to perform any of the methods of synchronizing the Nexus warehouse artifacts.
The network interface is used for network communication such as transmitting assigned tasks and the like. Those skilled in the art will appreciate that the structures shown in FIG. 4 are block diagrams only and do not constitute a limitation of the computer device on which the present aspects apply, and that a particular computer device may include more or less components than those shown, or may combine some of the components, or have a different arrangement of components.
It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Wherein in one embodiment the processor is configured to run a computer program stored in the memory to implement the steps of:
receiving a Select command through a synchronous program request control layer, and determining context data of a current product path;
determining the product data of the context data in a Nexus source product library through the synchronous program request control layer in response to a List command;
and under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products.
In one embodiment, in response to the List command, the request control layer, via the synchronization program, is further configured to implement, prior to determining the artifact data of the context data in the Nexus source artifact library:
detecting whether the current product path is a real effective path;
and under the condition that the current product path is the real effective path, enumerating all product data in the current product path, and screening all product data to remove useless product data in all product data.
In one embodiment, before detecting whether the current product path is a true valid path, it is further configured to implement:
and configuring a corresponding account number and password based on the List command.
In one embodiment, after detecting whether the current article path is a true valid path, it is used to implement:
in case the current product path is not the true valid path, and/or
And sending a back command to return to a preset path under the condition that the target data does not exist in the current product path.
In one embodiment, in the case that the Sync program request control layer receives a Sync command, synchronizing target data in the artifact data from the Nexus source artifact library to a Nexus target artifact library, to complete synchronization of Nexus warehouse artifacts, for implementing:
converting the target data into source product data corresponding to a Nexus OpenAPI interface based on the Sync command;
synchronizing the source artifact data from the Nexus source artifact library to a Nexus target artifact library.
Embodiments of the present application further provide a computer readable storage medium, where the computer readable storage medium stores a computer program, where the computer program includes program instructions, and the processor executes the program instructions to implement a method for synchronizing a Nexus warehouse product according to any one of the embodiments of the present application.
The computer readable storage medium may be an internal storage unit of the computer device according to the foregoing embodiment, for example, a hard disk or a memory of the computer device. The computer readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the computer device.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of synchronizing a Nexus warehouse article, comprising:
receiving a Select command through a synchronous program request control layer, and determining context data of a current product path;
determining the product data of the context data in a Nexus source product library through the synchronous program request control layer in response to a List command;
and under the condition that the synchronous program request control layer receives a Sync command, synchronizing target data in the product data from the Nexus source product library to a Nexus target product library, and completing the synchronization of the Nexus warehouse products.
2. The method of claim 1, wherein said requesting, by said synchronization program, a control layer in response to a List command, prior to determining the artifact data of said context data in a Nexus source artifact library, further comprises:
detecting whether the current product path is a real effective path;
and under the condition that the current product path is the real effective path, enumerating all product data in the current product path, and screening all product data to remove useless product data in all product data.
3. The method of synchronizing Nexus warehouse artifacts of claim 2 wherein the detecting if the current artifact path is a true valid path is preceded by:
and configuring a corresponding account number and password based on the List command.
4. The method of synchronizing Nexus warehouse artifacts of claim 2 wherein the detecting if the current artifact path is a true valid path is followed by:
in case the current product path is not the true valid path, and/or
And sending a back command to return to a preset path under the condition that the target data does not exist in the current product path.
5. The method of claim 4, wherein the predetermined path includes a root directory or a top directory.
6. The method for synchronizing a Nexus warehouse artifact according to claim 1, wherein synchronizing target data in the artifact data from the Nexus source artifact library to a Nexus target artifact library if the Sync command is received by the Sync program request control layer, comprises:
converting the target data into source product data corresponding to a Nexus OpenAPI interface based on the Sync command;
synchronizing the source artifact data from the Nexus source artifact library to a Nexus target artifact library.
7. A method of synchronizing the production of a Nexus warehouse article according to any one of claims 1 to 6 wherein the Nexus source production library and the Nexus destination production library are connected by a 4A springboard machine.
8. A synchronizing device for a Nexus warehouse article, comprising:
the context data determining module is used for receiving the Select command through the synchronous program request control layer and determining the context data of the current product path;
the product data determining module is used for responding to the List command, requesting a control layer to determine product data of the context data in a Nexus source product library through the synchronous program;
and the synchronization module is used for synchronizing the target data in the product data from the Nexus source product library to the Nexus target product library under the condition that the synchronization program request control layer receives a Sync command, so as to complete the synchronization of the Nexus warehouse products.
9. A computer device, the computer device comprising a memory and a processor;
the memory is used for storing a computer program;
the processor for executing the computer program and for implementing the method of synchronizing a Nexus warehouse article as claimed in any one of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, characterized in that it stores a computer program, which when executed by a processor causes the processor to implement the method of synchronizing a Nexus warehouse article as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311696740.9A CN117807043A (en) | 2023-12-11 | 2023-12-11 | Method, device, computer equipment and storage medium for synchronizing Nexus warehouse products |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311696740.9A CN117807043A (en) | 2023-12-11 | 2023-12-11 | Method, device, computer equipment and storage medium for synchronizing Nexus warehouse products |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117807043A true CN117807043A (en) | 2024-04-02 |
Family
ID=90422732
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311696740.9A Pending CN117807043A (en) | 2023-12-11 | 2023-12-11 | Method, device, computer equipment and storage medium for synchronizing Nexus warehouse products |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117807043A (en) |
-
2023
- 2023-12-11 CN CN202311696740.9A patent/CN117807043A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11740891B2 (en) | Providing access to a hybrid application offline | |
| US8812451B2 (en) | Programming model for synchronizing browser caches across devices and web services | |
| US11093221B1 (en) | Automatic containerization of operating system distributions | |
| CN107291750B (en) | Data migration method and device | |
| US8126859B2 (en) | Updating a local version of a file based on a rule | |
| CN110895484A (en) | Task scheduling method and device | |
| CN111324606B (en) | Data slicing method and device | |
| CN109032796B (en) | Data processing method and device | |
| WO2018031351A1 (en) | Discovery of calling application for control of file hydration behavior | |
| CN110895483A (en) | Task recovery method and device | |
| CN110895487A (en) | Distributed task scheduling system | |
| CN113343312A (en) | Page tamper-proofing method and system based on front-end point burying technology | |
| CN115080114B (en) | Application program transplanting processing method, device and medium | |
| CN117807043A (en) | Method, device, computer equipment and storage medium for synchronizing Nexus warehouse products | |
| US10599740B1 (en) | Program code streaming | |
| US20170091253A1 (en) | Interrupted synchronization detection and recovery | |
| CN113407629A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| US11017032B1 (en) | Document recovery utilizing serialized data | |
| CN115421785B (en) | Method, device and medium for transplanting application program | |
| US10185759B2 (en) | Distinguishing event type | |
| CN115454827B (en) | Compatibility detection method, system, equipment and medium | |
| US20240127148A1 (en) | Delta based task analysis for ci systems | |
| CN118012577A (en) | Task scheduling method and device, computing device, storage medium and program product | |
| CN117785603A (en) | Data service arrangement method and device, nonvolatile storage medium and electronic equipment | |
| CN117931764A (en) | Method, device and system for providing distributed file storage service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |