Nice! A few questions.

1. Step 8, what's that for? Enabling something in FishEye it looks like.

2. What about custom workflows, how to add their details? Is the #resolve based on the transition name in JIRA (case-insensitive) or something else?

And in general, how does this handle rebuilding a FishEye index? Does FishEye resend all the notifications so that JIRA will suddenly have a frenzy of trying to action issues that have already been actioned.

~Matt

1. Step 8 is setting up the subscription from FishEye to JIRA of commits. It tells FishEye, everytime there's a commit, to post the details to JIRA at that URL. This functionality is provided by the Atlassian Notifer plugin, and can be used as a generic webhook to post commits to anything. The authenticationType can also be BASIC, in which case it will use HTTP BASIC authentication, and you need to supply a password parameter as well. You can also specify NONE for authentication.

2. There is an administration screen for configuring commit commands: http://confluence.atlassian.com/display/JIRASTUDIO/Configuring+Commit+Commands+for+Issues The instructions there apply to the JIRA Studio administration layout, but the commit commands link can be found in the Global Settings section of the administration menu. The commands are actually stored as properties on the workflow, this is why the patch is needed, because JIRA doesn't allow editing the built in workflow.

I'll have to check, but I don't think rebuilding the index will cause notifications to be resent. The worst it will do is cause notifications to be missed. The commit event publishing mechanism stores the ID of the last revision it published in the index itself, and only publishes revisions since that index. If the it doesn't find that stored ID, which would happen when you first point FishEye at a repository or if you rebuild the index, it doesn't publish anything, it just stores, and this only happens after the entire index has finished rebuilding. So, when you rebuild the index, any commits that happen while its being rebuilt may not be published. There is still a chance of JIRA being hammered, if FishEye goes down for a long time, and then is brought back up, and lots of commits have happened in the mean time.

If you do try this, would appreciate any feedback you have. It is likely that at some point we'll add subscribing to commit notifications a button on the administration screen for the JIRA FishEye plugin. Getting this to a state usable outside of JIRA Studio was just something that I decided to do last Friday as part of my 20% time, because I thought it was about time we offered it to customers (many have asked about it).

Thank you very much for the solution.

We still had to add the two paths
   /plugins/servlet/streams
   /plugins/servlet/commitnotification
to the
   URL Paths to Allow:
list in the FishEye trusted application configuration in JIRA

Thanks for the walk through. I've got both beta plugins installed and the POST returned a 201, but I can't download the xml.patch file because the SVN repo is requesting a username and password.

So I'm stuck with a blank "Commit Notification Command Mappings" page in JIRA Administration.

Interestingly enough, the page lists the table header (Command|Transitions|Action) and an 'Add workflow command mapping' link.

A workaround others might be interested in. I've copied the default jira workflow, created a new workflow scheme, and assigned a workflow to each issue type of the new workflow scheme. Finally, for each project, I needed to change the workflow scheme from None to Copied Workflow.

Hi Brad,

The commit notification command mappings page I think had a bug in it (overlooked by me in my race to get something done on a Friday afternoon). This has since been fixed and beta 2 has been released:

http://maven.atlassian.com/contrib/com/atlassian/jira/plugins/jira-fisheye-plugin/3.1-beta2/jira-fisheye-plugin-3.1-beta2.jar

Let me know if this fixes it.

That SVN repository has recently been made private, I've copied the patch to this website:

http://blogs.atlassian.com/developer/commitnotifications/jira-workflow.xml.patch

I hope this works for you!

I wasnt able to get it to this to work with standalone installs of Fisheye and JIRA. I can see Fisheye sending the notification to JIRA and JIRA responsding with a status 200. Since I havent followed the Dragon Quest procedure maybe it is a problem with authentication since im not using Crowd?

Thomas,

Can you check the following things:

* You have trusted apps setup so JIRA trusts FishEye
* The username you used in step 8 when you posted the subscription to FishEye is a system administrator on JIRA
* The usernames that are doing the commits in Subversion exist on JIRA, and have permission to perform the actions you're trying to perform.

This is make or break for us with Jira Standalone. Absolutely have to have action issues with commit commands and we're not interested in Studio. We must be able to include keywords in our commits that will not only cause workflow transitions but also add comments to the issue (to generate emails to watchers) - the lack of this in the Standalone version might be enough to prevent us from migrating from Trac.

Still, I thought I'd give this Fisheye integration a try, but here's where I'm stuck and hope you can help. I've proceeded with all of the steps and am still coming up with 'FishEye - 403 Forbidden' on the Firefox Poster Post even though the username I provide is an admin on both the Fisheye and jira installations. I also added the paths mentioned by Andreas above to Jira's Trusted Applications / Fisheye entry.

'You do not have permission to access that resource. Only an administrator can manage subscriptions'

running release
FE2.1.2
(build-444 2009-11-18)

We are trying this but hitting a 500 server error. In the fisheye log we see the following (note that I have edited out our repository name):

ERROR - /plugins/servlet/notifier/***/COMMIT
java.lang.NullPointerException
at com.atlassian.notifier.core.NotificationManagerImpl.validateSubscription(NotificationManagerImpl.java:184)
at com.atlassian.notifier.core.NotificationManagerImpl.addSubscription(NotificationManagerImpl.java:164)
at com.atlassian.notifier.core.servlet.NotificationSubscriptionServlet.doPost(NotificationSubscriptionServlet
.java:105)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
etc.

Hi Evan,

Error reporting could definitely be improved here, this NullPointerException indicates that no callback URL was set in the request. Could you double check that you've set the content type appropriately (to application/x-www-form-urlencoded) and that the message body that you're sending includes the url parameter (eg, url=http://localhost/jira/plugins/servlet/commitnotification).

Cheers,

James

James, that was it - the content type had a typo. Thank you!!