doc: Mention the 3 processes that make up Hydra.
[?]
Mar 16, 2011, 10:50 PM
3463ZP55AVXWRCCITGBFGBZ6NQ5ZRNAUK4H3PZVSWFJEER5ZXXTQCDependencies
- [2]
KBW3FDZ2Merge remote branch 'remotes/origin/master' - [3]
RQ4SOPS3whitespace commit - [4]
HN7JDKV3doc: Mention SQLite.
Change contents
- replacement in doc/manual/installation.xml at line 172
<title>Getting started</title><title>Getting Started</title> - replacement in doc/manual/installation.xml at line 175
To start the Hydra webserver, execute:To start the Hydra web server, execute: - replacement in doc/manual/installation.xml at line 179
When the server is started, you can browse to <ulink>http://localhost:3000/</ulink> to start configuring your Hydra instance.When the server is started, you can browse to<ulink>http://localhost:3000/</ulink> to start configuringyour Hydra instance. - replacement in doc/manual/installation.xml at line 183
</section><para>The <command>hydra_server.pl</command> command launches theweb server. There are two other processes that come intoplay: - replacement in doc/manual/installation.xml at line 189
<section><title>Example: PatchELF</title><para></para><subsection><title>Defining jobsets</title><para></para></subsection><itemizedlist><listitem>The <emphasis>evaluator</emphasis> is responsible forperidically evaluating job sets, checking out theirdependencies off their version control systems (VCS),and queueing new builds if the result of the evaluationchanged. It is launched by the<command>hydra_evaluator.pl</command> command.</listitem><listitem>The <emphasis>queue runner</emphasis> launches builds(using Nix) as they are queued by the evaluator,scheduling them onto the configured Nix hosts. It islaunched using the<command>hydra_queue_runner.pl</command> command.</listitem></itemizedlist> - replacement in doc/manual/installation.xml at line 207
<subsection><title>Creating views</title><para></para></subsection>All three processes must be running for Hydra to be fullyfunctional, though it's possible to temporarily stop any oneof them for maintenance purposes, for instance.</para> - edit in doc/manual/installation.xml at line 215