Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Idealism Versus Reality: Reality Wins 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Our work setup is that everything runs thru a QA branch (trunk -> QA -> branch ). This is a patch for us not having a proper path to live so we just have a branch for stage. But this affords us a single path to trunk. So it would be feasible to merge to QA, run the fast tests on QA, if I feel good enough about my changes and I'm lazy then you can have a process that runs at night that:
    • locks the QA repo (no more commits)
    • runs the long tests
    • if all passes then merge to trunk
    • else email all the developers the output of the tests.

    This doesn't make the wrong things wrong-er but it does make the right thing easier.

    --
    benh~
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.