netwolfuk

Hi @buumi I finally has a chance to look at this with a build that has changes from multiple VCS's. In my opinion we have a few issues here: Firstly,...

BTW, this issue can be reproduced with any change. It doesn't have to have multiple VCS's

Yes. You're right. That data is not available to the templating engine. Once it's added it would be accessible via methods available to the velocity templates. I just need to...

Depends on #31

Hi @Swoorup I have added preliminary support for accessing the build object (SBuild) via Velocity. Please [try a build from this branch,](https://teamcity.jetbrains.com/buildConfiguration/WebHooksAndOtherPlugins_TcWebHooks?branch=issue_31-add_more_items_to_velocity_payload&buildTypeTab=overview) and create a template using the example on...

Will you wait for a release that's not alpha (no ETA yet) or do you mean when that branch is merged to master and `1.2.0alpha-3` is released?

Ok, I'll leave this ticket open until 1.2 is released. Yeah. That would be pretty simple in velocity

This is available for testing in the [v1.2.0-alpha.3](https://github.com/tcplugins/tcWebHooks/releases/tag/v1.2.0-alpha.3) release.

I'm not sure what you are expecting to see. Can you please give more detail?

Ah, I see what you mean. Although the `buildStatus` and `notifyType` do clarify that the build was cancelled (interrupted). ``` "buildStatus": "Canceled (Tests passed: 41; exit code 137 (new))", "buildResult":...