INTEGRATING COPY DATA TOKENS WITH SOURCE CODE REPOSITORIES

• US 20170004154A1
• Filed: 07/01/2015
• Published: 01/05/2017
• Est. Priority Date: 07/01/2015
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Actifio, Inc. (Alphabet Inc.)
• Inventors: BLUMENAU, Steven M., SULLIVAN, James, MURPHY, Christopher
• Granted Patent: US 10,691,659 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Computerized systems and methods are provided for integrating copy data tokens with source code repositories. A first command associated with the version control system stores in the memory a copy of source code and a copy of the data token from the remote repository, comprising source data and mount data. A second command associated with the version control system is executed to create a version of the source code stored in the memory. Based on the execution of the second command a working copy of the copy data is created based on the data token for use with the version of the source code, comprising creating a copy of the copy data from the data source based on the source data, and mounting the working copy to the device based on the mount data, thereby automatically managing the copy data for the version control system.

Claims

1. A computerized method for integrating a data token into a version control system, the data token defining attributes for copy data associated with the data token to facilitate the automatic management of the copy data for the version control system, the computerized method comprising:

executing, by a computing device with a processor and memory, a first command associated with the version control system configured to store in the memory (a) a copy of source code associated with the source code repository from a remote repository, and (b) a copy of the data token from the remote repository, the data token defining attributes associated with copy data for use with the source code repository, the attributes comprising;

source data for the copy data indicative of a data source for the copy data; and

mount data indicative of a device to which the computing device mounts the copy data;

executing, by the computing device, a second command associated with the version control system configured to create a version of the source code stored in the memory; and

creating, by the computing device, based on the execution of the second command a working copy of the copy data based on the data token for use with the version of the source code, comprising;

creating a copy of the copy data from the data source based on the source data; and

mounting the working copy to the device based on the mount data, thereby automatically managing the copy data for the version control system.

2. The method of claim 1, wherein creating the working copy based on the execution of the second command comprises hooking into the second command, comprising:

executing a branch command to create the working copy; and

executing a checkout command to mount the working copy to the device.

3. The method of claim 1, further comprising:

executing a third command associated with the version control system configured to create a branch of the version of the source code;

determining, based on execution of a fourth command associated with the branch a second working copy of the copy data needs to be created for the branch of the version of the source code; and

creating a second working copy of the copy data based on the data token for use with the branch of the version of the source code.

4. The method of claim 3, further comprising:

determining, based on execution of a fourth command configured to create a second version of the source code stored in the memory, that the branch no longer exists in the version control system; and

deleting the second working copy.

5. The method of claim 1, wherein creating a copy of the data token from the remote repository comprises:

determining the first command is associated with a user from a first group of users of the version control system; and

storing the data token because the data token is associated with the first group of users rather than a second data token associated with the second group of users.

6. The method of claim 1, wherein:

the first command is a pull command; and

the second command is a checkout command.

7. The method of claim 1, wherein:

the attributes of the data token comprise transformation data for the copy data indicative of a set of modifications for the copy data when creating an instance of the copy data; and

creating the working copy of the copy data comprises modifying the copy of the copy data based on the transformation data to generate the working copy.

8. A computerized apparatus for integrating a data token into a version control system, the data token defining attributes for copy data associated with the data token to facilitate the automatic management of the copy data for the version control system, the apparatus comprising a processor configured to run a module stored in memory that is configured to cause the processor to:

execute a first command associated with the version control system configured to store in the memory (a) a copy of source code associated with the source code repository from a remote repository, and (b) a copy of the data token from the remote repository, the data token defining attributes associated with copy data for use with the source code repository, the attributes comprising;

source data for the copy data indicative of a data source for the copy data; and

mount data indicative of a device to which the computing device mounts the copy data;

execute a second command associated with the version control system configured to create a version of the source code stored in the memory; and

create based on the execution of the second command a working copy of the copy data based on the data token for use with the version of the source code, comprising;

creating a copy of the copy data from the data source based on the source data; and

mounting the working copy to the device based on the mount data, thereby automatically managing the copy data for the version control system.

9. The computerized apparatus of claim 8, wherein creating the working copy based on the execution of the second command comprises hooking into the second command, comprising:

executing a branch command to create the working copy; and

executing a checkout command to mount the working copy to the device.

10. The computerized apparatus of claim 8, wherein the module stored in memory is further configured to cause the processor to:

execute a third command associated with the version control system configured to create a branch of the version of the source code;

determine, based on execution of a fourth command associated with the branch a second working copy of the copy data needs to be created for the branch of the version of the source code; and

creating a second working copy of the copy data based on the data token for use with the branch of the version of the source code.

11. The computerized apparatus of claim 10, wherein the module stored in memory is further configured to cause the processor to:

determine, based on execution of a fourth command configured to create a second version of the source code stored in the memory, that the branch no longer exists in the version control system; and

delete the second working copy.

12. The computerized apparatus of claim 8, wherein creating a copy of the data token from the remote repository comprises:

determining the first command is associated with a user from a first group of users of the version control system; and

storing the data token because the data token is associated with the first group of users rather than a second data token associated with the second group of users.

13. The computerized apparatus of claim 8, wherein:

the attributes of the data token comprise transformation data for the copy data indicative of a set of modifications for the copy data when creating an instance of the copy data; and

creating the working copy of the copy data comprises modifying the copy of the copy data based on the transformation data to generate the working copy.

18. The non-transitory computer readable medium of claim 8, wherein creating a copy of the data token from the remote repository comprises:

determining the first command is associated with a user from a first group of users of the version control system; and

storing the data token because the data token is associated with the first group of users rather than a second data token associated with the second group of users.

14. A non-transitory computer readable medium having executable instructions operable to cause an apparatus to:

execute a first command associated with the version control system configured to store in the memory (a) a copy of source code associated with the source code repository from a remote repository, and (b) a copy of the data token from the remote repository, the data token defining attributes associated with copy data for use with the source code repository, the attributes comprising;

source data for the copy data indicative of a data source for the copy data; and

mount data indicative of a device to which the computing device mounts the copy data;

execute a second command associated with the version control system configured to create a version of the source code stored in the memory; and

create based on the execution of the second command a working copy of the copy data based on the data token for use with the version of the source code, comprising;

creating a copy of the copy data from the data source based on the source data; and

mounting the working copy to the device based on the mount data, thereby automatically managing the copy data for the version control system.

15. The non-transitory computer readable medium of claim 14, wherein creating the working copy based on the execution of the second command comprises hooking into the second command, comprising:

executing a branch command to create the working copy; and

executing a checkout command to mount the working copy to the device.

16. The non-transitory computer readable medium of claim 14, wherein the executable instructions are operable to cause the apparatus to:

execute a third command associated with the version control system configured to create a branch of the version of the source code;

determine, based on execution of a fourth command associated with the branch a second working copy of the copy data needs to be created for the branch of the version of the source code; and

creating a second working copy of the copy data based on the data token for use with the branch of the version of the source code.

17. The non-transitory computer readable medium of claim 16, wherein the executable instructions are operable to cause the apparatus to:

determine, based on execution of a fourth command configured to create a second version of the source code stored in the memory, that the branch no longer exists in the version control system; and

delete the second working copy.

19. The non-transitory computer readable medium of claim 14, wherein:

the attributes of the data token comprise transformation data for the copy data indicative of a set of modifications for the copy data when creating an instance of the copy data; and

creating the working copy of the copy data comprises modifying the copy of the copy data based on the transformation data to generate the working copy.