<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>CruiseControl Overview</title>
<style type="text/css" media="all">
@import "cruisecontrol.css";
</style>
<link href="print.css" type="text/css" rel="stylesheet" media="print"/>
</head>
<body>
<div class="header">
<div class="hostedby">
Hosted By:<br/>
<a href="http://sourceforge.net"><img src="http://sourceforge.net/sflogo.php?group_id=23523&type=1" width="88" height="31" alt="SourceForge"/></a>
</div>
<div class="logo"><img alt="CruiseControl" src="banner.png"/></div>
</div>
<div class="container">
<div id="menu">
<ul id="menulist">
<li class="top"><a href="index.html">home</a></li>
<li><a href="download.html">download</a></li>
<li><a href="license.html">license</a></li>
<li><h2>documentation</h2></li>
<li><p id="menuselected">overview</p></li>
<li><a class="expandmenu" href="main/index.html">build loop</a></li>
<li><a class="expandmenu" href="reporting/jsp/index.html">results jsp</a></li>
<li><a class="expandmenu" href="dashboard.html">dashboard</a></li>
<li><a class="expandmenu" href="gettingstarted.html">getting started</a></li>
<li><a href="main/configxml.html">config ref</a></li>
<li><a href="faq.html">faq</a></li>
<li><a class="external" href="http://confluence.public.thoughtworks.org/display/CC/Home">wiki</a></li>
<li><h2>contributing</h2></li>
<li><a class="expandmenu" href="developers.html">developers</a></li>
<li><a href="contact.html">mailing lists</a></li>
<li><a href="svn.html">source repository</a></li>
<li><p id="menubottom">Release: 2.7.3</p></li>
</ul>
</div>
<div class="content">
<h1>Overview</h1>
<p>CruiseControl is composed of 3 main modules:</p>
<ul>
<li><a href="main/index.html">the build loop</a>: core of the system, it triggers build cycles then notifies various listeners (users) using various publishing techniques. The trigger can be internal (scheduled or upon changes in a <acronym title="Source Control Management">SCM</acronym>) or external. It is <a href="main/configxml.html">configured in a xml file</a> which maps the build cycles to certain tasks, thanks to a system of <a href="main/plugins.html">plugins</a>. Depending on configuration, it may produce build artifacts.</li>
<li><a href="reporting/jsp/index.html">the legacy reporting</a> allows the users to browse the results of the builds and access the artifacts</li>
<li><a href="dashboard.html">the dashboard</a> provides a visual representation of all project build statuses.</li>
</ul>
<p>This modularity allows users to install CruiseControl where it will best fit their needs and environment.</p>
<p>Using remoting technologies (HTTP, RMI), it is possible to control and monitor the CruiseControl build loop. Those are turned off by default for obvious security reasons.</p>
<p>CruiseControl can be installed from source, or using the all in one binary installation.</p>
<p>Further information can be found in this documentation and/or in the wiki.</p>
<h2>Architecture Diagram</h2>
<p><img src="cc-arch.png" alt="CruiseControl architecture"/> </p>
</div>
</div>
</body>
</html>
