Multiple Invocation Points In Software Build Task Sequence

• US 20110113415A1
• Filed: 03/25/2010
• Published: 05/12/2011
• Est. Priority Date: 11/09/2009
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: McCurdy, Daniel, McGraw, William Harrison IV, Ewington, Craig Leslie
• Granted Patent: US 8,972,974 B2
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/61 Installation

Abstract

Methods, apparatuses, and systems for handling multiple invocation points in a software build task sequence are described. A computer may receive a task sequence. The task sequence may include instructions for combining a first image and a second image to form a third image, installing a first software stack on the computer from a fourth image, and installing a software component to a second software stack already installed on the computer. The computer may receive an indication of a start point to begin executing the task sequence, and may execute the task sequence beginning at the start point.

Claims

1. A method, comprising:

receiving, at a computer, a task sequence, the task sequence comprising instructions for;

(a) combining a first image and a second image to form a third image,

(b) installing a first software stack on the computer from a fourth image, and

(c) installing a software component to a second software stack already installed on the computer;

receiving, at the computer, an indication of a start point to begin executing the task sequence; and

executing, by the computer, the task sequence beginning at the start point.

2. The method of claim 1, wherein the start point is such that executing the task sequence from the start point causes only a subset of (a), (b), and (c) to be performed.

3. The method of claim 1, wherein the start point is such that executing the task sequence from the start point causes (b) and (c) to be performed, but not (a), and wherein the first and second software stacks are a same software stack.

4. The method of claim 1, wherein the start point is such that executing the task sequence from the start point causes (c) to be performed, but not (a) and (b).

5. The method of claim 1, wherein the start point is such that executing the task sequence from the start point causes (a), (b), and (c) to be performed, wherein the third and fourth images are a same image, and wherein the first and second software stacks are a same software stack.

6. The method of claim 1, wherein the task sequence is configured such that execution of (a) causes execution of (b).

7. The method of claim 6, wherein the task sequence is configured such that execution of (b) causes execution of (c).

14. The computer-readable medium of claim 6, wherein the task sequence is configured such that execution of (b) causes execution of (c).

8. A computer-readable medium storing computer-executable instructions for performing a task sequence, the task sequence comprising instructions for:

(a) combining a first image and a second image to form a third image;

(b) installing a first software stack on the computer from a fourth image; and

(c) installing a software component to a second software stack already installed on the computer,

wherein the computer-readable medium further stores an indication of a start point to begin executing the task sequence, the start point corresponding to one of (a), (b), and (c).

9. The computer-readable medium of claim 8, wherein the start point is such that executing the task sequence from the start point causes only a subset of (a), (b), and (c) to be performed.

10. The computer-readable medium of claim 8, wherein the start point is such that executing the task sequence from the start point causes (b) and (c) to be performed, but not (a), and wherein the first and second software stacks are a same software stack.

11. The computer-readable medium of claim 8, wherein the start point is such that executing the task sequence from the start point causes (c) to be performed, but not (a) and (b).

12. The computer-readable medium of claim 8, wherein the start point is such that executing the task sequence from the start point causes (a), (b), and (c) to be performed, wherein the third and fourth images are a same image, and wherein the first and second software stacks are a same software stack.

13. The computer-readable medium of claim 8, wherein the task sequence is configured such that execution of (a) causes execution of (b).

15. An apparatus, comprising:

a computer-readable medium storing computer-executable instructions for performing a task sequence, the task sequence comprising instructions for;

(a) combining a first image and a second image to form a third image,

(b) installing a first software stack on the computer from a fourth image, and

(c) installing a software component to a second software stack already installed on the computer,

wherein the computer-readable medium further stores an indication of a start point to begin executing the task sequence, the start point corresponding to one of (a), (b), and (c); and

a processor configured to execute the task sequence beginning at the start point.

16. The apparatus of claim 15, wherein the start point is such that executing the task sequence from the start point causes only a subset of (a), (b), and (c) to be performed.

17. The apparatus of claim 15, wherein the start point is such that executing the task sequence from the start point causes (b) and (c) to be performed, but not (a), and wherein the first and second software stacks are a same software stack.

18. The apparatus of claim 15, wherein the start point is such that executing the task sequence from the start point causes (c) to be performed, but not (a) and (b).

19. The apparatus of claim 15, wherein the start point is such that executing the task sequence from the start point causes (a), (b), and (c) to be performed, wherein the third and fourth images are a same image, and wherein the first and second software stacks are a same software stack.

20. The apparatus of claim 15, wherein the task sequence is configured such that execution of (a) causes execution of (b), and execution of (b) causes execution of (c).