-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PullRequestComment Event does not appear to work with TFS 2017 #49
Comments
Are you sure you're running TfsNotificationRelay.tfs15-v1.17.0? Look in the windows application log for any errors. |
@kria looks like it IS working for most events, but not for the PullRequestComment event. I'm using Git, and I left the config file with defaults (All) except for the Slack webhookUrl and channels settings. Yes, I am using a fresh download of that version, thanks. |
You're right, PullRequestComment seems broken. Something must have changed between RC2 and RTM. I'll take a look at it. |
@kria I've been trying to figure it out myself in the source, but I'm not sure how to pull the events list. I haven't found any documentation on that particular event either. |
Yeah there really isn't any documentation for this stuff, one has to dig into the dll:s. I pushed a fix, I assume you can build it yourself. I found some other stuff I want to fix before doing a new release. |
@kria thanks for your help! I built it from your new branch, but am now seeing errors in my Application Log. I am going to try to debug it a bit myself but here is the detailed message: TF53010: The following error has occurred in a Team Foundation component or extension: Detailed Message: The subscriber TfsNotificationRelay raised an exception while being notified of event Microsoft.VisualStudio.Services.CodeReview.Discussion.WebApi.Events.DiscussionsNotification. |
I haven't seen that one before. It "works on my machine". Do you get it for all PRs or just some? The fact that I'm using something called
|
Did you find out anything more @unicron? I wasn't able to reproduce it. |
Thanks @kria I'm just now getting around to the log statements. Will report back if I have any further information. |
Looks like the comment does come through in the log. Maybe the format has changed? Here is the log of a comment pasted: [1/26/2017 9:55:18 PM] pullRequestId:2298 |
So weird, that data looks right. The pull request id is right there, how can it not find it. 😕 |
https://tfs.xxx.com/tfs/DefaultCollection/xxx/_git/xxx/pullrequest/2157 is the format, yeah. It does not seem to work with any PR, existing or new. For the other notifications, we are getting the created/changed/votes for PRs just fine. |
What I wanted to make sure is that the id in the url is the same as the pullRequestId in the log? The other event handlers fetch the pull requests by a different method so I might try changing to that and see if that works better for you. |
Nope, they do not match. The pullRequestId and ArtifactId (the end of that Id, 2298 in the example above) do match, but it does not match the url of the PR so that's the issue. I have yet to figure out any pattern for why it does not match. |
Try the prid branch. Hopefully it fixes things. 🙏 |
Thanks @kria it is working! |
Trying to use with self-hosted version of TFS 2017. About page shows the following:
Microsoft Visual Studio Team Foundation Server
Version 15.105.25910.0
Previous versions worked great with TFS 2015! Thanks!
The text was updated successfully, but these errors were encountered: