Continuous Integration (vs)

The corporate standard is "Cruise Control", it's a fine tool but annoying to configure and setup and not to mention that I personally prefer Hudson.

I have a couple of questions that cover different topics:
1) Can the java community provide some insights into the best plug-ins for Junit testing, pass/fail reporting, auto-deployment .. etc.

2) Is there an honest, supportable reason for me to spend the time to convince the 'powers that be' that it would be in our best interest to move to Hudson. I have both setup on different VM's but as an Sr Engineer my role is more directional and less hands on - I just want the best for the team.

All suggestions welcomed.

Thanks,

Steve

Quote:

---

Originally Posted by ssgeejr

The corporate standard is "Cruise Control"

---

It is?

We use Hudson, easy to deploy and easy to setup. See Setting up Hudson for small Teams - Continuous Integration with Hudson, Part 1 mgm technology blog on setting it up.

And here is the link to the download Hudson CI

I think Sun (Oracle) even contribute to this and that they have a support licence you can buy if you require support for it.

Oh and I forgot to mention there are all sorts of plugins for it as well, for things such as FindBugs, PMD, CPD, checkstyle and loads of other ones that might help you out.

See Plugins - hudson - Hudson Wiki for more information about the plugins.

We're currently in the process our selfs to move over to Hudson from our custom built build system.

// Json

heh... I sorta missed that first word "Our corporate standard...."

Haha, fair enough :)

I hope my post helped you somewhat anyway. I think you just need to look into the different plugins that Hudson offer.

Btw what do you use to build your projects, ant, maven, other?

// Json

I have both CC and Hudson compiling the same two project (differently named) with each also compiling under ant and maven. These are simple math projects that have unit test for each math function; add, subtract, multiply and divide.

[Our] company standard here now is to ant ... and sadly no other tools. I have managed to procure a CI box and am in the works of putting together a presentation on moving to Maven. Personally, I am a Hudson, SVN and Maven guy ... but each company does things their own way. I am hoping, at a minimum, to get the team moved to the CI server using Maven (even if it's just a pom that calls the build.xml). I think once the team sees the advantage of having a library repository they will be more "enthused" to move their projects from Ant to Maven.

Personal comment: It's been my experience when moving other teams to an enterprise environment that maven can be a real pain the butt - but once you learn it, it's magic. I hated it for a long time until one day I woke up and saw the light - I expect resistance and thus the reason for the hard demo to have everything nice and shiny.

I really dont want to try and fight a maven and hudson battle - so I'm hoping to find some nice CC plugins (which google has been of no use for)

I've taken a ton of notes and plan on dropping this on my blog once I'm happy with it. I'll drop a reference here as well.

Steve

Alright, cool. I'm very much a Hudson, SVN and Maven guy myself actually, best of luck to you on your presentation, I hope you win them all over, maven is absolutely fantastic :D

// Json