I'm running go-server 17.2.0. For some pipelines, I get subject lines like "Stage [xxx/16/build/1] failed" in my notification email, even though xxx/15 passed. For other pipelines, I get "is broken" as expected on a red build after a green.
Since the teams want to get notifications for all the pipelines in their pipeline group etc without subscribing to notifications for each of them, I have a little mail server which subscribes to all events and then look at the email subject line and go/api/config/pipeline_groups to figure out who should get what. (See https://github.com/magnus-lycka/mail2alert ) This means that I don't know whether or not the go-server respects the rules in https://docs.gocd.io/17.5.0/configuration/dev_notifications.html#events wrt to sending email or not, I just know that the subject line on broken jobs for some piplines contains "failed" instead of "is broken"!, whether or not the previous run passed, while for other pipelines, this seems to work as expected. Any ideas? -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
