Comments on: Goodbye CruiseControl.rb, Hello Hudson http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/ Matt Wynne taking it one tea at a time Sat, 13 Mar 2010 00:10:48 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Chris Bailey http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-746 Chris Bailey Thu, 20 Aug 2009 21:33:09 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-746 <p>I gave Hudson a go, but couldn't get it completely working for my build. I have to agree it looks great though. Oh, and it ran (for my project) on a 1GB Slicehost slice just fine. I wound up going back to Integrity due to the problem alluded to. I wrote this all up in case it helps anyone else: http://codeintensity.blogspot.com/2009/08/further-continuous-integration-travels.html</p> I gave Hudson a go, but couldn’t get it completely working for my build. I have to agree it looks great though. Oh, and it ran (for my project) on a 1GB Slicehost slice just fine. I wound up going back to Integrity due to the problem alluded to. I wrote this all up in case it helps anyone else: http://codeintensity.blogspot.com/2009/08/further-continuous-integration-travels.html

]]> By: Matt http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-744 Matt Thu, 20 Aug 2009 06:07:09 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-744 <p>We have our own branch at http://github.com/songkick/testjour/tree/master but I don't think it has anything particularly special in it - you should be able to use Bryan's branch just fine.</p> <p>We don't use github for our main application code - again we just run a git repo in-house, so I've never needed to try the hooks. We just get hudson up to poll the repo for changes every minute, which is good enough for us. I'm happy to hear there's a github plugin though. Want to post back here when you've tried it and let us know how it works?</p> We have our own branch at http://github.com/songkick/testjour/tree/master but I don’t think it has anything particularly special in it - you should be able to use Bryan’s branch just fine.

We don’t use github for our main application code - again we just run a git repo in-house, so I’ve never needed to try the hooks. We just get hudson up to poll the repo for changes every minute, which is good enough for us. I’m happy to hear there’s a github plugin though. Want to post back here when you’ve tried it and let us know how it works?

]]> By: Chris Bailey http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-743 Chris Bailey Thu, 20 Aug 2009 00:25:59 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-743 <p>Thanks Matt. Do you use the master branch of brynary's testjour, or have you guys forked it, etc.? I've been starting to prowl through the code (which is how I've found differences in command line args from what the docs have), but I don't see an "--on" param for example. I will keep prowling, but lemme know if you have a fork, etc.</p> <p>I will also probably give Hudson a shot. I'm going to bump my CI slice up to 1GB and see if it runs in that. The incremental cost is ok. Looks like Hudson supports GitHub post-receive hooks via a plugin someone has on GitHub, you guys using that?</p> Thanks Matt. Do you use the master branch of brynary’s testjour, or have you guys forked it, etc.? I’ve been starting to prowl through the code (which is how I’ve found differences in command line args from what the docs have), but I don’t see an “–on” param for example. I will keep prowling, but lemme know if you have a fork, etc.

I will also probably give Hudson a shot. I’m going to bump my CI slice up to 1GB and see if it runs in that. The incremental cost is ok. Looks like Hudson supports GitHub post-receive hooks via a plugin someone has on GitHub, you guys using that?

]]> By: Matt http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-742 Matt Wed, 19 Aug 2009 22:36:24 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-742 <p>Hey Chris,</p> <p>We run Hudson on in-house hardware, so we have the luxury of being able to add RAM fairly cheaply. Here's the output from ps on our build server:</p> <pre>USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND hudson 4821 2.0 6.4 1553652 249600 ? Sl Aug05 431:43 /usr/bin/java -jar /usr/share/hudson/hudson.war --webroot=/var/run/hudson/war</pre> <p>So it looks like we need about 1.5GB to run our Hudson. YMMV.</p> <p>For running testjour slaves, we use this in our rake task:</p> <pre>def run<em>feature</em>group(feature_group) slaves = [] slaves << "--on=http://hudson@of1-dev-buildslave1.srv.songkick.net:15434/var/lib/hudson/skweb" slaves << "--on=http://hudson@of1-dev-buildslave2.srv.songkick.net:15434/var/lib/hudson/skweb" slaves << "--on=http://hudson@of1-dev-buildslave3.srv.songkick.net:15434/var/lib/hudson/skweb" slaves << "--on=http://hudson@of1-dev-buildslave4.srv.songkick.net:15434/var/lib/hudson/skweb" # profiles are defined in cucumber.yml # subsystem profile excludes file<em>store features from the build sh("testjour #{slaves.join(" ")} -p #{feature</em>group} --max-local-slaves=0 features/cucumber/#{feature_group}") end</pre> <p>I'd advise having a look at the testjour code if you're not sure what it's doing - it's still pretty immature and not especially well documented yet.</p> Hey Chris,

We run Hudson on in-house hardware, so we have the luxury of being able to add RAM fairly cheaply. Here’s the output from ps on our build server:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
hudson    4821  2.0  6.4 1553652 249600 ?      Sl   Aug05 431:43 /usr/bin/java -jar /usr/share/hudson/hudson.war --webroot=/var/run/hudson/war

So it looks like we need about 1.5GB to run our Hudson. YMMV.

For running testjour slaves, we use this in our rake task:

def runfeaturegroup(feature_group)
  slaves = []
  slaves << "--on=http://hudson@of1-dev-buildslave1.srv.songkick.net:15434/var/lib/hudson/skweb"
  slaves << "--on=http://hudson@of1-dev-buildslave2.srv.songkick.net:15434/var/lib/hudson/skweb"
  slaves << "--on=http://hudson@of1-dev-buildslave3.srv.songkick.net:15434/var/lib/hudson/skweb"
  slaves << "--on=http://hudson@of1-dev-buildslave4.srv.songkick.net:15434/var/lib/hudson/skweb"

# profiles are defined in cucumber.yml
  # subsystem profile excludes filestore features from the build
  sh("testjour #{slaves.join(" ")} -p #{featuregroup} --max-local-slaves=0 features/cucumber/#{feature_group}")
end

I’d advise having a look at the testjour code if you’re not sure what it’s doing - it’s still pretty immature and not especially well documented yet.

]]> By: Chris Bailey http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-741 Chris Bailey Wed, 19 Aug 2009 21:37:21 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-741 <p>I just switched from CC.rb to Integrity, but am interesting in Hudson as Integrity works, but leaves some things to be desired. My main question is how much memory do you think you need on an Ubuntu box to run Hudson for a single Rails project? I've been running my CI server on a 256MB slice at Slicehost, in part to keep costs down. From my past experience with Java, as folks indicate above, it seems I'd need a lot more memory to get Hudson working. I can probably go up one level, but I'd rather not jump up to a 1GB machine and incur that cost when I have a fairly decently working setup.</p> <p>I am also in the middle of setting up Testjour, and that's how I came across this blog entry, as I'm having some issues simply starting up slaves. Do you have the correct command line vs. what's documented? i.e. I've found I need to use "testjour run:slave", instead of the "start:slave" in the README, but it seems to want a URL as well?</p> I just switched from CC.rb to Integrity, but am interesting in Hudson as Integrity works, but leaves some things to be desired. My main question is how much memory do you think you need on an Ubuntu box to run Hudson for a single Rails project? I’ve been running my CI server on a 256MB slice at Slicehost, in part to keep costs down. From my past experience with Java, as folks indicate above, it seems I’d need a lot more memory to get Hudson working. I can probably go up one level, but I’d rather not jump up to a 1GB machine and incur that cost when I have a fairly decently working setup.

I am also in the middle of setting up Testjour, and that’s how I came across this blog entry, as I’m having some issues simply starting up slaves. Do you have the correct command line vs. what’s documented? i.e. I’ve found I need to use “testjour run:slave”, instead of the “start:slave” in the README, but it seems to want a URL as well?

]]> By: Matt http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-732 Matt Mon, 17 Aug 2009 20:27:50 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-732 <p>Agreed Aaron - I just recently needed a build server to run on the Dreamhost shared host this blog runs on, and the Dreamhost admins kept killing hudson because it hogged too much RAM! Integrity fitted the bill nicely in the end (though getting a sinatra app running on Dreamhost was a world of pain).</p> <p>You're right it should be easier to delegate builds to a 3rd party. http://runcoderun.com/ are having a good crack at it.</p> Agreed Aaron - I just recently needed a build server to run on the Dreamhost shared host this blog runs on, and the Dreamhost admins kept killing hudson because it hogged too much RAM! Integrity fitted the bill nicely in the end (though getting a sinatra app running on Dreamhost was a world of pain).

You’re right it should be easier to delegate builds to a 3rd party. http://runcoderun.com/ are having a good crack at it.

]]> By: Aaron Evans http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-730 Aaron Evans Mon, 17 Aug 2009 17:37:55 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-730 <p>Yeah, the best reason I see not to use Hudson is to avoid having a heavy Java server (even jetty) running. </p> <p>If you have a LAMP (or Rails) hosted or VPS build server, then you might be hesitant to take the memory and CPU hit. I'm working on a way to make it easier to get a dedicated build farm running.</p> <p>Wouldn't it be nice to have an account somewhere that could run CI and even parallelize build and testing out? I want to work on something like that</p> Yeah, the best reason I see not to use Hudson is to avoid having a heavy Java server (even jetty) running.

If you have a LAMP (or Rails) hosted or VPS build server, then you might be hesitant to take the memory and CPU hit. I’m working on a way to make it easier to get a dedicated build farm running.

Wouldn’t it be nice to have an account somewhere that could run CI and even parallelize build and testing out? I want to work on something like that

]]> By: SIdu http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-651 SIdu Tue, 30 Jun 2009 21:47:14 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-651 <p>CC.rb 1.4.0 (http://github.com/thoughtworks/cruisecontrol.rb/tree/v1.4.0) is now available and supports git, hg and bzr. We plan to support building on JRuby and Ruby 1.9 fairly soon.</p> CC.rb 1.4.0 (http://github.com/thoughtworks/cruisecontrol.rb/tree/v1.4.0) is now available and supports git, hg and bzr. We plan to support building on JRuby and Ruby 1.9 fairly soon.

]]> By: Chris Komen http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-547 Chris Komen Thu, 14 May 2009 19:03:40 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-547 <p>Latest Software Test and Performance Magazine article referenced Hudson as their CI builder, so I thought I'd try it. We didn't have any Java running on our Ubuntu build server (it was installed, but nothing was using it), but Hudson put a big hurt on the server, slowing it down noticeably. We didn't see any advantage over CC.rb, and since the server was also our project's database and source control (svn) server, we uninstalled it and went back to CC.rb.</p> Latest Software Test and Performance Magazine article referenced Hudson as their CI builder, so I thought I’d try it. We didn’t have any Java running on our Ubuntu build server (it was installed, but nothing was using it), but Hudson put a big hurt on the server, slowing it down noticeably. We didn’t see any advantage over CC.rb, and since the server was also our project’s database and source control (svn) server, we uninstalled it and went back to CC.rb.

]]> By: Luke Francl http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/comment-page-1/#comment-546 Luke Francl Thu, 14 May 2009 15:19:19 +0000 http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/#comment-546 <p>I love Hudson. After futzing with the Java version of CruiseControl a few years back, I tried Hudson and I was blown away by how I could configure EVERYTHING in the UI. And it's just gotten better over the years. Now you can even install plugins from the web interface.</p> <p>I definitely recommend Ruby folks give it a shot. It has a rake plugin, or you can just have it run a shell command.</p> I love Hudson. After futzing with the Java version of CruiseControl a few years back, I tried Hudson and I was blown away by how I could configure EVERYTHING in the UI. And it’s just gotten better over the years. Now you can even install plugins from the web interface.

I definitely recommend Ruby folks give it a shot. It has a rake plugin, or you can just have it run a shell command.

]]>