Change from Tinderbox to Travis CI for automated Bugzilla testing

[David Lawrence]

Greetings

  For a month or so, I have been working on getting our automated Bugzilla QA test suite up and running with the Travis
Continuous Integration system[1] (Travis CI for short). Up until now we have been using Tinderbox[2] for performing our
automated testing. Mozilla WebOps have been wanting to decommission Tinderbox for quite some time as the code base is no longer
maintained and Bugzilla[3] was the only project still actively using it.

  Travis CI has a free service option for open source projects which is what we will be using for Bugzilla. It requires the code
to be located in github.com and since we now have a read-only mirror of all Bugzilla branches to github.com, Travis CI became a
good option. Basically whenever a commit is made, Travis CI fires off workers that will run the automated test suite and record
the results. All is required is a configuration file in the root directory of the code. The file contains some basic information
such as programming language, how to get the test environment set up, etc.

  So starting now, Tinderbox will no longer be running our automated test suite and we will instead using Travis CI[3]. Any
failures or changes in the testing status will be announced in the IRC channels #bugzilla and #qa-bugzilla. We will be working
on improving our test coverage as well as enabling tests for the master Bugzilla branch which we have not done up until now.
If you have any questions, feel free to email or ping me on IRC in #bugzilla.

Thanks
David Lawrence
Bugzilla Release Manager

[1] https://travis-ci.org
[2] http://www-archive.mozilla.org/projects/tinderbox/
[3] https://travis-ci.org/bugzilla/bugzilla

-- 
David Lawrence
dkl at mozilla.com