1

I am using the FogBugz hosted service for issue tracking and Mercurial for version control. I'd like my Mercurial repository to show up in FogBugz and to be able to relate changesets to issues. Unfortunately, I'm running into a problem and I'm having trouble getting the feedback I need to solve it.

I read the documentation for how to integrate Mercurial and FogBugz. I downloaded fogbugz.py and left it in the home folder of the user that hg serve runs as. I modified hgrc thus:

[paths]
default = /var/hg/myproject

[extensions]
fogbugz = /home/user/fogbugz.py

[hooks]
changegroup = python:/home/user/fogbugz.py:hook

[fogbugz]
host=https://myproject.fogbugz.com

[web]
baseurl=http://my.ip.address:port

Currently, when I push from my repository to /var/hg/myproject, the push succeeds, and I see no error messages, but nothing shows up in the Source Control part of my FogBugz site. I also confirmed that I could access the Mercurial repository by pointing my browser at the given IP and port. The repo shows my changes. In /home/user, a fogbugz.pyc file shows up, so I'm pretty sure that the Python interpreter tried to run the file and produced a compiled version for later use.

I'm pretty sure that something in the given configuration is wrong, but I can't tell what.

flag
have you taken a look at Kiln hosted Hg? It has tight integration with FogBugz and great code review and repo management tools. It's only $5/user/mo when bundled with FogBugz On Demand: fogcreek.com/Kiln (I'm not ignoring your questions here. We'll get you an answer asap) – adambox Mar 17 2010 at 18:38
I am a student and broker than broke. So the full package is out of my price range - I'm using the Student version of FB. – Sean M Mar 17 2010 at 19:32
1 
The Student version of FogBugz comes with Kiln free. Just click on "Kiln" in the upper left...that should give you all the Mercurial integration you need, and you won't have any trouble with changeset integration. – Ben Kamens Mar 18 2010 at 1:35
Ben: I misinterpreted what I saw on the Kiln page earlier. I've got my repository synced to Kiln now. Do I still need to include the hgrc configuration changes and fogbugz.py, or do I just need to hg push to the given URL with my credentials ? – Sean M Mar 18 2010 at 3:50
if you're using kiln and pushing from your local repo to kiln, then you don't need to do anything to have your checkins show up in cases. – adambox Mar 18 2010 at 15:00

1 Answer

0

After messing around for a while, I figured out the problem is simply that this config goes in your central repo, not the local, and the changesets are logged in fogbugz when you push changes to the central repo. I'm updating this question with some more debugging steps and sanity checks and opening a case to improve the documentation.

For this case, the fix should be to put your hgrc in the central repo and remove the [extensions] part. When you push from local to the central, you should see the links in fogbugz.

link|flag
Thanks. I'm definitely open to the possibility that I'm Doing It Wrong, too. – Sean M Mar 17 2010 at 19:24

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.