Re: Continuous integration tools for perl

in reply to Continuous integration tools for perl

Hudson is not bound to a specific programming language. Given that you organization already uses Hudson why deviate? Hudson is rapidly gaining in popularity and for good reason. It's easy to set-up and extensible. Tons of free plugins. See for a Perl example: automating Perl deployments with Hudson. You can add automatic testing, automatic code analysis, produce metrics for QA etc etc. Of course you can spend weeks/months comparing the different tools... But, as usual, it all starts with your requirements.

Cheers

Harry

Comment on Re: Continuous integration tools for perl

Replies are listed 'Best First'.
Re^2: Continuous integration tools for perl by sblanton (Sexton) on Mar 17, 2011 at 14:41 UTC
If you are going to evaluate, here are some random bits to pass along from my experience implementing build automation at 50 companies: (and no criticism implied whatsoever to other posters by my cynical tone) Read more... (1165 Bytes)	[reply]
Re^3: Continuous integration tools for perl by dHarry (Abbot) on Mar 17, 2011 at 15:00 UTC
sblanton++ Your comments are much appreciated. I would like to clarify one thing, I don't mind spending money, especially other peoples money;) But we have specific requirements with respect to open source. Basically, whenever possible use open source. The reason behind this is that we cannot afford to depend on Vendors that might go bankrupt (we have experience with that). Our projects can typically last for 10+ years. Some SW will have to work for many more years. Obviously the quality of open source varies a lot. In my experience you have to be very careful in selecting products and tooling. Things like install base, active community etc. are important factors. Also with commercial tools you can get stuffed. I once ended up between IBM and Oracle pointing to each other:( IBM blaming the database and Oracle blaming WebSphere. Cheers Harold	[reply]

In Section Seekers of Perl Wisdom