|
This document discusses how to programmatically create and maintain a Hudson instance (which is normally done by an administrator in a typical single-deployment scenario.) This is for a large organization that needs to manage a large number of Hudson installations, or perhaps a hosting environment that provides Hudson as a service. Installing a new instanceInstalling a new instance of Hudson is just a matter of deploying Hudson into an application server, so much of the automation depends on the container of your choice. You can also choose to run Hudson as "java -jar hudson.war" and use embedded Winstone, although the scalability of Winstone hasn't been widely tried yet. The only information Hudson needs when launching is HUDSON_HOME — a directory that Hudson uses to store all the data. See Administering Hudson for how to pass in this information. You can programmatically create such a directory and fill it with the data files to start Hudson in a pre-configured state that fits your environment. The easiest way to do this is to run Hudson once manually and configure it to a desired state, and grab its data file as a template. You should also be able to just look at the files and figure out what they mean. |