Tinderbox

  • Revision slug: Tinderbox
  • Revision title: Tinderbox
  • Revision id: 73302
  • Created:
  • Creator: mdas
  • Is current revision? No
  • Comment 70 words added

Revision Content

Tinderbox is a webtool that Mozilla developers previously used to check whether the current source code compiles on various platforms and passes automated test suites. It has been replaced by Tinderboxpushlog (tbpl).

Available trees

Description

Mozilla runs build computers ("Tinderboxes") that continually build the latest source code; the tinderbox webtool shows the status of these builds. Use the tables there to find out the status of the source tree for the platform, product, and code branch you are interested in.

  • The green bar means the latest code (in cvs/hg) compiles and passes the tests that are run on the box.
  • Red means the build failed during compilation, so your build likely will fail too (provided you're using a similar toolset).
  • Orange means the binary was built successfully, but failed some of the tests.
  • Finally, if yellow, the build is in process.

Full output from a particular build is also available from the tinderbox page. These (rather large) pages can be used to figure out why the tree is red or orange.

Tinderbox also reports the results of various {{ interwiki('wikimo', 'Performance:Tinderbox_Tests', 'performance tests') }} such as Tp or Txul. Mozilla developers frequently check these numbers to observe the effect of code changes on performance; a change that sufficiently slows performance may be backed out.

Types of boxes

  • Nightly Clobber builds, go into update system
  • Build Dependent builds
  • Leak test build Debug build, then do leak tests
  • Unit test Compile & run test suites (xpcshell-tests etc)
  • Talos performance testing on bits produced by build boxes
  • Static analysis catalogs compiler warnings and runs Dehydra analyses. The static analysis box is maintained by bsmedberg rather than the release team, and is considered tier 2.

Downloading the tinderbox builds

You can also directly access and download the builds that have recently been produced by tinderbox on the Mozilla FTP : ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds(Similarly for other applications, replacing /firefox/ by /thunderbird/   /seamonkey/   /calendar/lightning/   etc.)
This gives you access to builds that are even more frequently updated than the nightly, and also, inside the directories ending with "-debug", to builds that have been produced in debug mode and will be easier to use with a debugger.

{{ languages( { "de": "de/Tinderbox", "es": "es/Tinderbox", "fr": "fr/Tinderbox", "it": "it/Tinderbox", "pl": "pl/Tinderbox" } ) }}

Other downloadable files

You can access files other than logs and builds generated by Tinderbox.


  •  *.tests.zip includes all the test files generated. You can use this for testing purposes, as the mochitests, reftests and other test harnesses can be run from here, given a working binary.
  • *crashreporter-symbols.zip used for debugging
  • *.checksums
  • *.langpack.xpi

Revision Source

<p>Tinderbox is a webtool that Mozilla developers previously used to check whether the current source code compiles on various platforms and passes <a href="/en/Mozilla_automated_testing" title="en/Mozilla_automated_testing">automated test suites</a>. It has been replaced by <a class=" external" href="http://tbpl.mozilla.org" title="http://tbpl.mozilla.org/">Tinderboxpushlog</a> (tbpl).</p>
<h4>Available trees</h4>
<ul> <li><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox">Firefox</a> (<a href="/en/mozilla-central" title="en/mozilla-central">mozilla-central</a>) (use <a class=" external" href="http://tbpl.mozilla.org/?tree=Firefox" title="http://tbpl.mozilla.org/?tree=Firefox">tbpl</a> instead)</li> <li><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi?tree=XULRunner">XULRunner</a></li> <li><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi?tree=ThunderbirdTrunk">Thunderbird</a> (mozilla-central + comm-central)</li> <li><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey">SeaMonkey</a> (mozilla-central + comm-central)</li> <li><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi?tree=Camino">Camino</a></li> <li><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi">Other tinderbox pages</a></li>
</ul>
<h4>Description</h4>
<p>Mozilla runs build computers ("Tinderboxes") that continually build the latest source code; the tinderbox webtool shows the status of these builds. Use the tables there to find out the status of the source tree for the platform, product, and code branch you are interested in.</p>
<ul> <li>The green bar means the latest code (in cvs/hg) compiles and passes the tests that are run on the box.</li> <li>Red means the build failed during compilation, so your build likely will fail too (provided you're using a similar toolset).</li> <li>Orange means the binary was built successfully, but failed some of the tests.</li> <li>Finally, if yellow, the build is in process.</li>
</ul>
<p>Full output from a particular build is also available from the tinderbox page. These (rather large) pages can be used to figure out why the tree is red or orange.</p>
<p>Tinderbox also reports the results of various {{ interwiki('wikimo', 'Performance:Tinderbox_Tests', 'performance tests') }} such as Tp or Txul. Mozilla developers frequently check these numbers to observe the effect of code changes on performance; a change that sufficiently slows performance may be backed out.</p>
<h4>Types of boxes</h4>
<ul> <li><strong>Nightly</strong> Clobber builds, go into update system</li> <li><strong>Build</strong> Dependent builds</li> <li><strong>Leak test</strong> <strong>build</strong> Debug build, then do leak tests</li> <li><strong>Unit test </strong>Compile &amp; run test suites (xpcshell-tests etc)</li> <li><strong>Talos</strong> performance testing on bits produced by build boxes</li> <li><strong>Static analysis</strong> catalogs compiler warnings and runs Dehydra analyses. <small>The static analysis box is maintained by bsmedberg rather than the release team, and is considered <a href="/en/Supported_build_configurations" title="https://developer.mozilla.org/en/Supported_build_configurations">tier 2</a>.</small></li>
</ul>
<h4>Downloading the tinderbox builds</h4>
<p>You can also directly access and download the builds that have recently been produced by tinderbox on the Mozilla FTP : <a class=" link-ftp" href="ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds/" title="ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds/">ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds</a>.  <em>(Similarly for other applications, replacing <code>/firefox/</code> by <code>/thunderbird/   /seamonkey/   /calendar/lightning/</code>   etc.</em>)<br>
This gives you access to builds that are even more frequently updated than the nightly, and also, inside the directories ending with "-debug", to builds that have been produced in debug mode and will be easier to use with a debugger.</p>
<p>{{ languages( { "de": "de/Tinderbox", "es": "es/Tinderbox", "fr": "fr/Tinderbox", "it": "it/Tinderbox", "pl": "pl/Tinderbox" } ) }}</p>
<h4>Other downloadable files</h4>
<p>You can access files other than logs and builds generated by Tinderbox.</p>
<br>
<ul> <li> *.tests.zip includes all the test files generated. You can use this for testing purposes, as the mochitests, reftests and other test harnesses can be run from here, given a working binary.</li> <li>*crashreporter-symbols.zip used for debugging</li> <li>*.checksums</li> <li>*.langpack.xpi</li>
</ul>
Revert to this revision