Claus Witt

I have previously blogged about Xinc. I have decided to show how simple my setup really is. The Xinc configuration is a simple xml file containing few commands.

It does nothing more than check if there is a newer revision of the Subversion repository, if there is, it checks it out, and runs the Phing buildscript, and reports if there are errors with a mail. (In the beginning it sent mails upon success as well – I got very tired of all the “nothing is wrong” emails so I decided it was ok to just notify me if something went wrong with a build.

The phing buildfile described in my previous post is almost just as simple.

I described the actions of this file in the previous post.

At my company Arnsbo Media, responsible for one of the largest archive of voiceover talents in the world, we use Xinc for Continuous Integration. Every five minutes the CI server checks if there has been updates to the trunk of each of our software projects. If this is the case it runs the phing buildscript which is responsible for updating the svn checkout, checking the source with a codesniffer, creating documentation and running all tests. If all is ok, Xinc is happy, and the latest version of the given software is ready as a zip file, documentation is ready for browsing. If anything fails a mail will be sent to notify everyone involved in the project.