| commit | 22c516608dd4952eb8b102166a4a282e27c5f5e3 | [log] [tgz] |
|---|---|---|
| author | Ian Wienand <iwienand@redhat.com> | Wed Feb 24 14:32:16 2021 +1100 |
| committer | Ian Wienand <iwienand@redhat.com> | Wed Feb 24 16:33:58 2021 +1100 |
| tree | c1380bfc2e73ddf6d29a52155e8451696e71cf12 | |
| parent | 90f0f7cc6c97683ade0c9eeda3a644364f9649ea [diff] |
Handle SKIPPED state better
The SKIPPED results have a fake URL and no run-time.
Make the run-time part of the match optional so we start matching
these lines.
Because the URL is fake, null the result for SKIPPED matches so the
job name won't be a link to nowhere.
Put a secondary-color span around the job name in the null case so
it's a bit more obvious it was skipped.
A weird thing with the CSS matchers is that "first-child" doesn't work
with the templating "dom-if" we use. "first-child" seems to refer to
the "if={{job.link}}" template tag -- so it works when job.link is
defined, but when it is not, the "if={{!job.link}}" *isn't* the first
child, despite being the only thing displayed. Anyway,
"first-of-type" seems more like what we want -- the first <td> element
no matter what ... that should always be the first column. Update
that match.
Change-Id: I5c3bed85d7f64cd0890757237f93d13406c33788
Polygerrit plugin to show a summary of Zuul results in a change tab
Results are show in reverse chronological order, additionally sorted by CI userid's in ZUUL_PRIORITY (earlier entry in the list means sorted first in the output table). i.e. if you consider one of your CI reporters to be the main one, you should place it first in this list.
UI tests are still a work in progress
git clone https://gerrit.googlesource.com/gerritplugins/zuul-results-summary `cd plugins; git clone https://gerrit.googlesource.com/plugins/zuul-results-summarycd ..; bazel build plugins/zuul-results-summary:zuul-results-summarybazel-bin/plugins/zuul-results-summary/zuul-results-summary.js to Gerrit plugins directory