On Thursday 19 July 2012 11:49:19 Klaas Freitag wrote: > > I assume you already know how ci works - if not speak up, I'll happily > > describe it in a second email. > Heh, this is a typical question where nobody wants to say "Yes, I don't > know"
I learned about Continuous Integration (CI) from the book "Pragmatic Project Automation" by Mike Clark [1]. While it's written in 2004 and therefor the tooling is better and more extensive, the principle still applies. > PS: The sun shines over mirall :) That made you feel good, right? That's exactly what CI accomplishes, you *want* the sun to shine (or in the book's case the lava lamp to do it's magic). So if the sun isn't shining, maybe it's even raining, you want to fix things so the sun will shine. Seeing the various metrics your CI-server shows go down with each commit is really motivating. And since all the unit tests are run with each job, you also ensure that you're not breaking stuff along the way, which gives you peace of mind ... and better code. Improving the metrics is also a great candidate for junior jobs ;-) If you want even more metrics you can also plug in sonar into the mix, although I don't how well it works with php (I'm a Java developer) HTH, Diederik [1] http://pragprog.com/book/auto/pragmatic-project-automation _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
