I would, if it were me, choose a smaller and more Hudson-compatible codebase than Perl to evaluate Hudson. Perl's testing framework is extensive, but not well-supported out of the box by Hudson. (A significant amount of fiddling about would be necessary to integrate this with Hudson, and given that you are probably not going to be making updates to the Perl codebase itself, it's probably valueless for you.) I'd suggest getting Hudson building itself first as an evaluation tool, or better yet, Jenkins, as that codebase changes faster, and you'd get a better chance to evaluate the change tracking features in Hudson.

I have not used Bamboo, so I will refrain from making any remarks about it at all!

I think the approach mentioned previously, adding Puppet to the mix, is a good one; Perl's module installation stuff will work better if allowed to work in its natural manner; trying to graft more modules into the standard build is likely to prove quite difficult, especially if you're not already very familiar with the Perl build process. I'd recommend building the Perl source and making whatever standard Solaris package from that, then using Puppet or the like to run CPAN to install the modules you'd like to add.

In reply to Re^5: Add Modules to a PERL-Distribution by pemungkah
in thread Add Modules to a PERL-Distribution by gyrson

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.