OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [RELENG-45] Notify release list on merge failures https://jira.opendaylight.org/browse/RELENG-45 releng <p>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.</p> <p>Operating System: All<br/> Platform: All</p> RELENG-45 Notify release list on merge failures Bug Open Unresolved Unassigned Colin Dixon Mon, 27 Mar 2017 21:14:47 +0000 Wed, 28 Feb 2018 15:53:25 +0000 unspecified Jenkins Job Builder 0 3 <p>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.</p> <p>&gt; failing merge jobs</p> <p>Where a yellow dot is also considered a failed run.<br/> For example currently on Beryllium, Distribution merge <span class="error">&#91;0&#93;</span> has a red dot, because Tsdr merge <span class="error">&#91;1&#93;</span> has a yellow dot.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/Merge-Beryllium/job/distribution-merge-beryllium/380/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/Merge-Beryllium/job/distribution-merge-beryllium/380/</a><br/> <span class="error">&#91;1&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/Merge-Beryllium/job/tsdr-merge-beryllium/29/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/Merge-Beryllium/job/tsdr-merge-beryllium/29/</a></p> <p>&gt; persistently failing</p> <p>Start with notifying about every failure, and think about filtering out non-persistent failures later?</p> Development External issue ID 8091 External issue URL Rank 0|i01m7j: