Issue

There have been multiple cases where the promotion of Neutron component jobs was blocked or failing for extended periods (sometimes weeks) without being noticed by Neutron team members or others.

During a recent Neutron meeting, mtomaska@redhat.com raised this as a recurring issue.

In past OSP versions (before RHOSO 18), we received email notifications via UMB messages from `rhos-qe-jenkins` jobs. Over the years, this proved useful for quickly identifying and addressing issues during the compose phases, as relevant CI results were available.

Goal

This epic aims to establish a similar or improved notification mechanism to promptly alert our DFG about failures blocking Neutron component promotion. The goal is to minimize response time for addressing CI, DevOps, test, and component-related issues.

Proposed Solution

After consulting with bcafarel@redhat.com and reviewing UMB and slack bot documentation, as well as exploring ideas on how to leverage both, I believe implementing a slack bot would be the most efficient approach.
I have already made a plan for a Python-based solution that fetches promotion results by zuul API, parses them, and sends notifications via Slack.
This may ensure failures are detected and addressed quickly by our DFG.