Hudson or Teamcity for continuous integration?

continuous-integration hudson teamcity jenkins
pdeva picture pdeva · Sep 10, 2009 · Viewed 42.1k times · Source

We are a Java shop looking for a CI tool to use. Both Hudson and Teamcity seem to be free but Teamcity seems slicker and with more support.

I was wondering why one would still use Hudson and if anyone could provide any argument for/against either?

Answer

Nat picture Nat · Sep 10, 2009

Team City is by far and away the best CI server out there. Its killer feature for me is the tight integration with IDEs (IntelliJ, Eclipse and VisualStudio). It can show you, for example, when a file you're editing in the IDE becomes out of date, who changed it and what they changed. You can commit from the IDE to the CI server, run the comile and tests on the build grid, and then the CI server will commit if the build is successful. You can click on build reports in the CI web app and it will open the appropriate files in the IDE.

There are plugins available (I wrote one: http://team-piazza.googlecode.com), but not many.

Related questions

How to choose between Hudson and Jenkins?

It took me an hour or so to work out Hudson has only branched recently (Jan/2011) I have no idea how rapid the change of each branch is now, but more importantly, what is the direction each branch is taking …

Read More
Archive the artifacts in Jenkins

Could someone please explain to me the idea of artifacts in the build process? I have the workspace directory where I check out the code to compile and run my ant scripts etc. At the end, in my case, I …

Read More
Jenkins - passing variables between jobs?

I have two jobs in jenkins, both of which need the same parameter. How can I run the first job with a parameter so that when it triggers the second job, the same parameter is used?

Read More