TeamCity 9.1 support

• Bug: HipChat API changed (#59).
• Bug: Faulty 0.9.1 release that included EMMA instrumented code (#56, #57, #58).

TeamCity 9 and proxy support

• Enhancement: TeamCity 9 compatibility, specifically v9.0.2 (#44).
• Bug: Loading emoticons causes an infinite loop, due to un-RESTful HipChat API (#49).
• Feature: New build statistics message template variables (#45):
  ${noOfTests}, ${noOfPassedTests}, ${noOfFailedTests},
  ${noOfNewFailedTests}, ${noOfIgnoredTests} and
  ${durationOfTests}. Other build statistics, e.g. custom
  defined statistics, code duplicates, code coverage, etc.
  can be referenced in a template with the stats. prefix
  within the data model, e.g. ${.data_model["stats.myKey"]}.
  The exact variables will vary, so enable debug logging to
  see what's available in your environment.
• Feature: Proxy support (#46). For setting up TeamCity proxy support
  refer to the online documentation.

Branch filtering

• Bug: Syntax check templates before saving configuration (#39).
• Bug: Server room ID wasn't loaded from config during plugin initialisation.
• Feature: Specify a branch filter for which events must be triggered (#38).
• Feature: Support for testing against a stand-alone HipChat server by bypassing the SSL certificate check (#36).
• Enhancement: Linked the notify on first event check boxes to their parent check boxes.

Note that this release was tested against TeamCity v8.1.5.

HipChat API update

Recently released HipChat client went accord with API changes. This is an update to work against the new API (#35).

Notify on first success or failure events wasn't taking branches into account

• Bug: Notify on first success or failure events wasn't taking branches into account (#34).

Specifying a dedicated room for server events

• Enhancement: Specifying a dedicated room for server events (#33). To keep this backwards compatible, the default build events room will be used if no server events room has been configured.

Bugfix release

• Bug: For large setups, only a 100 rooms were returned to select from (#32).

Template and notification message bug fixes

• Bug: Point the link in the message (default template) to the build configuration rather than the project (#28).
• Bug: Build ID wasn't corrected formatted as a string (#29).
• Bug: Links to a build ID don't require the build type ID anymore, since TeamCity 8 (#30, #31).

Notify on first successful or failed build

• Bug: Large GET request when submitting plugin configuration (due to the templates) can cause a 404 on some setups because of request limits (#26, #27).
• Enhancement: Global setting to only notify on first successful build after a failure, or first failed build after a successful build (#21).

Customisable notification messages

• Bug: Unicode notification message payloads weren't sent as UTF-8 (#20).
• Bug: Race condition during plugin initialisation (during server startup) that sometimes prevented emoticons from being cached (#25).
• Enhancement: Configurable notification message templates, using FreeMarker.
• Enhancement: In addition to configurable templates, any build or agent parameter can now be referenced too (#16).
• Enhancement: Switched from JUnit to TestNG, added EMMA for code coverage analysis and lint4j for static analysis.