TfsNotificationRelay Versions Save

New

• Support for TFS 2017 Update 2.
• I got tired of creating all (five!) different editions manually, so I added a Cake build script to automate it.
• With the packaging automated, I took the opportunity to start signing the assemblies. Thanks to DigiCert!

Fixes

• #56 GitPush with gitRepository filter not working well
• #57 Messed up commit order
• #58 PullRequestComment issue on TFS2017.2 (RC)

Fixes

• #49 PullRequestComment Event does not appear to work with TFS 2017
• #50 Notification failure because HipChat removed TLS 1.0 support
• Git commit rows have been showing UTC times since the TFS 2017 migration, back to local time now.

New

• #53 TFS 17.1 support (TFS 17 and 17.1 have diverged, so pick the right zip)
• #52 Microsoft Teams support contributed by @mozts2005. Unfortunately the Teams API is kinda crappy, so it's hard to make it look right.

Changelog

I'm dropping support for TFS 2015 RTM and 2015 Update 1 in this release. TfsNotificationRelay.tfs2015-v1.17.0 will only run on TFS 2015.2 and TFS 2015.3.

Fixes

• Don't show empty Assigned To fields on work item updates.

New

• TFS "15" RC 2 support
• Filtering on text in comments with the new text attribute (affects GitPush, Checkin, WorkItemComment, GitCommitComment, PullRequestComment and ChangesetComment). If you for instance don't want the automatic comments when checking in a changeset associated with a work item, you can now add a rule like this:

<rule notify="false" events="WorkItemComment" text="Associated with changeset" />

• New PolicyViolation event to work with TfsPolicy

Changelog

Fixes

• #44 Word wrapped git commits

New

A new SmtpNotifier to send email notifications.

New for TFS 2015.2+ only

• Notifications for Git repository rename and delete
• Notifications for the new release management

This bugfix release fixes #42 for TFS 2015. Work item DM notifications via DirectMessageNotifier wouldn't fire.

Looking for TFS 2013 binaries? Get the previous release!

Changelog

New

TFS 2015.1 and 2015.2 support.

I have merged the old tfs2015 branch into master. The other active branches are: tfs2013, tfs2015.1 and tfs2015.2.

You can configure the TFS 2015 build output separate from XAML builds using the new setting build2015Format. Because the default build number scheme is different for TFS 2015 builds (doesn't contain build definition).

The user mapping that I added for the Slack direct messaging notifier can now be used with the ordinary notifiers. Useful for instance if you want a channel message in Slack to generate a Slack notification and get someones attention.

Example format that uses {mappedUser} to generate a Slack notification.:

build2015Format="Build ({buildReason}) <{buildUrl}|{projectName}/{buildDefinition}-{buildNumber}> triggered by <@{mappedUser}> ({buildDuration})."

Check out notification formatting to see available parameters.

Fixes

• A missing buildStatuses in the config was treated as None. I changes so it is treated as All. The same goes for events.
• Comment notifications (TFS 2015) failed if discussionId was missing.

Make sure to pick the correct zip file!

Changelog

TFS 2013 and 2015

Check-in messages are now truncated on newline or commentMaxLength. Work item comments are now truncated on discussionCommentMaxLength (new setting - add it to your config if you're updating).

TFS 2015 only

Three new events added for when someone comments on a check-in, git commit or pull request.

• GitCommitComment
• PullRequestComment
• ChangesetComment

The discussion comment feature exists in both TFS 2013 and 2015, but I couldn't find an event for it in TFS 2013.

The discussion notifications need these three new text formats in the config: commitCommentFormat, pullRequestCommentFormat and changesetCommentFormat.

Changelog

vNext builds (TFS 2015) will now generate BuildCompleted notifications. To make the event handler pick up this event, the dll:s have to also be copied to TFSJobAgent\Plugins in addition to Web Services\bin\Plugins.

The 2015 zip file no longer contains Newtonsoft and HtmlAgilityPack assemblies. Since TFS 2015 are loading them by default, we don't need to add them to the Plugins directory. This gets rid of the "Detected duplicate loading of assembly HtmlAgilityPack" error message in the event log.

No new features added for TFS 2013.

Changelog

New

• A new notifier that can send DMs to Slack users. Slack API is used (instead of incoming webhook) so a Slack bot user with API token is needed. Mapping between domain users and Slack users also needs to be set up. See config file for an example.
• Inheritance of bot settings and rules using the new basedOn attribute.
• Filtering by branch and tag for Git push and pull requests.
• Customizable formatting of Git branch and tag: branchFormat, tagFormat, refSeparator.

Fixes

• Ref update rows pointing to old commits are now ordered according to commit date.
• The natural (alphanumerical) order of tags on the same row was messed up if both lightweight and annotated tags pointing to the same commit was pushed.

Known issues

• The 2015 release won't work on any of the release candidates, only RTM.

Changelog

• BuildSucceeded and BuildFailed events replaced by BuildCompleted.
• A new rule filter buildStatuses has been added to filter statuses.
• WorkItemStateChange and WorkItemAssignmentChange events replaced by WorkItemCreated and WorkItemChanged.
• The new workItemfields rule filter controls which field changes generate a work item changed notification.
• Field transitions now shown in notification for work item changes.
• Which work item fields to display is now configured in bot settings.
• New event WorkItemComment for when someone leaves a comment on a work item.
• New workItemType filter.
• New areaPath filter for work items.
• New teamName filter which applies to most events.
• Fix of change count calculation for Git commits.

If you're upgrading, make sure to update the config file to reflect the event changes and new text strings (workItemFieldTransitionFormat, commentedOn and comment).

Look in the wiki for which filter applies to which event.