Hi Sudarshan Purohit,

Thank you for the insights on my request. I’ll try this workaround, but it would be great if this parameterization could also be supported through the UI.

Regards,

Jerin

Aegean Rabbit: Of course. We'll work on that support. Could you help by confirming:

* You're using Pipeline notifications and not the newer Centralized Notifications.

* Which notification channels (Email, Slack, Webhook...) you use the most frequently? We'll order the work accordingly.

Hi Sudarshan Purohit Abhishek Thamman,

Could you please check the below mentioned yaml is acceptable with respect to notification. I had a try and couldn't get the notification while trying to detect failures for one of the important CI step, named Checkmarx (which is based on a stepgroup template having checkmarx scan and SCA) among 7 steps. As I didn't find the documentation for this, I was unsure if I am missing something. Would be great if you can share the documentation url for this or would like to have a call based on your feasibility to show the live scenario. Thanks!

Regards,

Jerin

Hi Sudarshan Purohit,

Thank you for the prompt response and action. I can confirm that we are actively using pipeline notifications and frequently rely on the Email notification channel.

Regards,

Jerin

Aegean Rabbit, we don't currently support the Conditions keyword for notifications, so the step failed notification would get sent for all step failures (typically there's just one failure, so there would be one of these per pipeline).

We suggest filtering or additional actions on the recipient side for Notifications (for example, searching for the "checkmarx" keyword in the notification emails.

Hi Sudarshan Purohit,

Thank you for the response. Within the CI stage, I have multiple steps, including SonarQube and Checkmarx scans. I want failures from SonarQube to be routed to the DevOps team email DL, and similarly, Checkmarx failures to be sent to the security team email DL. I considered using parameterized inputs along with separate notification rules to achieve this. However, the main challenge I'm facing is filtering and isolating the individual step failures to trigger the appropriate notifications.

Could you please elaborate some more insights about this pointer --> We suggest filtering or additional actions on the recipient side for Notifications (for example, searching for the "checkmarx" keyword in the notification emails.

Regards,

Jerin

Hi Sudarshan Purohit,

Just following up-Could you please share your insights on the request above?

Regards,

Jerin

Hi Abhishek Thamman Sudarshan Purohit,

Kindly take a look. Thanks

Regards,

Jerin

Aegean Rabbit: Hello, regarding my previous comment, I meant that the notification system would send all step failures (not just only Checkmarx or SonarQube) to a notification target, and the system that receives all the notifications, does additional filtering of keywords to understand what kind of failure it was.

An alternative method here is to have different stages for SonarQube and CheckMarx, and have different endpoints/notfication templates for these two stage failures. This will get you exactly the flow mentioned earlier.

Hi Abhishek Thamman,

Yes. We have a standard golden template which is being utilized by many project teams and having this email notification method-channel type -->Type emails of your recipients, within "Notify" as runtime input helps to notify pipeline events to respective team DL's. Having this as hardcoded blocking our delivery and instead forced to create multiple templates for each project, which is a deviation of template reusability. Appreciate your prompt action on my request.

Regards,

Jerin

Aegean Rabbit: Makes sense. Thanks for the details.