Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Re^2: Continuous integration tools for perl

by sblanton (Sexton)
on Mar 17, 2011 at 14:41 UTC ( #893767=note: print w/replies, xml ) Need Help??

in reply to Re: Continuous integration tools for perl
in thread Continuous integration tools for perl

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)
  • If you have a budget, you can often get far better tools - sorry, open source guys, but it's true. Consider if they are worth it.
  • Beware following software tool trends, but at least you'll be in a large club where you can easily get good and bad advice.
  • Make sure the tool does what you need and beware the claim that something "can" do do something as opposed to "does" do something. That usually means it's extensible by some obscure means leading you down a path you don't want to be on. 3rd party plugins tend to be weak. Make sure the tool does what you need it to do pretty much out of the box/as downloaded or it is probably the wrong tool to use.
  • Open source is big on innovation and features but poor in stability and support. Commercial tools the opposite. But not perl or other rare, successful projects like Apache, JBoss, Linux (which are not dev tools). Projects vary of course.
  • If you are a really small place(<15 developers), probably stick with all open source tools.
  • If you are a crack open source developer, then open source is great because you can fix the bugs you need fixed.
  • Comment on Re^2: Continuous integration tools for perl

Replies are listed 'Best First'.
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.



Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://893767]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (4)
As of 2018-05-24 16:13 GMT
Find Nodes?
    Voting Booth?