Abstract: A method for executing program builds comprising: analyzing file dependency information and job duration information associated with jobs of the program build; scheduling jobs for a current program build based on the analysis of the dependency information and the job duration data; executing the jobs according to the schedule; collecting file usage information and new job duration information from each of the jobs; supplementing the file dependency information with the file usage information; and storing the new job duration information to be used for scheduling jobs in subsequent program builds.

Abstract: A method for executing program builds. According to one embodiment of the invention, jobs are scheduled for a program build based on dependencies between the jobs, where at least some of those jobs include one or more registry operations. Usage information is collected from each of those jobs responsive to those jobs being executed. The usage information includes registry usage information from those jobs that include one or more registry operations and includes the results of those registry operations. The registry usage information is analyzed to determine whether the execution of any of those jobs resulted in a conflict. The analyzing includes, for each job including a registry operation, comparing a version of a registry entry used by that job in the program build with a version of a registry entry that the job would have used in a sequential program build. Results of jobs that generated a conflict are invalidated, and the invalidated job is rebuilt using the correct registry entry versions.

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: A multi-tiered process automation system employing a novel property attachment mechanism is described.

Abstract: A method is described comprising: scheduling jobs for a program build to execute in parallel across a plurality of nodes; predicting the files required to complete each of the jobs; and preloading the files to each node prior to the execution of each job.

Abstract: A method implemented within a distributed build system is described comprising: transmitting a first source file from a program build file repository to a first node, the first node using the source file to generate a target file identified in the build process; receiving a request for the first source file from a second node; and redirecting the second node to retrieve the first source file from the first node rather than from the program build file repository.

Abstract: A method is described for executing program builds comprising: scheduling jobs for a program build based on dependencies between files used in the jobs; executing the jobs according to the schedule; collecting file usage information from each of the jobs, the file usage information indicating operations performed on the files in each of the jobs; and analyzing the file usage information to determine whether any one of the jobs resulted in a conflict.

Abstract: A method for executing program builds is described comprising: executing jobs for a program build in parallel according to a first job schedule; detecting a recursive build invocation in one of the jobs; analyzing dependency information associated with the recursive build invocation; and based on the analysis, supplementing the first job schedule with additional job schedule data.

Abstract: A method for executing program builds is described comprising: analyzing file dependency information contained within a first file; scheduling jobs for a program build based on the analysis of the dependency information; executing the jobs according to the schedule; collecting file usage information from each of the jobs; and supplementing the file dependency information with the file usage information.

Abstract: A method is described comprising: scheduling jobs for a program build to execute in parallel across a plurality of nodes; predicting the files required to complete each of the jobs; and preloading the files to each node prior to the execution of each job.