Distributed parallel build system

• US 10,048,961 B2
• Filed: 12/14/2016
• Issued: 08/14/2018
• Est. Priority Date: 03/31/2006
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Gu, Kevin
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US15/378,613
• Publication Number:
  US 20170097821A1
• Time in Patent Office: 608 Days
• Field of Search: 717101-108, 717120-122, 717116
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

This document describes, among other things, systems and methods for managing distributed parallel builds. A computer-implemented method to manage parallel builds, comprises identifying one or more software components in a software project, wherein each software component includes an executable binary file; determining a build configuration for each software component, wherein the build configuration includes a mapping from each software component to one or more build servers; and building each software component using the mapped one or more build servers in the corresponding build configuration, wherein the building includes compiling one or more source files associated with each software component to one or more object files, by distributing the one or more source files to one or more compilation machines.

Claims

1. A system for managing software component builds, comprising:

a hardware processor;

a memory comprising instructions which, when executed by the processor, cause the system to;

access multiple files associated with a software component;

map the software component to a subset of a set of build servers based on a typical frequency of changes to the software component; and

build the software component by using each build server, of the subset of build servers, to compile one or more of the multiple files.

2. The system of claim 1, further comprising instructions which, when executed by the processor, cause the system to:

determine a level of complexity of each of the multiple files;

determine a level of power of each of the build servers;

map each of the multiple files to a build server, of the subset of build servers, by mapping one or more of the multiple files with a higher level of complexity to a build server with a higher power level; and

compile one or more of the multiple files by using each build server, of the subset of build servers, to compile the one or more files that are mapped to the build server.

3. The system of claim 1, further comprising instructions which, when executed by the processor, cause the system to schedule one or more of the builds.

4. The system of claim 3, wherein the scheduling is based on a build requester or a build request time of each of the scheduled builds.

5. The system of claim 3, wherein the scheduling is based on build type or a build size of each of the scheduled builds.

6. The system of claim 1, further comprising instructions which, when executed by the processor, cause the system to detect one or more error conditions and perform one or more actions in response to the detected error conditions.

7. The system of claim 6, wherein the actions include one or more of reporting the error condition, logging the error condition, or ignoring the error condition.

8. A method for managing software component builds, comprising:

accessing multiple files associated with a software component;

mapping the software component to a subset of a set of build servers based on a typical frequency of changes to the software component; and

building the software component by using each build server, of the subset of build servers, to compile one or more of the multiple files.

9. The method of claim 8, further comprising:

determining a level of complexity of each of the multiple files;

determining a level of power of each of the build servers;

mapping each of the multiple files to a build server, of the subset of build servers, by mapping one or more of the multiple files with a higher level of complexity to a build server with a higher power level; and

compiling one or more of the multiple files by using each build server, of the subset of build servers, to compile the one or more files that are mapped to the build server.

10. The method of claim 8, further comprising scheduling one or more of the builds.

11. The method of claim 10, wherein the scheduling is based on a build requester or a build request time of each of the scheduled builds.

12. The method of claim 10, wherein the scheduling is based on build type or a build size of each of the scheduled builds.

13. The method of claim 8, further comprising detecting one or more error conditions and perform one or more actions in response to the detected error conditions.

14. The method of claim 13, wherein the actions include one or more of reporting the error condition, logging the error condition, or ignoring the error condition.

15. A non-transitory machine-readable medium comprising instructions which, when executed by a processor of the machine, cause the machine to manage software component builds by:

accessing multiple files associated with a software component;

mapping the software component to a subset of a set of build servers based on a typical frequency of changes to the software component; and

building the software component by using each build server, of the subset of build servers, to compile one or more of the multiple files.

16. The machine-readable medium of claim 15, further comprising instructions which, when executed by the processor, cause the machine to manage software component builds by:

determining a level of complexity of each of the multiple files;

determining a level of power of each of the build servers;

mapping each of the multiple files to a build server, of the subset of build servers, by mapping one or more of the multiple files with a higher level of complexity to a build server with a higher power level; and

compiling one or more of the multiple files by using each build server, of the subset of build servers, to compile the one or more files that are mapped to the build server.

17. The machine-readable medium of claim 15, further comprising instructions which, when executed by the processor, cause the machine to manage software component builds by scheduling one or more of the builds.

18. The machine-readable medium of claim 17, wherein the scheduling is based on a build requester or a build request time of each of the scheduled builds.

19. The machine-readable medium of claim 17, wherein the scheduling is based on build type or a build size of each of the scheduled builds.

20. The machine-readable medium of claim 15, further comprising instructions which, when executed by the processor, cause the machine to manage software component builds by detecting one or more error conditions and performing one or more actions in response to the detected error conditions.