commit | 6d79a8264547187d9da359e19ebe749cb43c8214 | [log] [tgz] |
---|---|---|
author | Ian Wienand <iwienand@redhat.com> | Thu Jan 28 15:28:21 2021 +1100 |
committer | Ian Wienand <iwienand@redhat.com> | Thu Jan 28 16:28:05 2021 +1100 |
tree | 33517f5020c4138bf906d5d0804ccc6de866e6fd | |
parent | 5e7259d80530c0d1bd696620b07b8bc52b5d18ad [diff] |
Observe change object to handle refresh The "ready()" function isn't quite right; it has been noted that when you navigate between changes the Zuul Summary tab isn't updating and you need a full refresh. I think what we should be doing is observing the change property and building the table in that handler. Change-Id: Id3410c28d2cd8fdb08fc14d755c43f1d2015eaa5
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/gerrit
plugins/zuul-results-summary
`cd plugins; git clone https://gerrit.googlesource.com/plugins/zuul-results-summarycd ..; bazel build plugins/zuul-results-summary:zuul-results-summary
bazel-bin/plugins/zuul-results-summary/zuul-results-summary.js
to Gerrit plugins directory