Now that ussuri is released, use it for stable release and move train to
previous release dashboard
Change-Id: Ic45da0cfe9a6efbc8df5187c758cba727c773a38
Update listed jobs to be close to master dashboard when relevant and add
some stable-specific jobs
Add master dashboard enhancements like TIMED_OUT count
Fix dashboards description formatting and content
Change-Id: I22cf934898dd357f5e96eb068d6eed6e2fa987ce
Updated neutron-stable-minusone.yaml and
neutron-stable-minustwo.yaml now that stable/train exists.
Change-Id: Id10d4093da162a4496ab0f8aa050d580167bac98
Now that Stein is officially released, update the stable dashboards to
point to the the new latest and previous releases
Also remove periodic jobs that only run on master
Change-Id: I63f6eb47e0fc03f1147f6a1b0a95ab5c935a0fab
Neutron has test failure dashboards not just for the current HEAD, but
for the most recent release and the one before that. The HEAD dashboard
was revamped, and this brings the dashboards for the stable releases
into line with that. Also it bumps the versions now that stable/rocky
is about to be the current release.
Change-Id: Ic06660e32a37643420b610529f0eb34938c9887c
In the Neutron CI meeting [1] it was discussed that failures on CI jobs
for stable branches were not getting sufficient visibility, because
the lack of dashboarding means that we are dealing with anecdotal data
as opposed to trended metrics. This change adds "back one" and "back
two" dashboards (referring to stable/queens and stable/pike
respectively) that can persistently refer to the last two stable
releases, and will be updated with each release to refer to the proper
stable branches.
[1] http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-06-19-16.00.log.html#l-70
Change-Id: I8a372ffe640ef1125e6acc2d5e40ef54c9f8e261
