From 3426bf59fffee29395e2a0ec79f454f0bac7e3f1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Wed, 16 Mar 2011 22:50:02 +0000 Subject: [PATCH] doc: Mention the 3 processes that make up Hydra. --- doc/manual/installation.xml | 57 +++++++++++++++++++++++-------------- 1 file changed, 35 insertions(+), 22 deletions(-) diff --git a/doc/manual/installation.xml b/doc/manual/installation.xml index c966cf05..8ccb772a 100644 --- a/doc/manual/installation.xml +++ b/doc/manual/installation.xml @@ -169,34 +169,47 @@ export HYDRA_DATA=/var/lib/hydra
- Getting started + Getting Started + - To start the Hydra webserver, execute: + To start the Hydra web server, execute: hydra_server.pl - When the server is started, you can browse to http://localhost:3000/ to start configuring your Hydra instance. + When the server is started, you can browse to + http://localhost:3000/ to start configuring + your Hydra instance. + + + The hydra_server.pl command launches the + web server. There are two other processes that come into + play: + + + + The evaluator is responsible for + peridically evaluating job sets, checking out their + dependencies off their version control systems (VCS), + and queueing new builds if the result of the evaluation + changed. It is launched by the + hydra_evaluator.pl command. + + + The queue runner launches builds + (using Nix) as they are queued by the evaluator, + scheduling them onto the configured Nix hosts. It is + launched using the + hydra_queue_runner.pl command. + + + + All three processes must be running for Hydra to be fully + functional, though it's possible to temporarily stop any one + of them for maintenance purposes, for instance. + +
-
- Example: PatchELF - - - - - Defining jobsets - - - - - - Creating views - - - -
- -