Question

I'm currently evaluating FogBugz as our issue tracking system, but GitHub integration is essential for us, and I've found it disappointingly difficult to get these two services talking. There's not much documenation on this topic, especially on the FogBugz side, and what there is seems to be stale.

I'd like to know if anyone has FogBugz talking to GitHub, and get some advice on where I'm going wrong! (I've a suspicion right now that the issue is authentication of the user trying to get info, as these are non-public codebases.)

Here's what I've been trying:

FOGBUGZ ADMIN:

On FogBugz 8, hosted, I've set up a generic Source Control repository with a 'diff URL' of:

https://github.com/[my github user]/[my company]/[my repo]/commit/^R2

The 'log URL' is:

https://github.com/[my github user]/[my company]/[my repo]/commits/^FILE

GITHUB ADMIN:

On my repo, I've set up a FogBugz 'service hook'.

The 'Cvssubmit URL' is:

http://[my company].fogbugz.com/cvsSubmit.asp

The 'Fb Version' I've set to '7', as it looks like only '6.1' and '7' are supported. The version is actually 8 of course...

The 'Fb Repoid' I've set to that shown on the FogBugz source control popups.

I've ticked the 'Active' box. The 'Test Hook' button reports 'deploying payload' and 'payload deployed', but it is not clear what this did.

USAGE:

I was also wondering if perhaps the integration is working, but it's the parsing of the commit messages which isn't correct; what form of words should I be using in the Git commit message so that the bug number is parsed out correctly? I'm assuming, based on a Google, that it's something like, "Fixes a bug to do with X (see BugzID 12234)"

Any help appreciated, thanks.

Answer 1

With Adam's help, I believe I now have a working solution. It looks like the instructions on both FogBugz and GitHub are slightly misleading, and with both services being hosted, it can be tricky working out what's not configured correctly.

Here's what worked for me to get FogBugz On Demand (8.0) talking to a private GitHub repository:

1. FOGBUGZ CONFIGURATION

   1. Go to 'Admin' -> 'Source Control', and add a generic repository.
   2. Give it a name like 'GitHub - [repo name]'.
   3. Note the 'ixRepository' number on the 'Redownload Scripts' URI.

   4. Set the 'Diff URL' to:

      https://github.com/[company]/[repo]/commit/^R2

   5. Set the 'Log URL' to:

      https://github.com/[company]/[repo]/commits/^FILE

Just to be clear, if my repo displays as '/fooinc/foo' in GitHub then I mean [company] to be 'fooinc' and [repo] to be 'foo' in the examples above.

1. GITHUB CONFIGURATION

   1. Click on your repository.
   2. Go to 'Admin' -> 'Service Hooks' -> 'FogBugz'

   3. Set the 'Cvssubmit Url' to (note the https):

      https://[company].fogbugz.com/cvsSubmit.asp

   4. Set the 'Fb Version' to '7.0'

   5. Set the 'Fb Repoid' to the value of the 'ixRepository' from step 1.3
   6. Tick the 'Active' checkbox.

Hopefully this helps someone else get started quickly.

Thanks, Dave

Answer 2

The trick is that the script on github expects the string "7.0" for the version. anything else ("7", "8", "7.2") causes it to use the old-style source-control integration, which doesn't send the ixRepository parameter. If that change doesn't fix it, please send us an email: http://www.fogcreek.com/sendmail.html

Answer 3

Did you ever figure out how to mark a commit as being related to a bug, or resolving a bug, from the commit message? And what constitutes the "commit message", do I have to put it on the first line of my message (the title) or can I put it in the body?