Mechanism for managing execution of interdependent aggregated processes

1. BuildCycle

1.1 GatherCode

1.1.1 MergeCode

1.1.2 Get3rdParty

1.2 BuildProduct

1.2.1 Build3rdParty

1.2.2 BuildComponentl

1.2.3 BuildComponent2

1.2.4 BuildComponent3

1.3 TestProduct

1.3.1 TestComponents

1.3.1.1 TestComponentl

1.3.1.2 TestComponent2

1.3.1.3 TestComponent3

1.3.2 TestSystemlntegration

1.3.3 TestSystemFlow

1.4 PackageProduct

1.4.1 Gather3rdParty

1.4.2 GatherBinaries

1.4.3 Createlnstallation

1.4.4 CreatePackage
TIME

finishes after 1.1.

start after 1.1 (dependency) finishes after 1.2.*
start with 1.2 (parent)
start with 1.2 (parent)
start with 1.2 (parent)
start with 1.2 (parent)

start after 1.2 (dependency) finishes after 1.3.*

start with 1.3 (parent) finishes after 1.3.1 .*

start with 1.3.1 (parent)
start with 1.3.1 (parent)
start with 1.3.1 (parent)

start with 1.3 (parent)
start with 1.3 (parent)

start after 1.3(dependency) finishes after 1.4.
start with 1.4 (parent)
start with 1.4 (parent)
start with 1.4 (parent)
start with 1.4 (parent)

FIG. 3 RECEIVE A WORK REQUEST THAT SPECIFIES A FIRST JOB COMPRISING A FIRST TASK AND A SECOND JOB COMPRISING A SECOND TASK

m

RECEIVE A WORK REQUEST THAT SPECIFIES A FIRST JOB COMPRISING A FIRST SET OF SUB-WORKS AND A SECOND JOB COMPRISING A SECOND SET OF SUB-WORKS, THE SECOND JOB HAVING A DEPENDENCY ON SAID FIRST JOB MEETING A PARTICULAR CONDITION 502 ^_

1

PROCESS THE WORK REQUEST TO AUTOMATICALLY DETERMINE THAT THE SECOND JOB HAS THE DEPENDENCY

ON THE FIRST JOB

5iM |

I

PLACE THE FIRST JOB IN AN ACTIVE STATE TO ENABLE THE FIRST SET OF SUB-WORKS TO BE SCHEDULED FOR

EXECUTION

5£&

I

PLACE THE SECOND JOB INTO A PENDING STATE

508

"I

DETERMINE WHETHER THE FIRST JOB HAS MET THE
PARTICULAR CONDITION
510

T

IN RESPONSE TO DETERMINATION THAT THE FIRST JOB HAS MET THE CONDITION, PLACING THE SECOND JOB INTO AN

ACTIVE STATE

m

T

SCHEDULE THE SECOND SET OF SUB-WORKS FOR EXECUTION

514

FIG. 5

RECEIVE A WORK REQUEST THAT SPECIFIES A FIRST JOB COMPRISING A FIRST TASK THAT IS A CHILD OF THE FIRST JOB, THE WORK REQUEST INDICATING AN ASSOCIATION BETWEEN THE FIRST JOB AND A FIRST WORKSPACE DEFINITION THAT DEFINES A FIRST EXECUTION ENVIRONMENT

m

t

PROCESS THE WORK REQUEST TO AUTOMATICALLY DETERMINE THAT THE FIRST TASK INHERITS THE ASSOCIATION WITH THE FIRST WORKSPACE DEFINITION AND SHOULD BE EXECUTED USING THE FIRST WORKSPACE DEFINITION

m

CAUSE THE FIRST EXECUTION ENVIRONMENT TO BE AUTOMATICALLY PURGED FROM THE ONE OR MORE FIRST COMPUTERS AFTER EXECUTION OF THE FIRST TASK IS

COMPLETED
610

FIG. 6

RECEIVE A WORK REQUEST THAT SPECIFIES A JOB
COMPRISING A FIRST TASK
702

INTERPRETING THE WORK REQUEST TO AUTOMATICALLY ESTABLISH A JOB DATA STRUCTURE FOR THE JOB

704

INTERPRETING THE WORK REQUEST TO AUTOMATICALLY
ESTABLISH A FIRST DATA STORAGE STRUCTURE FOR THE

FIRST TASK
706

INTERPRETING THE WORK REQUEST TO AUTOMATICALLY ESTABLISH A PARENT-CHILD RELATIONSHIP BETWEEN THE JOB DATA STRUCTURE AND THE FIRST DATA STORAGE STRUCTURE

m

CAUSE THE FIRST TASK TO BE EXECUTED

m

CAUSE LOG INFORMATION PERTAINING TO EXECUTION OF THE FIRST TASK TO BE STORED IN THE FIRST DATA STORAGE

STRUCTURE

212

FIG. 7