tcSlackBuildNotifier icon indicating copy to clipboard operation
tcSlackBuildNotifier copied to clipboard

Failed to Start builds are never "fixed"

Open staffan-einarsson opened this issue 8 years ago • 1 comments

This is an issue relating to consistency. When a build fails after it has started, the Only trigger when build changes from Failure to Success works as expected.

However, if a build fails to start, for example due to incorrect build configuration, the first success after the failure does not trigger a notification. The consistency problem is that Failed to Start is considered a Failure when a failure notification is sent, but not considered a Failure when fix notification is to be sent.

staffan-einarsson avatar Sep 20 '16 06:09 staffan-einarsson

Thanks for participating!

I will take a look when I got some time :)

marvin-w avatar Oct 25 '16 16:10 marvin-w