Advanced packaging techniques for improving work flows

Patent metadata

Field	Value
Publication number	US-10740093-B2
Application number	US-201615254866-A
Country	US
Kind code	B2
Filing date	Sep 1, 2016
Priority date	Sep 1, 2016
Publication date	Aug 11, 2020
Grant date	Aug 11, 2020

Abstract

Source code of a logical segment of a codebase can be isolated from other portions of the codebase yet the logical segment and the other portions may have mutual dependencies. Packaging multiple versions of the logical segment and the other portions of the codebase to be compilable as a single binary file can simplify the development, testing, and release work flows of the codebase. For example, development, evaluation, and deployment of the logical segment and the other portions of the code base can run on different schedules. As another example, a provider of the codebase can control which version of the logical segment computing devices execute.

First claim

What is claimed is:

1. A computer-implemented method comprising:
receiving source code for a first version of a first logical segment of a codebase and a second version of the first logical segment, the first logical segment having a first dependency on a second logical segment of the codebase, the second logical segment having a second dependency on the first logical segment;
generating a first package including the source code for the first version of the first logical segment and the second version of the first logical segment, wherein compilation of the package generates an executable file including a first execution path that corresponds to the first version of the first logical segment and a second execution path that corresponds to the second version of the first logical segment;
providing the generated first package to a user account;

selecting the first execution path during a first period of time distinct from a second period of time;
causing, when the first execution path is selected, the first execution path to be executed during the first period of time that a first computing device executes the executable file;
selecting the second execution path during the second period of time; and
causing, when the second execution path is selected, the second execution path to be executed during the second period of time that the first computing device executes the executable file, wherein the causing the first execution path to be selected during the first period of time and the causing the second execution path to be selected during the second period of time includes sending a command to the user account identifying the execution path to be selected.

2. The computer-implemented method of claim 1 , further comprising:
receiving user account information associated with the first computing device; and
causing the first execution path to be executed by the first computing device based at least in part on the user account information.

3. The computer-implemented method of claim 1 , further comprising:
determining an execution path per network session.

4. The computer-implemented method of claim 1 , further comprising:
updating configuration data specifying that the first package includes the source code of the first version of the first logical segment of the codebase and the second version of the first logical segment,
wherein the first package is generated based at least in part on the configuration data.

5. The computer-implemented method of claim 1 , further comprising:
providing the first package including the executable file to a first user account group; and
providing a second package that includes second source code of a third version of the first logical segment of the codebase to a second user account group.

6. The computer-implemented method of claim 1 , further comprising:
receiving user account information associated with the first computing device; and
determining that the first package includes the source code for the first version of the first logical segment of the codebase and the second version of the first logical segment based at least in part on the user account information.

7. The computer-implemented method of claim 1 , further comprising:
creating a first sub-repository in a repository storing the codebase;
receiving first source code for the first version of the first logical segment of the codebase to the first sub-repository;
creating a second sub-repository in the repository; and
receiving second source code for the second version of the first logical segment to the second sub-repository.

8. The computer-implemented method of claim 1 , wherein a type of a data object corresponding to the first execution path is determined at run time.

9. The computer-implemented method of claim 1 , wherein the codebase corresponds to a client application of a content management system, and the first logical segment of the codebase corresponds to a client-side synchronization functionality.

10. The computer-implemented method of claim 9 , further comprising:
receiving from the first computing device a first synchronization request during the first period of time;
sending to the first computing device a first synchronization response that includes first data for executing the first execution path during the first period of time;
receiving from the first computing device a second synchronization request during the second period of time; and
sending to the first computing device a second synchronization response that includes second data for executing the second execution path during the second period of time.

11. The computer-implemented method of claim 9 , further comprising:
determining an execution path per synchronization request.

12. The computer-implemented method of claim 1 , further comprising: applying a conditional logic to determine whether to select the first execution path or the second execution path.

13. A computer-implemented method, comprising:
executing an executable file compiled from a package including source code for a first version of a first logical segment of a codebase and a second version of the first logical segment, the first logical segment having a first dependency on a second logical segment of the codebase, the second logical segment having a second dependency on the first logical segment, the executable file including a first execution path that corresponds to the first version of the first logical segment and a second execution path that corresponds to the second version of the first logical segment;
instantiating the first execution path during a first period of time distinct from a second period of time;
executing the first execution path during the first period of time that the executable file is executed when the first execution path is instantiated;
instantiating the second execution path during the second period of time; and
executing the second execution path during the second period of time that the executable file is executed when the second execution path is instantiated,
wherein the first logical segment offers a functionality and the first and second versions of the first logical segment are release branches used to test which version of the first logical segment that offers the functionality is preferred.

14. The computer-implemented method of claim 13 , further comprising:
sending a first synchronization request to a content management system during the first period of time;
receiving a first synchronization response that includes first data for executing the first execution path during the first period of time;
sending a second synchronization request to the content management system during the second period of time; and
receiving a second synchronization response that includes second data for executing the second execution path during the second period of time.

15. The computer-implemented method of claim 14 , further comprising:
sending, in the first synchronization request, first information that includes a first characteristic of a first computing device, wherein the first synchronization response includes the first data for executing the first execution path based at least in part on the first characteristic; and
sending, in the second synchronization request, second information that includes a second characteristic of a second computing device, wherein the second synchronization response includes the second data for executing the second execution path based at least in part on the second characteristic.

16. The computer-implemented method of claim 15 , further comprising:

Assignees

• Dropbox Inc

Inventors

• Lai John
• Kaplan Joshua
• Jayakar Sujay
• Ross Bryon

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title