Fix for FogBugz/Perforce integration on OSX

The Short Answer

Add --no-check-certificate to the wget call in logBugDataP4.pl

The Waffle

On the recommendation of Kirby, I’ve been trying out FogBugz for task and bug tracking. I’d dismissed FogBugz assuming the cost would be too much (and for the daft name), but, amazingly, it has a free startup edition – good for 2 users. (One of the most interesting features is the Evidence Based Scheduling i.e using historical metrics for better estimates. I’ll be very interested to see how it works out.)

FogBugz integrates with a number of SCM packages. In my case I’m also running the free 2-user Perforce install, and of course wanted to link the two. (I’ll get around to SVN and Git too but for now it looks like I’ll have to sort myself out for integration with AccuRev).

For Mac OS X, FogBugz has a Perl script (logBugDataP4.pl) which scans your changelist description for lines like:

BugzIDs: 1234


This allows FogBugz to link back to the Perforce changelist (if you’re running P4Web). By default though, the script appears to fail when issuing the wget.

The answer is to add –no-check-certificate to the wget calls, so that:

system("wget '$url' -q -O /dev/null");

becomes

system("wget '$url' -q -O /dev/null --no-check-certificate");

In my version I’ve removed the -q and the /dev/null preferring to dump the output and logging to files, so I can see what’s going on.

(There are two calls around lines 134 and 165.)