Feature: Enable selection of all CI pipelines at once when the Environment filter is applied in Notifications.

[kamal-devtron]

🔖 Feature description

While configuring notifications at the environment level, users can select all current and future pipelines for deployment notifications. However, the same functionality is not available for build notifications.

PRs

• feat: Enable selection of all CI pipelines at once when the Environment filter is applied in Notifications notifier#130
• https://github.com/devtron-labs/devtron-enterprise/pull/2699
• feat: Enable selection of all CI pipelines at once when the Environment filter is applied in Notifications #6526

Flag (orches)

ENABLE_NOTIFIER_V2 = "true"
It will enable the new endpoint, notification should work in either way, flag on/off

Dev Tasks

• Basic Files Refactoring/Restructuring in Notifier
• Refactoring in NotificationRestHandler and Service - Orchestrator
• Migrate unique matching logic from notifier to orchestrator
• Implement new repository and service in orchestrator
• Env based CI filtering
• Add new API endpoint in notifier
• Update event client to support new payload

✅ Test Cases Checklist

CI (Build) Pipeline Events:

• CI Trigger (when build starts)
• CI Success
• CI Failure

CD (Deployment) Pipeline Events:

• CD Trigger (when deployment starts)
• CD Success
• CD Failure

Pre/Post CD Events:

• PRE-CD Events
• POST-CD Events

Approval Events:

• Deployment Approval
• Configuration Approval
• Artifact Promotion Approval

Security Events:

• Image Scanning (vulnerability scan results)

Pipeline Status Events:

• Blocked (when pipeline is blocked)

Scoop Events:

• Scoop Notification (EventType = 9)

🎤 Pitch / Usecases

By implementing this feature, users can ensure that all build notifications are consistently configured at the environment level without manual intervention. This will improve efficiency, reduce configuration overhead, and prevent missed notifications for newly created pipelines.

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct