Version synchronization method and device of cross-version control system

Abstract

The invention discloses a version synchronization method and device for a cross-version control system, and relates to the field of big data, and the method comprises the steps: pulling a latest full file from a Git server; comparing the submitted version number of the current Git with the submitted version number corresponding to the last synchronization, and generating an incremental change file list; creating a temporary view in a ClarCase server, and loading a latest full-volume file; calculating MD5 feature values of all files in the current ClarCase version library, and comparing the feature values obtained through current calculation with feature values obtained through calculation after previous ClarCase synchronization is completed; if yes, uploading the files related to newly added and modified files in the incremental change file list to a ClarCase server; and detecting the incremental change file into a target stream of a ClarCase version library according to the difference type. According to the invention, the version synchronization of the cross-version control system can be efficiently and accurately realized.

Description

technical field [0001] The invention relates to the technical field of big data, in particular to a method and device for synchronizing versions across version control systems. Background technique [0002] This section is intended to provide a background or context to embodiments of the invention that are recited in the claims. The descriptions herein are not admitted to be prior art by inclusion in this section. [0003] In some traditional software development companies, ClearCase is usually used as the main version control system. With the popularity of Git, some project teams gradually began to use Git as a version control system. For compliance or multiple backup of assets, it is often necessary to synchronize the files uploaded by developers to the Git server to the ClearCase server. The existing synchronization scheme and its existing problems are as follows: [0004] Solution 1 of the prior art: through manual operation, compare the difference between the Git ve...

AI Technical Summary

Problems solved by technology

[0006] If the manual synchronization operation in the prior art solution 1 is adopted, the operation efficiency is low, the time-consuming is long, the synchronization frequency is not very high, and there is a possibility of manual operation errors

[0007] If the file in the Git repository and the file in the ClearCase repository are compared one by one in the prior art solution 2 and then operated, if a large number of files are stored in the repository, the time for each comparison will be very long and the efficiency is very low , are also not suitable for high frequency synchronous operation

Images