TAG | Continuous Integration
Yesterday I learned about Travis CI when I read a post by Lukas. I hadn’t heard about it before but just flicking through the documentation and some examples I got hooked.
Apparently it’s amazing.
For a while I’ve been toying with the idea to set up a fully automated continuous deployment process for my symfony plugins. You can think of continuous deployment as a continuous integration process with automated deployment.
I just didn’t come round to do it as I couldn’t find the time so far. But then I read this article by Toni Schneider about CD at wordpress.com and it got me hooked again.
So I thought lets write down what it takes for a start.
Now you may want to include this configuration file in your projects sourcecode to be used by all participating developers and your continuous integration server. But how?
I must admit that I have been lazy with my efforts on continuous integration lately. Eventually my server crashed unnoticed and I didn’t get any emails about broken builds anymore and by now I think I’ve stacked up some work to do.
First of course I’ve got to get my CI server up and running again, that’s why I installed Hudson again.
But there is room for improvement too. Sebastian Bergmann of PHPUnit fame spent some time on a template Hudson job for PHP projects that includes much more than PHPUnit. So I decided to use that!
Lately I was playing around with my old Hudson installation to try and use Sebastian Bergmanns PHP Hudson template. But in the end I only had it halfway working and was increasingly confused by the number of plugins I had installed.
So I decided to make a backup of everything and start from scratch with a fresh install. Only there are no official ebuild for my Gentoo box..
Using symfonys functional testing classes this is actually quite easy to do.
But wouldn’t it be cool if you could integrate these tests into your continuous integration service just like PHPUnit tests? Wouldn’t it be cool to be able to generate PHPUnit coverage reports?
Earlier this year I decided to go with Hudson as my Continuous Integration Server for testing my symfony plugins.
Earlier this week I installed phpUnderControl and wrote about setting up both phpuc and Hudson-CI.
Now what should you use? Here I try to summarise my experience and compare the two. (more…)
Yesterday I wrote about setting up a symfony plugin project in phpUnderControl. However so far I’ve been using Hudson as my Continuous Integration server. So before comparing the two I will explain how to achieve yesterdays setup using Hudson. (more…)
As I’ve just started to look into phpUnderControl again I thought why not try to setup a project for testing sfImageTransformExtraPlugin running all the PHPUnit tests that I wrote about last week.
So the goal is to setup a phpuc project for a single plugin but with all dependencies (symfony itself) provided. This was a bit tricky so here we go! (more…)
Those of you following my blog know that I use Hudson as my continuous integration server. You can see the running installation at automat.ical.ly.
Today I decided to give phpUnderControl another shot and I found that the brilliant post by Andries Seutens needs an update.