All the Perl that's Practical to Extract and Report
use Perl Log In
jozef (8299)
>500k lines of Perl code and >2.4k packages
Once upon a time there was >500k lines of Perl code and >2.4k non-CPAN packages in a huge SVN repository. Sounds like fun? Yes, especially for a new-comer
Now? Even more lines and even more packages in even huger SVN repository
How? http://github.com/jozef/HTTP-DAV-Browse/ that allows to walk through SVN WebDAV (check examples/hdb-build-tarballs for complete script), http://github.com/jozef/Build-Daily/ to allow daily/svn_revision based versions and http://github.com/AndyA/CPAN--Mini--Inject/ that has now option to index *.pm files of tarballs (--discover-packages).
Future? Feeds for everyone about failed builds, smoketesting, automated Debian packages builds or ??? Let's see where the fantasy will take us...
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
reporting (Score:1)
For reporting the smoke tests you might want to look at Smolder (http://github.com/mpeters/smolder/tree/master). You basically just hand it TAP archive and it will generate a nice looking report and send emails and an Atom feed. Reports are per-project. This might get kind of tricky with so many modules, but if you just organized the modules by project (if that makes sense) and then each test submission was a different module then it would probably work (especially if you use some tags to help organize thin