This release is another alpha and is primarily a bugfix release fixing two issues and a regression. It also includes a more enhanced History view to monitor webhook activity. REST API plugin fixes for those running TeamCity on Windows. Major HttpClient upgrade to resolve compatibility issues with Discord. Reapply PR #25 (regression) Bug Fixes REST API on Windows In alpha13, The REST API plugin would not start on windows and the Jar Cleaner tool is not successful on Windows hosts due to file locking issues. This release (alpha 14) fixes the REST plugin startup issue (thanks @Hakon) and provides better feedback for when the jaxb jars cannot be removed due to file locking on windows (thanks @padawahn) HttpClient upgrade HttpClient is the library on which WebHooks is based. It is responsible for actually making the WebHook POST request and handling message content, authentication, proxying, etc. This release migrates from HttpClient 3.x to 4.5.4. This resolves an issue with webhook requests to Discord being denied. Please raise an issue if you see connectivity problems or unexpected behaviour with tcWebHooks POSTing to endpoints which previously worked using the old 3.x library. Reapply PR #25 (regression) Somehow this was lost in the move from 0.9 to 1.1 New Features WebHook reporting is now available in the TeamCity admin section on the WebHooks tab and more at /webhooks/history.html?view=errors. It's also possible to view all, ok and skipped webhooks in the history. Just click the relevant number in the boxes at the top. Up to the last 10,000 webhook executions are stored in memory in TeamCity. These are discarded on TeamCity restart. The history page is available for any user to view. However, if a user is not granted the Project Edit role on the project that triggered the webhook, then the URL is partially hidden so as not to reveal API keys etc.
↧