Upgrades from external sources is a risk-laden activity.
Continuous Integration is a form of automation, and automation is dependent on a risk-averse environment.

I would not trust my product development process to be dependent on an automated CPAN upgrade/install/deploy process until my testing and monitoring infrastructure had proved themselves over time. Update: I also suffer no delusions that it would ever truly reach this state.

I think your local PPM cache is a brilliant work-around, and permits you to continue to develop and refine the automation of your CPAN upgrade and testing process as you see fit. If you ever get to the point where you trust that back end automation, you can choose when to integrate that into your PPM cache.

Until then, you're stuck with a mostly-manual process, substituting the time-honored "sweat and blood" for automation, all in the name of reliability. Theoretically, this should keep you motivated to work on those back end upgrade, testing, and monitoring tools. :-)

Or you could settle for releasing crap.

I do hope you saw that last line as sarcasm. :-)

In reply to Re: Effectively handling prerequisites during continuous integration by marinersk
in thread Effectively handling prerequisites during continuous integration by ali0sha

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.