Continuous Integration comes to AMO

It's time to hail another milestone for AMO in our epic push for improvements in 2010. This time I'm happy to announce our Hudson continuous integration server which has been humming along for a few months.

Hudson Integration Screenshot. Click to enlarge.

AMO is the first Mozilla Webdev site to use continuous integration, and it's been a long time coming. With the way it's currently configured we've got code coverage trending, unit test trending, code quality trending, as well as detailed reports for all the above for every single check in.

If anything fails or oversteps a threshold our IRC bot complains and we can get it fixed up quickly. It's a boon to productivity to know that all the code being checked in is being tested automatically, plus it gives everyone a stable state to compare to.

Thanks to everyone that helped get Hudson going, from the people that write it, to the IT team that keeps it alive, to the webdev team that helped work out the kinks.

2 Comments

Nice one Wil. We've just started using Hudson for continuous integration on the Translate Toolkit. I've found it helpful especially the tests and pylint output. Just seeing the state of those allowed us to pull them back into line. The coverage helped us discover that we're in a better test position then we thought.

We're not sure what our next steps are but we'll probably put Virtaal and Pootle onto Hudson as well as try to test various versions of Python.

I'll be interested to hear what new Hudson scripts you add for testing Django apps.
-- Dwayne Bailey, 12 Apr 2010
Hi Wil. I thought you might be interested in this post Dwayne wrote about actually integrating the testing of our translations into Hudson in addition to code:
http://translate.org.za/blogs/dwayne/en/content/continuous-integration-can-it-work-software-localisation
-- F Wolff, 12 May 2010

Post a comment

All comments are held for moderation; basic HTML formatting accepted.

Name: