[RELENG-45] Notify release list on merge failures Created: 27/Mar/17 Updated: 28/Feb/18 |
|
| Status: | Open |
| Project: | releng |
| Component/s: | Jenkins Job Builder |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Colin Dixon | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8091 |
| Description |
|
Given that persistently failing merge jobs can break the entire release by braking distribution check jobs when their artifacts age out of Nexus. The result is that having some notification of failed merge jobs seems important. At the very least when the periodic run of the merge job happens, we should e-mail release. |
| Comments |
| Comment by Thanh Ha (zxiiro) [ 27/Mar/17 ] |
|
We should only send the email for jobs that are participating in autorelease as there are projects that are inactive and not participating that regularly fail and we don't want them to spam the release list. |
| Comment by Vratko Polak [ 30/Mar/17 ] |
|
> failing merge jobs Where a yellow dot is also considered a failed run. [0] https://jenkins.opendaylight.org/releng/view/Merge-Beryllium/job/distribution-merge-beryllium/380/ > persistently failing Start with notifying about every failure, and think about filtering out non-persistent failures later? |