aolszowka/ccnet-hipchat-v2-publisher

A Simple CruiseControl.NET HipChat v2 Publisher

ccnet-hipchat-v2-publisher's Issues

@Mentions Do Not Work

Issue

If an Integration Fails the CruiseControl.NET FailureUsers (usually the version control usernames from the failing commit) are posted to the room with an @mention, however they are not linked.

Resolution

This is a limitation of the Send room notification API with regards to HTML messages. There is a feature request on their site here please help by voting.

Installing The Plugin Causes A System.BadImageFormatException

Issue

After installing the ccnet-hipchat-v2-publisher CruiseControl.NET (Console/Service/Validator) crashes on startup with a System.BadImageFormatException.

Resolution

This is a known issue and is related to the plug-in requiring .NET 4.5+, ensure that you've added the appropriate supportedRuntime tag as per the README.md.

Publish Room Notifications To Multiple Rooms

It would be nice to publish Integration results to multiple rooms.

Plugin Does Not Work With Version X of CruiseControl.NET

Issue

The plugin does not work with version X of CruiseControl.NET

Resolution

This is by design, if you wish to use a different version of CruiseControl.NET feel free to fork the project.

Cross Reference of FailureUsers to HipChat Names

Request

Currently the FailureUsers as reported by CruiseControl.NET are what is published, this is usually the username from the version control system. This doesn't always jive up with what is in HipChat, a Cross Reference of some sort could fix this issue.

Response

In my opinion this is better suited to HipChat's side, otherwise there would be a maintenance nightmare. It seems like something like Alias is the answer. However until Issue #1 (@Mentions do not work) is fixed this doesn't make a whole lot of sense to invest into unless some functionality to message users directly was added.

Out of the Box Customization of Failure/Fixed/Success Messages

Request

It would be nice to offer out of the box customization of Failure/Fixed/Success

Response

Its not quite as simple as it seems, we'd probably want to have some keywords to allow for replacement of things like $(ProjectName), $(Status), and $(FailureUsers)``` probably beyond the scope of what I'm willing to do right now. I'd be interested to see a pull request though.

Publishing to Custom HipChat URLs

Request

The ability to publish to custom HipChat URLs (on-site HipChat Server)

Response

I don't think it'd be too hard to do this, but just not needed right now, simply adding an additional property and then changing the constructor used to create a new ApiConnection should be straightforward. Any change should keep the functionality optional, and assume by default to be using HipChat's cloud servers.