Beefy Boxes and Bandwidth Generously Provided by pair Networks Bob
XP is just a number
 
PerlMonks  

Re: Continuous integration tools for perl

by chrestomanci (Priest)
on Mar 17, 2011 at 10:38 UTC ( #893717=note: print w/ replies, xml ) Need Help??


in reply to Continuous integration tools for perl

What is wrong with Hudson or Jenkins?

If other parts of your organisation have already standardised on Hudson, then I don't think it is a good idea to be looking for alternatives until you have decided that it is unsuitable for your needs.

By using the same tool as other teams in your organisation, you reduce the effort required when you need to transfer code or people between teams. You should not be using a different tool just to be different.


Comment on Re: Continuous integration tools for perl
Re^2: Continuous integration tools for perl
by sblanton (Sexton) on Mar 17, 2011 at 12:53 UTC

    Agree with above, but if Hudson doesn't work for you - it didn't for me, you can try free Mojo from OpenMake Software. Hudson was too narrowly focused. Mojo can do production scheduling as well continuous integration, so it made sense to use one tool for both of those in addition to having additional flexibility on the CI side.

    Mojo actually grew out of a need for a standard tool across multiple development teams and languages, so as mentioned by chrestomanci, be careful adding unneeded complexity to your environment. As a disclaimer, I used to work for OpenMake Software, but helped make Mojo suitable for my own needs for Perl continuous integration.

    Continuous integration (CI) can be complex to set up and it can mean different things to different people. The details depend heavily on your version control tool. Mojo and Hudson do have hooks out of the box for a number of VC tools, but be sure to have a clear plan. Usually CI assumes a code-compile part, but with Perl I used passing automated unit tests as an integration measure.

    Mojo's GUI is very buggy, but it works solidly when configured. It easily allows you to create a job out of a perl command line, controlling arguments and environment variables. One of the best things is the real-time monitoring dashboard and the HTML wrappering and web posting of the output of all the perl cmds. It is perl/Eclipse/Java/C/C++ based, and if you use Eclipse, it can be nicely installed as a plug-in.

Re^2: Continuous integration tools for perl
by djzort (Acolyte) on Oct 12, 2011 at 09:58 UTC
    I would be interested if anyone knows of or wants to start a pure-perl CI platform. Not necessarily because there is anything wrong with whats out there, but merely because im a purist and im always keen to see diversity. fwiw there is still Tinderbox (which is perl) http://en.wikipedia.org/wiki/Tinderbox_%28software%29 there is a FreeBSD version and the original mozilla release. The FreeBSD one is active but is hardcoded to compiling freebsd ports, the original mozilla is old school. 'SCIT' recently popped up on freshmeat.net - http://code.google.com/p/scit/
      smolder also exists at - https://github.com/mpeters/smolder

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://893717]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (15)
As of 2014-04-16 17:43 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (433 votes), past polls