Closed sergey-prosvirnin closed 4 years ago
Could you check Administration -> Diagnostics -> Server Logs -> teamcity-server.log for any related to Slack errors?
Is notifications broken since update to 1.5.1?
Is notifications broken since update to 1.5.1?
No, it's still 1.5.0. I was trying to find a solution to the problem in the update.
Could you check Administration -> Diagnostics -> Server Logs -> teamcity-server.log for any related to Slack errors?
I looked quickly and found no Slack errors.
Could you attach screenshot with Slack build configuration? (Press Edit near Try it)
Could you attach screenshot with Slack build configuration? (Press Edit near Try it)
Please look at #21 and #25
You should specify branch name according to the names you see in TeamCity build info.
I guess in your case correct name for Branch field is development
Unfortunately, that option didn't help me.
What branch name do you see in build history list?
I guess I didn't quite get it right where it was.
As you can see, TeamCity does not parse branch name.
I see the names of the repositories in the build log.
You should edit VCS root and specify correct branch specification
Unfortunately, these actions have not been successful.
as a result you can now find the branch name on build page
Feel free to reopen if needed
I have TeamCity Professional 2019.2.1 (build 71758) in which I used to have successful notifications when building successfully in Slack. But now they have stopped working. At the same time Try It function successfully works and sends test notifications to Slack.
Plugin version: 1.5.1 Java version: 13.0.2 OS: Ubuntu 16.04