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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The source code is broken up into standard CPAN-compliant distributions. There's a CruiseControl instance that builds the ones that were affected after a change is checked in. If the build/test is successful, the result of "./Build dist" is put into a CPAN structure that is in the source repository along side the source code. (This houses all third-party distributions that we use as well.)

    There's one distribution that acts like a Task::* distribution, i.e. it doesn't do anything but depend upon other distributions and runs some overall sanity checks.

    Every six hours an integration build kicks off. It creates a new, isolated directory, copies some bootstrap files and distributions (CPAN, Module::Build, etc.) and uses a custom wrapper around CPAN.pm to install the task distribution. The standard dependency mechanisms pull in all the rest of our code plus the third party distributions we use. We end up with one output tarball containing everything we use.

    This was all set up by Jeff Thalhammer.