This commit ensures elastic-recheck is able to support zuul v2 and v3
simultaneously:
- Add message queries based on v3 completion messages
- Include job-output.txt where console.html was expected
Change-Id: If3d7990d892a9698a112d9ff1dd5160998a4efe6
Depends-On: I7e34206d7968bf128e140468b9a222ecbce3a8f1
The Elasticsearch schema was updated to make the file portion of tags
the basename of filename. This allows us to use tags to filter for files
with a common basename instead of searching with globs in the filename
field. This should be more performant and easier to read.
Change-Id: I8fe36c56309ea851afd63f08f65583008fa4857f
clean up 4 queries which were matching across the entire e-r index
and instead restrict them to the files where they results were
actually found. This will hopefully adjust the load on the ES
cluster.
Change-Id: Ic999039d5f896f632987fcb87f3a3469596972ed
Depending on exactly at what point a build in Jenkins is aborted,
sometimes it can end up with a result of FAILURE. Since logstash
gets its data from Jenkins rather than Zuul, it doesn't know the
build has aborted.
Since ER gets its data from logstash, it also doesn't know that
some failures are actually just aborted builds. We want to know
that we should ignore these failures for classification rate
purposes, but we should not display them on the graph page as they
are not actionable bugs.
Change-Id: If381e36144ffc03c0e36d3eb74ad7f24db245aa6
Can't see this bug on the elastic recheck page. trying
a simpler query (714 hits in last 48 hours)
Change-Id: Ie19e3ea5f68e6e3350469c11e56d599fa3067619
David Moreau-Simard