Results 449 comments of netwolfuk

I suspect the same will happen when editing a webhook via the REST api (which is how it works on a project edit page)

I have a fix that looks like it works. I need to get the coverage up on this code, but will try to push later today or tomorrow.

BTW, I found another bug. Copying a project that contains webhooks with specific builds configured does not update those WebHooks with the new buildType ids in the new project.

So it looks like copying a project fires off the `projectCreated` event. There is no "projectCopied" event that I can find. If a project is new, then it won't have...

New commit pushed. It will build soon. No coverage improvements yet, but now has support for deleted builds.

I found another event that might help. `projects.ProjectEventsNotifier - Attempting to publish event about projectExtId TcPlugins3. Cause projectPersisted` This might be useful to speed up the 10 second window (14)....

I've pushed an update with the following changes: 1. Uses a different event `projectPersisted`. From what I can tell, this fires after persist and reload. 2. `projectPersisted` triggers a refresh...

The [build has run](https://teamcity.jetbrains.com/buildConfiguration/WebHooksAndOtherPlugins_TcWebHooks?branch=issue_238-webhooks_not_showing_when_project_copied&buildTypeTab=overview&mode=builds). oooh, it's build 500. Exciting.

I forgot to say that the logs look like this... ``` INFO - jetbrains.buildServer.SERVER - WebHookSettingsManagerImpl :: WebHook uniqueId selected as candidate for updating to avoid conflict with existing webhooks....

> Checking... This branch includes the fixes for https://github.com/tcplugins/tcWebHooks/issues/238 as well, yeah? Yes, it's supposed to, unless I have introduced a regression