1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2 3<html> 4<head> 5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> 6 <title>Builds view</title> 7</head> 8 9<body> 10<h1>Builds view</h1> 11<p> 12This view shows the list of all the builds contained in the connected database 13or in the local data files if no database is connected. 14</p> 15 16<h2>Information status</h2> 17<p> 18When starting the tool for the first time, this view is empty as no data has been 19populated, neither from the <a href="local_data.html">local data</a> files 20nor from the performance results database. 21</p><p> 22The typical usage of the performance tools is to read local data files copied 23from the server (see <a href="local_data.html">local data</a>). When this has 24been done, build names are displayed in this view using normal black color. 25</p> 26Some or all build names of the list may be displayed in a different font when 27a performance results database is connected: 28<ul> 29<li> 30<i><font color="#888888">gray and italic</font></i>: no local data files 31were read 32<p><img src="images/builds-nolocaldata.png" alt="Builds view with no local data"/></p> 33</li> 34<li> 35<font color="#888888">gray</font></i>: the local data files were read but contain 36no information about this build (typically new performance tests ran but the local 37data files were not copied since then): 38<p><img src="images/builds-missinglocaldata.png" alt="Builds view with missing local data"/></p> 39In this case it's possible to update those builds using the popup-menu: 40<p><img src="images/builds-update.png" alt="Update local data builds"/></p> 41It's also possible to rewrite the local data files from the database contents 42in one shot using the toolbar pull-up menu: 43<p><img src="images/builds-updateall.png" alt="Update all local data"/></p> 44</li> 45</ul> 46 47<h2>Generate</h2> 48<p> 49From this view, it is also possible to generate HTML pages using the generate 50command accessible from the popup-menu: 51<p><img src="images/builds-generate-menu.png" alt="Generate results: menu item"/></p> 52<p> 53After having selected the directory where to put the generated files, it's possible 54to choose the baseline to compare with: 55<p><img src="images/builds-generate-baseline.png" alt="Generate results: baseline selection"/></p> 56<p> 57And also whether you only want to generate the fingerprints or all the data: 58<p><img src="images/builds-generate-fingerprints.png" alt="Generate results: fingerprints"/></p> 59<p> 60After the generation ends, there should be in the specified directory similar 61files than the one generated on eclipsebuildserv. 62</p><p> 63<i>Note that a PHP server is neeeded to be able to read these files as it's done on 64eclipsebuildserv or fullmoon...</i> 65</p> 66 67<h2>Filters</h2> 68<p> 69There are several possible filters in this view. 70 71<h3>Builds filters</h3> 72<ul> 73<li>Baseline: hide the baselines (starting with R-3.x)</li> 74<li>Nightly: hide the nightly builds (starting with 'N')</li> 75<li>Old: hide all builds before last milestone except earlier milestones</li> 76</ul> 77<p> 78In this view baselines filter is not activated by default. It's because it may 79be interesting to know which baselines have results in the DB. 80Note that this filter is not synchronized with the one in Components view. 81</p> 82 83</body> 84</html>
