2

2

I would like to know if it's possible to show commit messages from checkins linked to a case in the case history along with existing information like changes to the fields and other comments.

A bit of background:

  • I'm using Fogbugz on demand with an external SVN repository.
  • I have installed the post-commit script (and TortoiseSVN/Subclipse integration) and that works fine.
  • Unfortunately, I cannot install WebSVN or Trac for logs and diffs.
    • (Would installing WebSVN/Trac and linking it to Fogbugz provide the functionality I described?)
flag

3 Answers

1

I don't think you could see the SVN related information in the in the case history area without writing a plugin, Chris. You can get to this information from the left panel in FB though via the Checkins link.

WebSVN is slick, it gives you a quick way to go from the Checkins link to either a log of the changes made or a diff of the change with the previous version.

link|flag
I had a feeling that this might be the preferred way to see commit messages from a case, although it would be nice to see them without going to a different page – Chris Bunney Nov 13 2009 at 9:47
2

I implemented this by having the svn post-commit hook send the commit message to fogbugz via email. Since the body of an email message is shown in the case history, you effectively get what you're looking for.

It's a kludge, but not too bad of one.

link|flag
1

I have already written python scripts which use the FB API to download bug data (basic reporting functionality) and so I think updating such scripts to allow 'posting' to a bug wouldn't be too complicated.

The key problem, as I see it, is authentication. The existing logBugDataSVN.pl script, called from a post-commit hook, manages to bypass authentication - presumably via a built-in backdoor which only allows posting commit information to a bug; to use the API to post events to a bug you need to log in properly which is a pain for users who typically have their svn credentials cached already and so don't expect to be queried for username/password when committing changes.

One solution to this would be to hardcode authentication information into the 'new' logBugData script - given that the script is stored in the repository hooks area it should be secure from 'unauthorised' access anway.

I'm not sure when I'm next going to have some time to spend on this, however I'd be interested to collect any other ideas and suggestions in the interim.

link|flag
That's unfortunate with us not having a non-person user available (as is the free license seat with Perforce for that type of usage). We'll never have a paid seat go to this and we won't use an actual user's account either. – Kris K. Apr 6 2010 at 12:35
We've ended up using amoore's approach - ie the svn post-commit hook generates an email with commit details and sends this to the FB with the appropriate "... (Case nnnn)" in the subject. Most people here seem pretty happy with this approach, with the limitations that (a) you still need to use the normal 'Checkins' popup to actually see commit details and (b) it's a bit harder to fixup the audit trail when someone commits against the wrong bug by mistake. – Matt Feb 8 2011 at 11:38

Your Answer

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