Comments on: CruiseControl.rb and Bazaar http://inodes.org/2009/05/22/cruisecontrolrb-and-bazaar/ Moo - Development, Trouble-shooting and Random thoughts... Thu, 01 Jul 2010 03:27:59 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Sidu http://inodes.org/2009/05/22/cruisecontrolrb-and-bazaar/comment-page-1/#comment-2550 Sidu Fri, 03 Jul 2009 07:31:27 +0000 http://inodes.org/blog/?p=139#comment-2550 Thanks for the patch, John. It's been merged into the 1.4.0 release of <a href="http://cruisecontrolrb.thoughtworks.com" rel="nofollow">CC.rb</a> Thanks for the patch, John. It’s been merged into the 1.4.0 release of CC.rb

]]> By: johnf http://inodes.org/2009/05/22/cruisecontrolrb-and-bazaar/comment-page-1/#comment-2537 johnf Fri, 22 May 2009 23:24:18 +0000 http://inodes.org/blog/?p=139#comment-2537 @Mr. Hericus I should have been a bit more specific. In this particular case my server was already setup to run rails apps and it was simply much simpler to setup another rails app than to have to install say Tomcat to get a java CI rig running. Purely a case of sysadmin laziness in this case. :) In this case the VCS integration is fairly loose. It's not that complicated a patch basially a matter of <ul> <li>What command do you run to checkout, update etc</li> <li>How do you parse the log output to get author, date etc</li> </ul> John @Mr. Hericus

I should have been a bit more specific. In this particular case my server was already setup to run rails apps and it was simply much simpler to setup another rails app than to have to install say Tomcat to get a java CI rig running. Purely a case of sysadmin laziness in this case. :)

In this case the VCS integration is fairly loose. It’s not that complicated a patch basially a matter of

  • What command do you run to checkout, update etc
  • How do you parse the log output to get author, date etc

John

]]> By: Mr. Hericus http://inodes.org/2009/05/22/cruisecontrolrb-and-bazaar/comment-page-1/#comment-2536 Mr. Hericus Fri, 22 May 2009 16:42:38 +0000 http://inodes.org/blog/?p=139#comment-2536 What was it about being a rails project that made it incompatible with existing CI servers? From my point of view the CI server shouldn't care what type of project you are working with. Java, C++, C#, Rails, Groovy, etc. should all be one and the same. The same goes for VCS integration. If your CI is too tightly bound to your VCS, you'll run into problems like you hit, where you have to write your own code to get around the issues. The CI system should be loosely coupled to your dev environment. If it tries to know too much about what you are doing, then ultimately it won't be flexible enough to adapt to new projects and methodologies. What was it about being a rails project that made it incompatible with existing CI servers? From my point of view the CI server shouldn’t care what type of project you are working with. Java, C++, C#, Rails, Groovy, etc. should all be one and the same.

The same goes for VCS integration. If your CI is too tightly bound to your VCS, you’ll run into problems like you hit, where you have to write your own code to get around the issues.

The CI system should be loosely coupled to your dev environment. If it tries to know too much about what you are doing, then ultimately it won’t be flexible enough to adapt to new projects and methodologies.

]]>