Systems and methods for automated centralized build/merge management

• US 8,522,207 B1
• Filed: 09/19/2006
• Issued: 08/27/2013
• Est. Priority Date: 09/19/2006
• Status: Active Grant

• Current Assignee: United Services Automobile Association
• Original Assignee: United Services Automobile Association
• Inventors: Whittington, Paula A., Hager, Sean M., Chavez, Carlos J.
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): Lee, Marina
• Application Number:
  US11/524,359
• Time in Patent Office: 2,534 Days
• Field of Search: 717/170, 717/122
• US Class Current: 717/122
• 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. An article including a storage medium comprising computer-executable instructions to cause at least one processor to perform a method comprising:

continuously monitoring a system for requests to build or merge code, the continuous monitoring comprising iteratively;

checking out a program from a centralized location within the system;

identifying build dependencies for the program;

determining a latest build dependency from the identified build dependencies capable of building a source code to ensure a build uses a latest tested dependency change;

determining an applicable version of the latest build dependency;

integrating additional components with the program using the applicable version of the latest build dependency;

generating a source code build for the program using the applicable version of the latest build dependency and the additional components;

updating a shared directory with the generated source code build, the shared directory including a directory updated each time there is a source code build and each time there is a code merge;

identifying a conflict upon completion of the merging if there is a difference between one of components of a most recent applicable release of the source code build and a same one of the components of a subsequent release;

generating a merge report that summarizes the one or more components of the most recent applicable release and the subsequent release that were copied, deleted, added, and identified as a conflict;

resolving the conflict;

maintaining an inventory including the source code build, wherein the inventory includes a time and date of the source code build; and

maintaining a first source code repository and placing built source code into the first source code repository based on a particular naming convention.

2. The article of claim 1 wherein the centralized location is a second source code repository.

3. The article of claim 1, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

checking out the program after detection of a trigger.

4. The article of claim 1, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

providing a notification upon completion of the integrating additional components.

5. The article of claim 4 wherein the notification comprises an email message.

6. The article of claim 1 wherein the program is one version of a plurality of versions of the program.

7. The article of claim 6 wherein the applicable version of the latest build dependency is a most recent release of the dependency that applies to the one version of the program.

8. An article including a storage medium comprising computer-executable instructions to cause at least one processor to perform a method comprising:

continuously monitoring a system for requests to build or merge code, the continuous monitoring comprising iteratively;

comparing a first release of a program with subsequent release of the program;

automatically merging one or more components of the first release with one or more components of the subsequent release;

updating a shared directory with the one or more merged components, the shared directory including a directory updated in response to a source code build and in response to a code merge;

providing a notification upon completion of merging the components, the notification including identifying a conflict if there is a difference between one of the components of the first release and a same one of the components of the subsequent release;

generating a merge report that summarizes the one or more components of the first release and subsequent release that were copied, deleted, added, and identified as a conflict;

resolving the conflict;

generating a source code build of the one or more merged components;

maintaining an inventory including the source code build, wherein the inventory includes a time and date of the source code build; and

maintaining a source code repository and placing built source code into the source code repository based on a particular naming convention.

9. The article of claim 8, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

deleting one of the components from the subsequent release, if the one of the components of the subsequent release is omitted in the first release.

10. The article of claim 8, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

updating one of the components of the subsequent release if the one of the components in the first release is updated.

11. The article of claim 8, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

copying one of the components of the first release to the subsequent release, if the one of the components of the first release is new to the subsequent release.

12. The article of claim 8 wherein the subsequent release is a next release in a sequence.

13. The article of claim 8 wherein the subsequent release is a later release in a sequence.

14. An article including a storage medium comprising computer-executable instructions to cause at least one processor to perform a method comprising:

continuously monitoring a system for requests to build or merge code, the continuous monitoring comprising iteratively;

monitoring requests for a source code build of a program;

dynamically creating a search path identifying a most recent applicable release of a dependency for the source code build;

generating the source code build using the most recent applicable release of the dependency;

monitoring requests to merge the source code build;

dynamically merging the source code build into at least one subsequent release;

updating a shared directory with the merged source code build, the shared directory including a directory updated each time there is a source code build and each time there is a code merge;

identifying a conflict upon completion of the merging if there is a difference between one of the components of the most recent applicable release and a same one of the components of the subsequent release;

generating a merge report that summarizes the one or more components of the most recent applicable release and the subsequent release that were copied, deleted, added, and identified as a conflict;

resolving the conflict;

maintaining an inventory including the source code build, wherein the inventory includes a time and date of the source code build; and

maintaining a source code repository and placing built source code into the source code repository based on a particular naming convention.

15. The article of claim 14, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

maintaining an inventory of one or more source code builds.

16. The article of claim 14, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

providing a notification after generating the source code build.

17. The article of claim 14, the method performed by the at least one processor further comprising continuous monitoring comprising iteratively:

providing a notification after merging the source code build.

18. The article of claim 14 wherein the request for the source code build is represented by a first trigger.

19. The article of claim 14 wherein the request to merge the source code build is represented by a second trigger.

20. The article of claim 14 wherein the monitoring of requests for the source build of a program and the monitoring of requests to merge the source code build are performed by a daemon.