Synchronization of program code between revision management applications utilizing different version-control architectures

• US 9,336,228 B2
• Filed: 12/18/2013
• Issued: 05/10/2016
• Est. Priority Date: 12/18/2013
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Nguyen, Sinh V, Murali-Venkataraman, Rahul, Ramakrishnan, Ramesh Babu
• Primary Examiner(s): Cao, Phuong Thao
• Application Number:
  US14/132,418
• Publication Number:
  US 20150169614A1
• Time in Patent Office: 874 Days
• Field of Search: 707/634
• US Class Current: 1/1
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A device may receive a request to synchronize a first set of document revisions with a second set of document revisions. The first set of document revisions may be associated with a first format readable by a first application utilizing a stream architecture. The second set of document revisions may be associated with a second format readable by a second application utilizing a branch architecture. The device may determine synchronization configuration information, and may compare the first set of document revisions with the second set of document revisions based on the synchronization configuration information. The device may selectively modify one or more files based on comparing the first set of document revisions and the second set of document revisions. The device may provide information associated with selectively modifying the one or more files.

Claims

1. A device, comprising:

one or more hardware processors to;

receive a request to synchronize a first set of document revisions and a second set of document revisions,

the first set of document revisions being associated with a first format readable by a first application utilizing a stream architecture,

the second set of document revisions being associated with a second format readable by a second application utilizing a branch architecture;

determine synchronization configuration information associated with comparing the first set of document revisions and the second set of document revisions;

compare the first set of document revisions and the second set of document revisions based on the synchronization configuration information;

check out at least one parent directory, to deny access to information associated with the at least one parent directory, associated with one or more files associated with the first set of document revisions or the second set of document revisions based on comparing the first set of document revisions and the second set of document revisions;

selectively modify the one or more files associated with the first set of document revisions or the second set of document revisions based on comparing the first set of document revisions and the second set of document revisions;

store an indication of the at least one parent directory; and

provide information associated with checking in the at least one parent directory, to permit access to the information associated with the at least one parent directory, based on the stored indication of the at least one parent directory.

2. The device of claim 1, wherein the one or more hardware processors, when comparing the first set of document revisions and the second set of document revisions, are to:

determine that a directory process, associated with the first set of document revisions, does not correspond to another directory process associated with the second set of document revisions; and

wherein the one or more hardware processors are further to;

create a new directory based on the directory process associated with the first set of document revisions,

the new directory being associated with the second format; and

merge the new directory with the second set of document revisions.

3. The device of claim 1, wherein the one or more hardware processors, when comparing the first set of document revisions and the second set of document revisions, are to:

determine that a file process, associated with the first set of document revisions, does not correspond to another file process associated with the second set of document revisions; and

wherein the one or more hardware processors are further to;

create a new file based on the file process associated with the first set of document revisions,

the new file being associated with the second format; and

merge the new file with the second set of document revisions.

4. The device of claim 1, wherein the one or more hardware processors, when comparing the first set of document revisions and the second set of document revisions, are to:

determine that a first file process, associated with the first set of document revisions, corresponds to a second file process associated with the second set of document revisions;

perform a comparison of the first file process and the second file process; and

wherein the one or more hardware processors are further to;

selectively modify the one or more files for the second file process based on performing the comparison of the first file process and the second file process.

5. The device of claim 1, wherein the one or more hardware processors are further to:

identify a file structure associated with the first set of document revisions, the file structure including one or more directories; and

wherein the one or more hardware processors, when comparing the first set of document revisions and the second set of document revisions, are to;

recursively traverse the file structure associated with the first set of document revisions; and

compare the first set of document revisions and the second set of document revisions based on recursively traversing the file structure associated with the first set of document revisions.

6. The device of claim 1, wherein the one or more hardware processors, when determining the synchronization configuration information, are to:

determine a file extension filter based on the synchronization configuration information;

identify a particular file, associated with the first set of document revisions, that includes a file extension corresponding to the file extension filter; and

remove the particular file from the first set of document revisions that are to be synchronized with the second set of document revisions.

7. The device of claim 1, wherein the one or more hardware processors, when comparing the first set of document revisions and the second set of document revisions, are to:

determine that a file process or a directory process, associated with the first set of document revisions, is absent for the second set of document revisions; and

wherein the one or more hardware processors are further to;

create a new file or a new directory based on the file process or the directory process associated with the first set of document revisions,

the new file or the new directory being associated with the second format; and

promote the new file or the new directory to the second set of document revisions.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors, cause the one or more processors to;

receive a request to synchronize a first set of document revisions and a second set of document revisions,

the first set of document revisions being associated with a first format readable by a first application utilizing a branch architecture,

the second set of document revisions being associated with a second format readable by a second application utilizing a stream architecture;

determine synchronization configuration information associated with comparing the first set of document revisions and the second set of document revisions;

determine that a first file process, associated with the first set of document revisions, corresponds to a second file process associated with the second set of document revisions;

compare the first file process and the second file process based on determining that the first file process corresponds to the second file process;

determine that a conflict exists between the first file process and the second file process based on comparing the first file process and the second file process;

provide information identifying the conflict between the first file process and the second file process;

receive information associated with resolving the conflict between the first file process and the second file process;

selectively modify file contents associated with the first set of document revisions or the second set of document revisions based on receiving the information associated with resolving the conflict between the first file process and the second file process; and

provide information associated with selectively modifying the file contents associated with the first set of document revisions or the second set of document revisions.

9. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

determine that a directory process, associated with the first set of document revisions, is absent for the second set of document revisions; and

wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to;

create a new directory based on the directory process associated with the first set of document revisions,

the new directory being associated with the second format; and

promote the new directory to the second set of document revisions.

10. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

determine that a file process, associated with the first set of document revisions, is absent for the second set of document revisions; and

wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to;

create a new file based on the file process associated with the first set of document revisions,

the new file being associated with the second format; and

promote the new file to the second set of document revisions.

11. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

determine that the first file process corresponds to the second file process;

perform a comparison of the first file process and the second file process;

determine that the first file process conflicts with the second file process based on performing the comparison of the first file process and the second file process; and

wherein the one or more instructions, that cause the one or more processors to selectively modify the file contents associated with the first set of document revisions or the second set of document revisions, cause the one or more processors to;

selectively modify file contents for the second file process based on determining that the first file process conflicts with the second file process.

12. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions, that cause the one or more processors to provide the information associated with selectively modifying the file contents, cause the one or more processors to:

provide information associated with updating a synchronization date identifier associated with the first set of document revisions and the second set of document revisions.

13. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions, that cause the one or more processors to determine the synchronization configuration information, cause the one or more processors to:

determine a synchronization date threshold based on the synchronization configuration information;

identify a file, associated with the first set of document revisions, that includes a synchronization date identifier that satisfies the synchronization date threshold; and

remove the file from the first set of document revisions that are to be synchronized with the second set of document revisions.

14. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

determine that a file process or a directory process, associated with the first set of document revisions, does not correspond to another file process or another directory process associated with the second set of document revisions;

create a new file or a new directory based on the file process or the directory process associated with the first set of document revisions,

the new file or the new directory being associated with the second format; and

merge the new file or the new directory with the second set of document revisions.

15. A method, comprising:

receiving, by a device, a request to synchronize a first set of program code revisions and a second set of program code revisions,

the first set of program code revisions being associated with a first format readable by a first revision management application utilizing a first architecture,

the second set of program code revisions being associated with a second format readable by a second revision management application utilizing a second architecture;

determining, by the device, synchronization configuration information associated with comparing the first set of program code revisions and the second set of program code revisions;

determining, by the device, that a first file process, associated with the first set of program code revisions, corresponds to a second file process associated with the second set of program code revisions;

performing, by the device, a comparison between the first file process and the second file process based on determining that the first file process corresponds to the second file process;

selectively modifying, by the device, the second set of program code revisions based on performing the comparison between the first file process and the second file process; and

providing, by the device, information associated with selectively modifying the second set of program code revisions.

16. The method of claim 15, wherein determining the synchronization configuration information comprises:

determining a synchronization filter;

identifying a subset of the first set of program code revisions corresponding to the synchronization filter; and

removing the subset of the first set of program code revisions from the first set of program code revisions that is to be synchronized.

17. The method of claim 15, further comprising:

identifying a synchronization date identifier associated with the first set of program code revisions and the second set of program code revisions; and

wherein providing the information associated with selectively modifying the second set of program code revisions comprises;

providing information associated with updating the synchronization date identifier.

18. The method of claim 15, further comprising:

determining that a particular subset of program code revisions, included in the first set of program code revisions, does not correspond to another particular subset of program code revisions included in the second set of program code revisions; and

wherein selectively modifying the second set of program code revisions comprises;

merging the particular subset of program code revisions, included in the first set of program code revisions, with the second set of program code revisions.

19. The method of claim 15, further comprising:

determining that a first subset of program code revisions, included in the first set of program code revisions, corresponds to a second subset of program code revisions included in the second set of program code revisions; and

wherein selectively modifying the second set of program code revisions comprises;

merging the first subset of program code revisions and the second subset of program code revisions; and

wherein providing the information associated with selectively modifying the second set of program code revisions comprises;

providing the information based on merging the first subset of program code revisions and the second subset of program code revisions.

20. The method of claim 15, further comprising:

determining a conflict between a first subset of program code revisions, included in the first set of program code revisions, and a corresponding second subset of program code revisions included in the second set of program code revisions;

providing information identifying the conflict between the first subset of program code revisions and the second subset of program code revisions;

receiving information associated with resolving the conflict between the first subset of program code revisions and the second subset of program code revisions; and

wherein selectively modifying the second set of program code revisions comprises;

selectively modifying the second set of program code revisions based on receiving the information associated with resolving the conflict between the first subset of program code revisions and the second subset of program code revisions.