Distributed code repository with limited synchronization locking

• US 10,114,833 B2
• Filed: 04/19/2018
• Issued: 10/30/2018
• Est. Priority Date: 12/23/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: GitHub Incorporated (Microsoft Corporation)
• Inventors: Reynolds, Patrick, Haggerty, Michael R., King, Jeffrey
• Primary Examiner(s): Kang, Insun
• Application Number:
  US15/957,258
• Publication Number:
  US 20180246904A1
• Time in Patent Office: 194 Days
• Field of Search: None
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/49 Partial evaluation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A system for a distributed repository includes an input interface and a processor. The input interface is to receive a request to change a portion of code. The processor is to determine a change reference and an existing reference, indicate to lock one or more repositories, determine whether swapping references is approved by a vote, and in the event that swapping references is approved by a vote, swap the references and indicate to unlock the one or more repositories.

Claims

1. A system, comprising:

a hardware processor configured to;

receive a request to change an existing portion of code;

determine whether the request to change the existing portion of code is valid;

in response to determining that the request to change the existing portion of code is valid, distribute the request to a plurality of repositories, wherein the request comprises a new portion of the code;

request the plurality of repositories to approve the request to change the existing portion of code to the new portion;

receive a corresponding vote to approve swapping references from each repository of the plurality of repositories;

determine whether swapping references is approved by a majority of the plurality of repositories based on the corresponding votes; and

in response to determining that swapping references is approved by the majority of the plurality of repositories, modify the code by swapping an existing reference associated with the code that points to the existing portion with a change reference associated with the code that points to the new portion and unlock the plurality of repositories; and

a memory coupled to the hardware processor and configured to provide the hardware processor with instructions.

2. The system of claim 1, wherein the new portion of code is determined to be valid at least in part by checking the new portion of code using a checksum.

3. The system of claim 1, wherein a reference comprises a pointer.

4. The system of claim 1, wherein the new portion of code comprises a code block and associated metadata.

5. The system of claim 1, wherein the hardware processor is additionally configured to store the new portion of code.

6. The system of claim 1, wherein the hardware processor is additionally configured to provide the new portion of code to other systems.

7. The system of claim 1, wherein the hardware processor is configured to provide an indication of a ready to lock state.

8. The system of claim 1, wherein to indicate to lock the plurality of repositories, the hardware processor is further configured to indicate to lock a repository stored on the system.

9. The system of claim 1, wherein to indicate to lock the plurality of repositories, the hardware processor is further configured to indicate to lock a repository stored on another system.

10. The system of claim 1, wherein the hardware processor is further configured to:

in the event a swap indication to not swap is received but swapping references is approved, provide a repair indication to the system that provided the swap indication to not swap.

11. The system of claim 1, wherein the hardware processor is further configured to:

in the event swapping references is not approved, provide an indication that changing the existing portion of code has failed.

12. The system of claim 1, wherein the hardware processor is further configured to:

in the event swapping references is approved, provide an indication that changing the existing portion of code has completed.

13. The system of claim 1, wherein the system and one or more other systems each determine whether swapping references is approved by a vote.

14. The system of claim 1, wherein the processor is further configured to:

in the event swapping references is approved, provide an indication to one or more other systems to swap references.

15. The system of claim 1, wherein a file associated with the existing portion of code is checked for synchronization.

16. The system of claim 1, wherein one or more files associated with the existing portion of code are locked.

17. A method, comprising:

receiving a request to change an existing portion of code;

determining, using a hardware processor, whether the request to change the existing portion of code is valid;

in response to determining that the request to change the existing portion of code is valid, distributing the request to a plurality of repositories, wherein the request comprises a new portion of the code;

requesting the plurality of repositories to approve the request to change the existing portion of code to the new portion;

receiving a corresponding vote to approve swapping references from each repository of the plurality of repositories;

determining whether swapping references is approved by a majority of the plurality of repositories based on the corresponding votes; and

in response to determining that swapping references is approved by the majority of the plurality of repositories, modifying the code by swapping an existing reference associated with the code that points to the existing portion with a change reference associated with the code that points to the new portion and unlocking the plurality of repositories.

18. The method of claim 17, wherein the new portion of code is determined to be valid at least in part by checking the new portion of code using a checksum.

19. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request to change an existing portion of code;

determining, using a hardware processor, whether the request to change the existing portion of code is valid;

in response to determining that the request to change the existing portion of code is valid, distributing the request to a plurality of repositories, wherein the request comprises a new portion of the code;

requesting the plurality of repositories to approve the request to change the existing portion of code to the new portion;

receiving a corresponding vote to approve swapping references from each repository of the plurality of repositories;

determining whether swapping references is approved by a majority of the plurality of repositories based on the corresponding votes; and

in response to determining that swapping references is approved by the majority of the plurality of repositories, modifying the code by swapping an existing reference associated with the code that points to the existing portion with a change reference associated with the code that points to the new portion and unlocking the plurality of repositories.