Re: All JUnit tests now pass! Next steps...

[Scott Gray]

CI just stands for continuous integration and is the umbrella that all the specific tools live under.

From the link that Christian provided, we've got the choice of:

I haven't (and don't plan to at this stage) had a look at the ASF hosted OFBiz demo setup but we should be able to take care of this as a separate effort because the CI tools are hosted on their own separate servers. BuildBot (Feature list looks impressive: http://ci.apache.org/buildbot.html , includes the RAT tool for licensing checks)

Continuum (ASF project)
Gump (ASF project)
Hudson (Seems to be popular)



Regards
Scott

On 20/11/2009, at 9:26 AM, Tim Ruppert wrote:

I'd like to prefer an ASF project but not if it means giving up on some features that would be really useful.

I've used Cruise Control and Bamboo in the past and they're both amazing. I'm sure that CI will also do the trick.

Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

On Nov 19, 2009, at 1:06 PM, Scott Gray wrote:

Whoever's spending the time on the new Virtual Boxes that have been setup for OFBiz should totally get this setup as well. It would be a big win.

Thanks for the pointer Christian, I figured the ASF would have something for us and they haven't disappointed :-)

Thanks
Scott

On 20/11/2009, at 1:08 AM, Christian Geisert wrote:

I'll keep playing around the different CI services locally for a little bit so I can learn how they work a bit better and also find the one that will be the most useful to us.

Scott Gray schrieb:

It took a while but all our JUnit tests now pass, next I'd like to get a continuous integration server set up. Can anybody recommend some tools

Why not just use what is available at the ASF ;-)

http://ci.apache.org/

I use Hudson and like it, but I haven't tried the others...

Once that is done I'd like to have it run the tests after every commit and report any failures to the dev list. It would then be the offending committer's responsibility (well primarily at least) to fix the problem as soon as possible, much like a build failure. If we can't get everyone to agree to take on that responsibility then I might as well stop now because I'll be damned if I'm going to spend any more time fixing tests that I didn't break :-)

+1

All of this should help us increase the stability of the trunk and our confidence when taking a checkout that we won't half to spend our development time fixing things that used to work. It'll hopefully also encourage the community to contribute more tests with the knowledge that doing so will increase the stability of the functionality they depend on. Fix a bug and you're good for a day, write a test and you're good a lifetime :-)

--
Christian

Absolutly agreed, big thanks for your (and all the others) work in this area!

smime.p7s
Description: S/MIME cryptographic signature