<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add a script for automatically running the buildbot configurations on a test environment."
href="https://bugs.webkit.org/show_bug.cgi?id=169084">169084</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Add a script for automatically running the buildbot configurations on a test environment.
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Tools / Tests
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>clopez@igalia.com
</td>
</tr>
<tr>
<th>CC</th>
<td>achristensen@apple.com, bugs-noreply@webkitgtk.org, don.olmstead@am.sony.com, lforschler@apple.com, ossy@webkit.org
</td>
</tr></table>
<p>
<div>
<pre>I have been working on a script that does the following:
* Creates a temporal workingdir
* Installs buildbot and its dependencies there (very same version used by the webkit.org buildbot master <a href="https://build.webkit.org/about">https://build.webkit.org/about</a> ). This is important as there are problems that that may not be detected if you don't test with the same version that will be used on production.
* Copies the buildmaster config files to the temporal workingdir.
* Performs the required steps to start a buildmaster.
* Creates the required config for each slave and starts all of them.
Then you can use your browser to log into the test buildmaster at <a href="http://localhost:8710/">http://localhost:8710/</a> and test to trigger manual builds, etc.
So you can actually test any configuration changes on the buildmaster on a test environment that is pretty much identical to the production one.
When you finish testing, simply press CTRL+C and all the temporal files will be cleaned. Note that if you actually want to trigger builds, the default path for the temporal workingdir on Linux (/tmp/) may have not enough free space. You can specify another temporal directory with the --base-temp-dir argument.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>