clickheat Extreme Programming Club: 'Continuous Integration' cont.

The Yorkshire Extreme Programming and Agile Methods Club

The Extreme Programming Club has changed it's name Please visit for details. All postings for upcoming meetings will now be made there.

Where we meet:
Our meetings are held on every second Wednesday of each month at Victoria Hotel Pub in Leeds city centre at 7.00pm.
Place »
Directions »
Google Callendar »
Join our mailing list for updates and interesting discussion on technology, project management, programming and many more...


'Continuous Integration' cont.

After Richard's really good presentation in Bradford last Wednesday (screencast to be uploaded soon, so watch this space) and a really good networking session that spanned from Black Marble offices to The Fighting Cock I would like to keep the thread going. There were some really good thoughts floating by the glasses of cloudy ales that evening and maybe asking wider community and their experience with Continuous Integration will spread the knowledge even further. So please come forward and share your views.

I would like to post my thesis, just to bootstrap the thread:
Would it not be so much easier for everyone, if all tests had to run prior to committing any code into the source management. This would kill off (i.e. speed up) the following loop:

whack some code > run all tests (OR not) > commit > wait for CI to do the build > when green move on, when red come back to code and fix it OR move on and pretend it wasn't you

Such a barrier would put an imperative on every developer to fix all the issues with their code, before they could even dream of committing. It would also mean that the bad code would be fixed by the perpetrators, leading to better practices across the organization. It seams like one of those small changes to the system, that would make huge difference.

Any thoughts on that or anything related to CI, please write them up folks!

And below is Roy Osherove singing about this issue:


Blogger Ian Carroll said...

Check out this article:

14 March 2008 at 13:09

Blogger Richard Fennell said...

If you are using Visual Studio TFS you can set all sorts of check in conditions e.g must complile, pass static analysis, pass tests, have comments etc. You can also write your own.

27 March 2008 at 16:43


Post a Comment

Subscribe to Post Comments [Atom]

<< Home