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
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
This bug should never get reported back to gerrit or irc, this is for
tracking our classification rate. Bug 1270309 is about how if jenkins
interrupts a job (think gate reset) the job gets marked as FAILED
instead of incomplete or something.
Change-Id: I424a03840b0a3e691c46a03872b7e99f5865c1df
David Moreau-Simard