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.
  • We have the same issue at Fotango. Essentially we've come to the decision that if something is used by our source, then we need to version control it. The net result has been doing vendor imports of huge amounts of source code (ie, apache, mod_perl, perl, all CPAN modules, etc) into our version control system.

    We are also putting together a build system so that our systems all build into one app directory with its own bin, lib and include dirs.

    The individual package build instructions live on our intranet (which happens to be a Kwiki) and the build results get reported back to another page on the Kwiki. Basically the plan is to do nightly smokes that we can see relatively easily...

    The build instructions themselves need to be multiplatform, as we build to three different OS's. In order to handle that we've come up with a multi-platform build syntax for Kwiki that can be commented on^W^Wranted about alongside the build instructions themselves.

    As it turns out we need to manage well over 2 million lines of code, which has surprised all of us here....

    Its all very useful and interesting, but bootstrapping it is taking a _long_ time. Once we are done however, we'll have an Kwiki-based automated build system that allows our development team to be responsible for software quality, rather than the sysadmins. Of course this will be all open-sourced in several weeks...