Data migration system and method for git and svn platforms

Abstract

The application discloses a data migration system and method of GIT and SVN platforms, wherein the migration backend module is connected with the GIT platform and the SVN platform respectively, the migration frontend module is connected with the migration backend module, and the migration frontend module is connected with a browser; the browser constructs a user interface based on a frontend framework; the migration frontend module sends a data migration request to the migration backend module according to a data migration operation instruction of a user based on the user interface; and the migration backend module migrates specified data of the GIT platform to the SVN platform or migrates specified data of the SVN platform to the GIT platform according to the data migration request. Through the technical scheme, data migration and synchronization can be realized without understanding operation commands and use methods of the SVN platform and the GIT platform, the maintenance cost and the learning cost of data migration and data mutual backup are reduced, regular synchronization operation can be realized, and the workload is reduced.

Description

Technical Field

[0001] This invention relates to the field of data migration technology, and in particular to a data migration system and a data migration method for the Git and SVN platforms. Background Technology

[0002] Currently, some established companies have used SVN as their data and code hosting platform for data storage and sharing. However, with the passage of time and technological advancements, SVN no longer meets the needs of most companies, and Git data hosting platforms are being increasingly accepted and adopted. For companies that have used SVN for a long time, data transfer and migration have become major issues, requiring both the integrity of the data migration and its ease of use.

[0003] However, based on existing technologies, data migration has high technical requirements, is relatively complicated to operate, and requires a large workload in the long term. It also requires high maintenance or learning costs and additional work. Summary of the Invention

[0004] To address the aforementioned issues, this invention provides a data migration system and method for Git and SVN platforms. By employing a migration backend module and a migration frontend module, data migration between Git and SVN platforms can be achieved through interactive operations via the frontend browser's user interface. Data migration and synchronization can be accomplished without needing to understand the operation commands and usage methods of SVN and Git platforms, reducing the maintenance and learning costs of data migration and data backup. Furthermore, based on this system, regular synchronization operations can be performed, further reducing workload.

[0005] To achieve the above objectives, the present invention provides a data migration system for GIT and SVN platforms, comprising: a migration backend module and a migration frontend module;

[0006] The migration backend module is connected to the Git platform and the SVN platform respectively, the migration frontend module is connected to the migration backend module, and the migration frontend module is connected to the browser;

[0007] The browser builds a user interface based on a front-end framework, and the migration front-end module sends a data migration request to the migration back-end module according to the user's data migration operation instructions based on the user interface.

[0008] The migration backend module migrates specified data from the GIT platform to the SVN platform, or migrates specified data from the SVN platform to the GIT platform, according to the data migration request.

[0009] In the above technical solution, preferably, the migration front-end module and the browser use the middleware nginx to provide proxy services, thereby enabling data interaction between the migration front-end module and the browser.

[0010] In the above technical solution, preferably, the migration backend module can also pull specified data from the GIT platform or the SVN platform to the local machine according to the data migration request, or delete specified data from the GIT platform or the SVN platform according to the data migration request.

[0011] This invention also proposes a data migration method for Git and SVN platforms, applicable to a data migration system for Git and SVN platforms as disclosed in any of the above technical solutions, comprising:

[0012] Based on the data migration operation instructions executed by the user through the browser-based user interface, the migration front-end module sends the corresponding data migration request to the migration back-end module;

[0013] The migration backend module migrates specified data from the GIT platform to the SVN platform, or migrates specified data from the SVN platform to the GIT platform, according to the data migration request.

[0014] In the above technical solution, preferably, the specific process of migrating the specified data from the GIT platform to the SVN platform includes:

[0015] Based on the GIT branch of the GIT platform input by the user and the SVN address to be migrated, the system queries whether there is a file with the same name as the file corresponding to the GIT branch in the SVN address. If it exists, the system backs up or renames the current file. If it does not exist, the system performs data migration, migrates the file corresponding to the GIT branch to the SVN address, and checks whether the file data is complete after the migration is completed.

[0016] In the above technical solution, preferably, the specific process of migrating the specified data from the SVN platform to the GIT platform includes:

[0017] Based on the SVN address and GIT address entered by the user, the GIT address and the corresponding GIT repository branch are pre-built in the GIT platform, and then the files in the SVN address are moved into the GIT repository branch corresponding to the GIT address.

[0018] In the above technical solutions, preferably, the data migration method for GIT and SVN platforms further includes:

[0019] Based on the user's input data request command, GIT address, and GIT platform account password, the data in the GIT repository branch corresponding to the GIT address is pulled to the local machine, and the integrity of the data is checked.

[0020] In the above technical solutions, preferably, the data migration method for GIT and SVN platforms further includes:

[0021] Based on the user's input data request command, SVN address, and SVN platform account password, the data corresponding to the SVN address is retrieved to the local machine, and the integrity of the data is checked.

[0022] In the above technical solutions, preferably, the data migration method for GIT and SVN platforms further includes:

[0023] Based on the user-input data deletion command, SVN address, and SVN platform account password, the system performs a deletion operation on the data corresponding to the SVN address and confirms whether the current data has been deleted normally.

[0024] In the above technical solution, preferably, according to a preset timed synchronization instruction, the specified data of the GIT platform is periodically migrated to the SVN platform, the specified data of the SVN platform is periodically migrated to the GIT platform, the specified data of the GIT platform or the SVN platform is periodically pulled to the local machine, or the data of the specified address of the SVN platform is periodically deleted.

[0025] Compared with the prior art, the beneficial effects of the present invention are as follows: by adopting a migration backend module and a migration frontend module, data migration between the GIT platform and the SVN platform can be achieved through interactive operation via the user interface of the frontend browser. Data migration and synchronization can be achieved without understanding the operation commands and usage methods of the SVN platform and the GIT platform, which reduces the maintenance cost and learning cost of data migration and data backup. Furthermore, based on this system, regular synchronization operations can be achieved, reducing the workload. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of the structure of a data migration system for the GIT and SVN platforms disclosed in one embodiment of the present invention;

[0027] Figure 2 This is a schematic diagram illustrating the full-process interaction of a data migration system on the GIT and SVN platforms disclosed in one embodiment of the present invention;

[0028] Figure 3 This is a flowchart illustrating a data migration method for the GIT and SVN platforms disclosed in one embodiment of the present invention.

[0029] In the diagram, the correspondence between the components and the reference numerals is as follows:

[0030] 1. Migrate backend modules, 2. Migrate frontend modules, 3. Git platform, 4. SVN platform, 5. Deploy middleware, 6. Browser. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0032] The present invention will now be described in further detail with reference to the accompanying drawings:

[0033] like Figure 1 and Figure 2 As shown, a data migration system for GIT and SVN platforms provided by the present invention includes: a migration backend module 1 and a migration frontend module 2;

[0034] The migration backend module 1 is connected to the GIT platform 3 and the SVN platform 4 respectively, the migration frontend module 2 is connected to the migration backend module 1, and the migration frontend module 2 is connected to the browser 6.

[0035] Browser 6 builds a user interface based on a front-end framework. The migration front-end module 2 sends a data migration request to the migration back-end module 1 based on the user's data migration operation instructions based on the user interface.

[0036] The migration backend module 1 migrates specified data from the GIT platform 3 to the SVN platform 4, or migrates specified data from the SVN platform 4 to the GIT platform 3, based on the data migration request.

[0037] In this implementation, by employing a migration backend module 1 and a migration frontend module 2, data migration between the GIT platform 3 and the SVN platform 4 can be achieved through interactive operations via the user interface of the frontend browser 6. Data migration and synchronization can be achieved without needing to understand the operation commands and usage methods of the SVN platform 4 and the GIT platform 3, reducing the maintenance and learning costs of data migration and data backup. Furthermore, based on this system, regular synchronization operations can be performed, reducing workload.

[0038] Specifically, the development of the front-end user interface greatly expands the application scope of the system. If only the back-end module 1 is migrated, synchronizing data from Git platform 3 to SVN platform 4 requires familiarity with the operation commands and usage methods of both Git platform 3 and SVN platform 4. However, with the addition of the front-end module 2, the user interface enables functions such as synchronizing data from SVN platform 4 to Git platform 3, pulling remote files from Git platform 3 to the local machine, pulling remote files from SVN platform 4 to the local machine, and deleting specified remote files from SVN platform 4. This allows users new to data hosting platforms like Git platform 3 and SVN platform 4 to migrate and synchronize data.

[0039] Among them, the migration front-end module 2 uses the Vue framework and Web Package to build the user interface, and the migration back-end module 1 uses the Spring Boot framework, with Logback as the auxiliary tool for recording operation logs, and the data uses a MySQL database.

[0040] In the above implementation, preferably, the migration front-end module 2 and the browser 6 are connected via a proxy service using the middleware nginx to enable data interaction between the migration front-end module 2 and the browser 6.

[0041] In the above embodiments, preferably, the migration backend module 1 can also pull specified data from the GIT platform 3 or SVN platform 4 to the local machine according to the data migration request, or delete specified data from the GIT platform 3 or SVN platform 4 according to the data migration request.

[0042] like Figure 2 and Figure 3 As shown, the present invention also proposes a data migration method for GIT and SVN platforms, applied to the data migration system for GIT and SVN platforms disclosed in any of the above embodiments, comprising:

[0043] Based on the data migration operation instructions executed by the user based on the user interface of Browser 6, the migration front-end module 2 sends the corresponding data migration request to the migration back-end module 1.

[0044] The migration backend module 1 migrates specified data from the GIT platform 3 to the SVN platform 4, or migrates specified data from the SVN platform 4 to the GIT platform 3, based on the data migration request.

[0045] In this implementation, by employing a migration backend module 1 and a migration frontend module 2, data migration between the GIT platform 3 and the SVN platform 4 can be achieved through interactive operations via the user interface of the frontend browser 6. Data migration and synchronization can be achieved without needing to understand the operation commands and usage methods of the SVN platform 4 and the GIT platform 3, reducing the maintenance and learning costs of data migration and data backup. Furthermore, based on this system, regular synchronization operations can be performed, reducing workload.

[0046] In the above embodiments, preferably, the specific process of migrating the specified data from the GIT platform 3 to the SVN platform 4 includes:

[0047] Based on the user-inputted Git branch (GIT platform 3) and the SVN address to be migrated, the system checks if a file with the same name as the corresponding file in the SVN address exists. If it does, the file is backed up or renamed; otherwise, it is deleted during the data migration process. If the file does not exist, the data migration is performed, moving the corresponding file from the Git branch to the SVN address. The system then checks the integrity of the migrated file data; if incomplete, the data migration operation is repeated.

[0048] In the above embodiments, preferably, the specific process of migrating the specified data from SVN platform 4 to GIT platform 3 includes:

[0049] Based on the SVN address and Git address entered by the user, the Git address and its corresponding Git repository branch are pre-built in Git Platform 3. Then, the files in the SVN address are moved into the Git repository branch corresponding to the Git address. The default master branch is preferred as the Git repository branch.

[0050] In the above embodiments, preferably, the data migration method for GIT and SVN platforms further includes:

[0051] Based on the user's input data request command, GIT address, and GIT platform 3 account password, the data in the GIT repository branch corresponding to the GIT address is pulled to the local machine, and the integrity of the data is checked.

[0052] In the above embodiments, preferably, the data migration method for GIT and SVN platforms further includes:

[0053] Based on the user's input data request command, SVN address, and SVN platform 4 account password, the data corresponding to the SVN address is pulled to the local machine, and the integrity of the data is checked.

[0054] In the above embodiments, preferably, the data migration method for GIT and SVN platforms further includes:

[0055] Based on the user-input data deletion command, SVN address, and SVN platform 4 account password, perform the deletion operation on the data corresponding to the SVN address, and confirm whether the current data has been deleted normally.

[0056] In the above embodiments, preferably, according to the preset timed synchronization instructions, the specified data of the GIT platform 3 is periodically migrated to the SVN platform 4, the specified data of the SVN platform 4 is periodically migrated to the GIT platform 3, the specified data of the GIT platform 3 or the SVN platform 4 is periodically pulled to the local machine, or the data at the specified address of the SVN platform 4 is periodically deleted.

[0057] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A data migration system for Git and SVN platforms, characterized in that, include: Migrate the backend module and migrate the frontend module; The migration backend module is connected to the Git platform and the SVN platform respectively. The migration frontend module is connected to the backend module and to the browser. The migration frontend module and the browser communicate through a proxy service using the deployed middleware nginx to achieve data interaction between the migration frontend module and the browser. The browser builds a user interface based on a front-end framework. The migration front-end module sends a data migration request to the migration back-end module according to the user's data migration operation instructions based on the user interface. The data migration request includes account password information and GIT address, SVN address and GIT branch information used to indicate the migration direction. The migration backend module migrates specified data from the GIT platform to the SVN platform, or migrates specified data from the SVN platform to the GIT platform, according to the data migration request. When the data migration request indicates that the specified data from the GIT platform be migrated to the SVN platform, the migration backend module queries the SVN address to see if there is a file with the same name as the file corresponding to the GIT branch. If it exists, the current file is backed up or renamed. If it does not exist, the data migration is performed to migrate the file corresponding to the GIT branch to the SVN address, and the integrity of the migrated file data is checked. If it is incomplete, the data migration operation is re-executed. When the data migration request indicates that the specified data from the SVN platform be migrated to the GIT platform, the migration backend module pre-builds the GIT address and the corresponding GIT repository branch in the GIT platform based on the SVN address and the GIT address, and then migrates the files in the SVN address to the GIT repository branch corresponding to the GIT address. The migration backend module also pulls the specified data from the GIT platform or the SVN platform to the local machine according to the data request instruction and checks the integrity of the data, or performs a deletion operation on the data corresponding to the SVN address according to the data deletion instruction and confirms whether the current data has been deleted normally. The migration backend module also periodically performs the following actions according to preset timed synchronization instructions: migrating specified data from the GIT platform to the SVN platform, periodically migrating specified data from the SVN platform to the GIT platform, periodically pulling specified data from the GIT platform or the SVN platform to the local machine, and periodically deleting data from a specified address on the SVN platform.

2. The data migration system for the Git and SVN platforms according to claim 1, characterized in that, The migration backend module can also pull specified data from the GIT platform or the SVN platform to the local machine according to the data migration request, or delete specified data from the GIT platform or the SVN platform according to the data migration request.

3. A data migration method for Git and SVN platforms, characterized in that, A data migration system applied to the Git and SVN platforms as described in claim 1 or 2, comprising: Based on the data migration operation instructions executed by the user through the browser-based user interface, the migration front-end module sends a corresponding data migration request to the migration back-end module; wherein, the data migration request includes at least the GIT address, SVN address and GIT branch information used to indicate the migration direction, and includes the account password information of the GIT platform or the SVN platform; The migration backend module migrates specified data from the GIT platform to the SVN platform, or migrates specified data from the SVN platform to the GIT platform, according to the data migration request. Specifically, when the data migration request instructs that specified data from the GIT platform be migrated to the SVN platform, based on the GIT branch input by the user and the SVN address to be migrated to, the system queries whether there is a file with the same name as the file corresponding to the GIT branch in the SVN address. If it exists, the system performs a backup or rename operation on the current file. If it does not exist, the system performs data migration, migrates the file corresponding to the GIT branch to the SVN address, and checks whether the file data is complete after the migration is completed. If it is incomplete, the system re-executes the data migration operation. When the data migration request indicates that the specified data of the SVN platform be migrated to the GIT platform, the GIT address and the corresponding GIT repository branch are pre-built in the GIT platform according to the SVN address and the GIT address entered by the user, and then the files in the SVN address are migrated into the GIT repository branch corresponding to the GIT address. Upon receiving a data request instruction from a user, the system retrieves the data from the GIT repository branch corresponding to the GIT address to the local machine and checks the data integrity, based on the data request instruction, the GIT address, and the account password of the GIT platform; and upon receiving a data request instruction from a user, the system retrieves the data corresponding to the SVN address to the local machine and checks the data integrity, based on the data request instruction, the SVN address, and the account password of the SVN platform. Upon receiving a data deletion instruction from the user, the system performs a deletion operation on the data corresponding to the SVN address based on the data deletion instruction, the SVN address, and the account password of the SVN platform, and confirms whether the current data has been deleted normally. According to the preset timed synchronization instructions, the system periodically performs the following operations: migrating specified data from the Git platform to the SVN platform, migrating specified data from the SVN platform to the Git platform, pulling specified data from the Git platform or the SVN platform to the local machine, and deleting data from a specified address on the SVN platform.

Images