Peter Edwards

• Website: perl.dragonstaff.co.uk
• About: Freelance Perl contractor.

Recent Actions

• Commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls
  Nice article....
• Posted Installing Local Perl And Libraries On Mac Book Snow Leopard to Peter Edwards

  I recently installed Perl 5.14 on a new Mac Book running Snow Leopard so I thought I'd share my findings and experiences to save the next person doing this some time.

  I started off by doing a search on Google for "install perl mac".
  Hit number 1: Download Perl - www.perl.org

• Commented on Ch-ch-ch-ch-changes
  1. Modern OO built in to the compiler. Not the hackjob add on we have now that is slow and has a lot of dependencies if you want full functionality (sorry, Moose is great work, the problem is not...
• Commented on Some nifty things you can do with Catalyst on Plack
  Nice article, Aristotle. I'm inspired to have a hack on this now!...
• Posted Colorized perl code snippets on ANSI terminals to Peter Edwards

  Ever wanted to do a quick diff on some perl code and see it colored like in in vim ?

  Fortunately, the Kate editor has a good colorizer and Gabor Szabo ported it to Perl. We can join that up with Term::ANSIColor to create a filter program to colorize perl code snippets on the fly:

Comment Threads

• David E. Wheeler commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  I haven't used the TAP plugin yet, but it looks like you can't use a standard tool like prove to run the tests. Instead you'd have to find all the tests yourself and run the manually with the output going to a file, something like:

     for tfile in `find t -name '*.t'`; do
         perl -Ilib $tfile > $tfile.tap 2>&1
     done
  

  And then you'd tell the TAP plugin to look for t/*.tap. This is rather annoying. Maybe I'm mistaken?

  —Theory

• ilmari.org commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  You can Point TAP::Harness::Archive at an empty directory to get per-script output in the form expected by the plugin.

• Bruno P. Kinoshita commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  Hi there David!

  I have just created an issue for that: https://sourceforge.net/tracker/?func=detail&aid=3489038&group_id=351793&atid=1470127

  I will work on this in the next days. Feel free to add any comments, suggestions.

  When I wrote tap4j, I had a short deadline to deliver it for an internal project too. So probably there is room for improvements in both, tap4j and TAP Plug-in (in the latter, mainly due to the fact that I code Java everyday, but still have a loooot…

• Bruno P. Kinoshita commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  Thanks for reporting the issue! I'm back working on my Open Source projects, probably until July/August.

  I'm currently working on a YAMLish issue in tap4j (this was reported in GitHub), and after this one I'll focus in integration tests for Perl x tap4j.

  Feel free to drop a message and check the status if I take too long to update the issue.

  All the best,
  Bruno

• Mark Stosberg commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  I also tried the TAP plugin for Jenkins/Hudson and couldn't get it to work.

  We are doing parallel testing with -j4, so the hack of manually running each script with "perl" won't work. and I couldn't get --archive to produce any results for me. (Perhaps it's not compatible with parallel testing). We also use "done_testing()", so perhaps that it is part of the issue as well.

  However, emitting JUnit works fine, I was just hoping to get TAP integration to work!