A new version (0.7.25.115) of the tcWebHooks plugin is available.
With the recent release of Teamcity 6.5, some assumptions I was making about the prototype javascript functions proved incorrect. I think the newer version is stricter with badly named functions, or perhaps teamcity has changed some of their internal functions on which I was mistakenly relying.
This release fixes those bugs and also fixes a long standing oversight in the lack of checking of the URL and payload formats when submitting the form. Now, when trying to add a webhook with no url or no payload format selected you are prompted before the dialog goes away. Previously, the dialog would just close and no webhook would be added. It ended up being that my jsp was not setting the content type to text/xml, so the javascript error listener was never firing.
As usual, get the latest from sourceforge. If you find a bug please leave a comment below, or on the bugs page.
Very nice work!
I use this plug-in to call a service, temporarily enabling/disabling push during build. But I noticed that the event for BuildStarted and BuildCompleted are triggered for each build configuration in a project, but what I would like are events for when the complete project starts a build and is finished building all it’s build configurations. Is there a solution to this, or any new events that you can add to solve this problem?
Best regards,
Joel
Hi Joel. thanks for your feedback.
If I understand your comment correctly, you have a set of builds in your project that have dependencies on each other, and you want to know when the dependency chain starts and finishes?
I’ve had a quick look at the API docs for teamcity and I can’t see how it would be possible to add that based on the events available.
I suspect you’d have to add some logic to your webhook endpoint to figure out where in the chain it is. Perhaps by looking at the trigger reason. It’d be difficult though, as you could enter the chain at any point. It might not always be the first build that triggered the chain.
Or are you referring to a single build with multiple build steps?
If so, I thought that build steps were considered part of a single build. Admittedly I’ve not done much testing with build steps.
Very nice indeed! I’m using it to feed our build bunny.
Our Nabaztag had been quiet ever since Mindscape went bust. But a new Ruby server has been written which listens for tcWebHooks and breathes new life into the every developers favourite rabbit.
https://github.com/quimarche/trudy
That’s very cool. Thanks for the feedback Chris.
Hi,
This is a handy plugin. Does TeamCity provide the flexibility to allow for webhooks per Build Configuration in addition to Project level? I know the plugin doesn’t currently support that but Build-Config level webhooks could be very valuable and also solve Joel’s problem above.
Thanks
Thanks for your comment Frank.
Yes, it’s certainly possible. To be honest, the main reason I’ve not done it is because I’ve not come up with a way of implementing it without making the ui cluttered.
Any suggestions?
Any plans for switching to the new zip-based package format?
Also I was really looking forward to using tcWebHooks in our new TC7 install, but it just crashes, any TC7 supported builds?
The other projects use the zip format. I haven’t done that yet for tcWebhooks.
TC 7 is still in EAP, so I’ve not looked at that yet. Thanks for the reminder.
Hi Patrik, can you tell me more about your crashes? It worked for me on TC7.
There is a problem where events fire without fully populated details, and that is causing a stacktrace to appear in the logs, but that is only for Responsibility changes. The other events should work. I have alerted the TeamCity developers.
Hi,
We’ve been using your tcWebHooks plugin (latest version) for HipChat integration and it’s been great. Thanks for making it.
However, since upgrading to TeamCity 6.5.6 we’ve been getting this exception: https://gist.github.com/1677782
Is tcWebHooks known to work with the latest production TeamCity?
Thanks,
Josh
Hi Josh.
tcWebHooks 0.7.25.115 works for me on TeamCity 6.5.6.
Looking at your error log, it appears that the plugin is installed inside the teamcity webapp WEB-INF/lib folder. Please remove the jar from the lib folder and install the plugin in your .BuildServer/plugins/ folder inside a sub-folder called “tcWebHooks” (or something similar).
The .BuildServer folder will be in your user’s profile folder, unless you are directing Teamcity to locate it somewhere else with a startup flag.
Full docs are at: http://sourceforge.net/apps/trac/tcplugins/wiki/TcWebHooks
Thanks for the help. I missed the subfolder bit. It’s working now. Thanks!