Systems and methods for automated centralized build/merge management

• US 9,311,064 B1
• Filed: 08/22/2013
• Issued: 04/12/2016
• Est. Priority Date: 09/19/2006
• Status: Active Grant

• Current Assignee: United Services Automobile Association
• Original Assignee: United Services Automobile Association
• Inventors: Hager, Sean M., Chavez, Carlos J., Whittington, Paula
• Primary Examiner(s): Lee, Marina
• Application Number:
  US13/973,179
• Time in Patent Office: 964 Days
• Field of Search: 717/122
• US Class Current: 1/1
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Embodiments of the invention monitor requests for a source code build of a program. The source code build is generated using the most recent applicable release of the dependencies. The source code build is dynamically merged into at least one subsequent release. Other embodiments may be described and claimed.

Claims

1. A system, comprising:

a memory; and

a processor coupled to the memory and operable to execute instructions to;

using a continuous integration daemon to continuously monitor the system for a build label to trigger the processor to build or merge source code including the following steps;

retrieve a program from a centralized location within the system;

identify build dependencies for the program;

determine a latest build dependency from the identified build dependencies, including an applicable version of the latest build dependency;

create a shell script to interface with a build tool;

invoke the shell script to generate a source code build; and

upon successful completion of the source code build change the label to indicate a built state.

2. The system of claim 1, the processor further operable to execute instructions upon detecting a label to merge code to merge code and generate a merge report that summarizes the files that were copied, deleted, added, and identified as a conflict.

3. The system of claim 2, the processor further operable to execute instructions to update a shared directory with the generated source code build.

4. The system of claim 2, the processor further operable to execute instructions to update a data store with the generated source code build, wherein the data store includes a directory updated each time there is a source code build.

5. The system of claim 2 further comprising generating a merge status in response to a conflict identification, wherein the merge status summarizes the component of the latest build dependency and the same component of a subsequent release.

6. The system of claim 1, the processor further operable to execute instructions to update the same component of a subsequent release in response to the component of the latest build dependency being updated.