My first reaction was: Don't do it!

Install and test your set-up very thoroughly and then; stick with it until you have a need to change it. Then install and test the set-up with the changes, very thoroughly and then test again. And only then move your workload(s) over to it. But keep the old one running in parallel, ready for a quick back out if the results from the two do not compare. Only when you've run that way for a month or so, do you take the old set-up down.

Continuous integration is change for the sake of change; and (IMO) bloody madness.

But, assuming that isn't an acceptable answer to your question; then I'd suggest a two stage solution: one is your production system; the other your integration&test system. You run both with live data in parallel. Make your changes to the I&T system on Friday's whilst hording the input data; leave it to catchup with the production system over the weekend.

If on Monday everything checks out; it becomes your production system and the production system becomes your I&T system. Make the same changes to the new I&T system, run in parallel for a few days, then add the latest set of changes on Friday; catchup over the weekend.

Rinse & repeat.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

In reply to Re: Effectively handling prerequisites during continuous integration by BrowserUk
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.