Distributed parallel build system

• US 9,529,589 B2
• Filed: 03/02/2015
• Issued: 12/27/2016
• 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:
  US14/635,818
• Publication Number:
  US 20150169322A1
• Time in Patent Office: 666 Days
• Field of Search: 717120-125, 717107-109
• US Class Current: 1/1
• 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 comprising:

a components module configured to access one or more software components, each of the software components comprising one or more files; and

a mapping module executable by one or more processors and configured to map each software component to at least one of a plurality of build servers by dividing the number of build servers by the number of software components and assigning the resulting number of build servers to each of the software components; and

a compiler configured to build each software component using the at least one build server mapped to the respective software component to compile the one or more files of the software component.

2. The system of claim 1, wherein the mapping module is further configured to map each software component based on the size of the software component.

3. The system of claim 1, further comprising a scheduling module, coupled to the components module and the mapping module, configured to schedule one or more of the builds.

4. The system of claim 3, wherein the scheduling is based on a build requestor 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 an error handling module, coupled to the components module and the mapping module, configured 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 comprising:

accessing one or more software components, each of the software components comprising one or more files; and

mapping, by one or more processors, each software component to at least one of a plurality of build servers by dividing the number of build servers by the number of software components and assigning the resulting number of build servers to each of the software components; and

building each software component using the at least one build server mapped to the respective software component to compile the one or more files of the software component.

9. The method of claim 8, wherein the mapping of each software component is based on the size of the software component.

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 requestor 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 storing program code which, when executed, is operative to cause a machine to perform the operations of:

accessing one or more software components, each of the software components comprising one or more files; and

mapping, by one or more processors, each software component to at least one of a plurality of build servers by dividing the number of build servers by the number of software components and assigning the resulting number of build servers to each of the software components; and

building each software component using the at least one build server mapped to the respective software component to compile the one or more files of the software component.

16. The machine-readable medium of claim 15, wherein the mapping of each software component is based on the size of the software component.

17. The machine-readable medium of claim 15, the steps further comprising scheduling one or more of the builds.

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

19. The machine-readable medium of claim 15, the steps further comprising detecting one or more error conditions and perform one or more actions in response to the detected error conditions.

20. The machine-readable medium of claim 19, wherein the actions include one or more of reporting the error condition, logging the error condition, or ignoring the error condition.