Sirene is not always blinking when a build is in failed state

[TurboPablos]

We're using Sirene of Shame connected to the VSTS and monitoring few projects builds.

When one build (project A) is in failed state, sirene is blinking for the failed build as expected. But, if after that someone has triggered next build (project B), sirene is blinking for the running build as expected as well. If the second build is successfull, sirene is not blinkinig anymore even if the first build for project A is still failed.

It would be nice to remain the Sirene behavior for the failed build if at least one build is in failed state.

[lprichar]

That's a great point! I've mostly only ever watched a small numbers of builds, but I can imagine with many builds the value of the siren would go down. To do it right is a tricky concurrency problem. But perhaps an easy first step is just to remember and then restore the state of the siren when a build is triggered.

[TurboPablos]

First of all- sorry for the delay, many things around to do ;)

Then I want to apreciate all your work, it was a brilliant idea to create this kind of tool like Sirene of Shame :)

What do you think, when can we expect it?