Package hudson.init

Logic for Hudson startup.

See:
Description

Interface Summary

InitReactorListener

ReactorListeners that get notified of the Hudson initialization process.

Class Summary

InitializerFinder	Discovers initialization tasks from Initializer.
InitStrategy	Strategy pattern of the various key decision making during the Jenkins initialization.

Enum Summary

InitMilestone

Various key milestone in the initialization process of Hudson.

Annotation Types Summary

Initializer

Placed on static methods to indicate that this method is to be run during the Jenkins start up to perform some sort of initialization tasks.

Package hudson.init Description

Logic for Hudson startup.

Hudson's start up is based on the same idea as the modern Unix init mechanism like initng/upstart/SMF. It first builds a set of Tasks that are units of the initialization work, and have them declare dependencies among themselves. For example, jobs are only loaded after all the plugins are initialized, and restoring the build queue requires all the jobs to be loaded.

Such micro-scopic dependencies are organized into a bigger directed acyclic graph, which is then executed via Session. During execution of the reactor, additional tasks can be discovred and added to the DAG. We use this additional indirection to:

1. Perform initialization in parallel where possible.
2. Provide progress report on where we are in the initialization.
3. Collect status of the initialization and their failures.