System and method for detecting software patch dependencies

• US 8,615,752 B2
• Filed: 12/30/2008
• Issued: 12/24/2013
• Est. Priority Date: 12/30/2008
• Status: Active Grant

• Current Assignee: DoorDash, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Izard, William, de Vos, David, Spanner, Andreas
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): APONTE, FRANCISCO JAVIER
• Application Number:
  US12/346,165
• Publication Number:
  US 20100169874A1
• Time in Patent Office: 1,820 Days
• Field of Search: 717101-178, 726/21, 709/223
• US Class Current: 717/169
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

This disclosure relates to software patches and, more particularly, to detecting software patch dependencies in an environment where multiple software patches may be installed. A method, computer program product, and system for detecting software patch dependencies receives one or more first lists of software code segments, including changes to the software code segments associated with one or more first software patches. A second list of software code segments that includes software code paths executed at run-time by a second software patch is received. One or more matching code segments are identified. Dependencies of the second software patch based on the one or more matching software code segments are identified. The dependencies represent software patches required by the second software patch. A list of the dependencies is generated.

Claims

1. A method of detecting software patch dependencies comprising:

receiving one or more first lists of software code segments that include changes to the software code segments associated with one or more first software patches;

receiving a second list of software code segments that includes software code paths executed at run-time by a second software patch, wherein receiving the second list includes;

monitoring, by a code coverage tool, execution of the software code paths of the second software patch at run-time;

measuring, by the code coverage tool, the degree to which the software code paths of the second software patch have been tested or executed at run-time;

reporting the software code paths executed by the second software patch at run- time;

wherein said reporting includes which functions calls, statements or instructions have been executed during run-time; and

identifying the software code segments of the second software patch that are executed at run time;

identifying one or more matching software code segments that are included in at least one of the first lists and the second list, where the matching software code segments include changes associated with the one or more first software patches and software code paths executed at run-time by the second software patch;

identifying one or more dependencies of the second software patch based on the one or more matching software code segments, where the one or more dependencies represent one or more of the first software patches required by the second software patch; and

generating a list of the one or more first software patches required by the second software patch; and

compiling a software patch installation package that includes the second software patch and the one or more first software patches required by the second software patch.

2. The method of claim 1 further comprising:

installing the one or more first software patches on a computer system;

installing the second software patch on the computer system;

executing one or more applications on the computer system including exercising substantially all run time code paths of the second software patch;

monitoring the execution of the one or more applications, including monitoring at least the run time code paths of the second software patch;

recording the software code segments executed at run-time by the second patch during the exercising of substantially all run time code paths of the second software patch; and

generating the second list of software code segments executed at run-time from the recorded software code segments.

3. The method of claim 2 wherein the exercising of substantially all run time code paths of the second software patch is performed by one or more of:

an automated software test tool configured to exercise the run time code paths of the second software patch; and

a manual test process configured to exercise the run time code paths of the second software patch.

4. The method of claim 1 wherein the one or more first lists of software code segments are generated by a software source code revision tool.

5. The method of claim 1 wherein the second list of software code segments is generated by a run time software code coverage tool.

6. The method of claim 1 wherein the changes to the software code segments include one or more of:

a deleted method;

a modified method;

an added method;

a deleted class;

a modified class;

an added class;

a deleted file;

a modified file; and

an added file.

7. A computer program product for detecting software patch dependencies, residing on a non-transitory computer readable medium, having a plurality of instructions stored thereon, which, when executed by a processor, cause the processor to perform operations comprising:

receiving one or more first lists of software code segments that include changes to the software code segments associated with one or more first software patches;

receiving a second list of software code segments that includes software code paths executed at run-time by a second software patch, wherein receiving the second list includes;

monitoring, by a code coverage tool, execution of the software code paths of the second software patch at run-time;

measuring, by the code coverage tool, the degree to which the software code paths of the second software patch have been tested or executed at run-time;

reporting the software code paths executed by the second software patch at run-time;

wherein said reporting includes which functions calls, statements or instructions have been executed during run-time; and

identifying the software code segments of the second software patch that are executed at run time;

identifying one or more matching software code segments that are included in at least one of the first lists and the second list, where the matching software code segments include changes associated with the one or more first software patches and software code paths executed at run- time by the second software patch;

identifying one or more dependencies of the second software patch based on the one or more matching software code segments, where the one or more dependencies represent one or more of the first software patches required by the second software patch; and

generating a list of the one or more first software patches required by the second software patch; and

compiling a software patch installation package that includes the second software patch and the one or more first software patches required by the second software patch.

8. The computer program product of claim 7 wherein the operations further comprise:

installing the one or more first software patches on a computer system;

installing the second software patch on the computer system;

executing one or more applications on the computer system including exercising substantially all run time code paths of the second software patch;

monitoring the execution of the one or more applications, including monitoring at least the run time code paths of the second software patch;

recording the software code segments executed at run-time by the second patch during the exercising of substantially all run time code paths of the second software patch; and

generating the second list of software code segments executed at run-time from the recorded software code segments.

9. The computer program product of claim 8 wherein the exercising of substantially all run time code paths of the second software patch is performed by one or more of:

an automated software test tool configured to exercise the run time code paths of the second software patch; and

a manual test process configured to exercise the run time code paths of the second software patch.

10. The computer program product of claim 7 wherein the one or more first lists of software code segments are generated by a software source code revision tool.

11. The computer program product of claim 7 wherein the second list of software code segments is generated by a run time software code coverage tool.

12. The computer program product of claim 7 wherein the changes to the software code segments include one or more of:

a deleted method;

a modified method;

an added method;

a deleted class;

a modified class;

an added class;

a deleted file;

a modified file; and

an added file.

13. A computing system comprising:

at least one processor;

at least one memory architecture coupled with the at least one processor;

a first software instruction set executed on the at least one processor and the at least one memory architecture configured to receive one or more first lists of software code segments that include changes to the software code segments associated with one or more first software patches;

a second software instruction set executed on the at least one processor and the at least one memory architecture configured to receive a second list of software code segments that includes software code paths executed at run-time by a second software patch, wherein the second software instruction set is configured to monitor, by a code coverage tool, execution of the software code paths of the second software patch at run-time and measure, by the code coverage tool, the degree to which the software code paths of the second software patch have been tested or executed at run-time, and configured to report the software code paths executed by the second software patch at run-time;

wherein said report includes which functions calls, statements or instructions have been executed during run-time and identify the software code segments of the second software patch that are executed at run time;

a third software instruction set executed on the at least one processor and the at least one memory architecture configured to identify one or more matching software code segments that are included in at least one of the first lists and the second list, where the matching software code segments include changes associated with the one or more first software patches and software code paths executed at run-time by the second software patch;

a fourth software instruction set executed on the at least one processor and the at least one memory architecture configured to identify one or more dependencies of the second software patch based on the one or more matching software code segments, where the one or more dependencies represent one or more of the first software patches required by the second software patch; and

a fifth software instruction set executed on the at least one processor and the at least one memory architecture configured to generate a list of the one or more first software patches required by the second software patch; and

a sixth software instruction set executed on the at least one processor and the at least one memory architecture configured to compile a software patch installation package that includes the second software patch and the one or more first software patches required by the second software patch.

14. The computing system of claim 13 further comprising:

a seventh software instruction set executed on the at least one processor and the at least one memory architecture configured to install the one or more first software patches on a computer system;

an eighth software instruction set executed on the at least one processor and the at least one memory architecture configured to install the second software patch on the computer system;

a ninth software instruction set executed on the at least one processor and the at least one memory architecture configured to execute one or more applications on the computer system including exercising substantially all run time code paths of the second software patch;

a tenth software instruction set executed on the at least one processor and the at least one memory architecture configured to monitor the execution of the one or more applications, including monitoring at least the run time code paths of the second software patch;

an eleventh software instruction set executed on the at least one processor and the at least one memory architecture configured to record the software code segments executed at run-time by the second patch during the exercising of substantially all run time code paths of the second software patch; and

a twelfth software instruction set executed on the at least one processor and the at least one memory architecture configured to generate the second list of software code segments executed at run-time from the recorded software code segments.

15. The computing system of claim 14 wherein the exercising of substantially all run time code paths of the second software patch is performed by one or more of:

an automated software test tool configured to exercise the run time code paths of the second software patch; and

a manual test process configured to exercise the run time code paths of the second software patch.

16. The computing system of claim 13 wherein the one or more first lists of software code segments are generated by a software source code revision tool.

17. The computing system of claim 13 wherein the second list of software code segments is generated by a run time software code coverage tool.

18. The computing system of claim 13 wherein the changes to the software code segments include one or more of:

a deleted method;

a modified method;

an added method;

a deleted class;

a modified class;

an added class;

a deleted file;

a modified file; and

an added file.