Add package-lock.json file

Lockfiles are required to ensure we have visibility into builds,
checksum verification and accurate vulnerability scanning. The file was
generated by running `npm install`.

Google-Bug-Id: b/275121168
Change-Id: I58790e740356008f855790fc64750c2ed66218d5
1 file changed
tree: f246df24bf728f209eeaddc796eda4fc80c2c7cc
  1. java/
  2. resources/
  3. zuul-results-summary/
  4. .eslintignore
  5. .eslintrc.json
  6. .gitignore
  7. .gitreview
  8. bower.json
  9. BUILD
  10. LICENSE
  11. package-lock.json
  12. package.json
  13. README.md
README.md

Zuul Results Summary

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

UI tests are still a work in progress

Test plugin on Gerrit

  1. Clone gerrit git clone https://gerrit.googlesource.com/gerrit
  2. Clone plugin to plugins/zuul-results-summary `cd plugins; git clone https://gerrit.googlesource.com/plugins/zuul-results-summary
  3. Run build cd ..; bazel build plugins/zuul-results-summary:zuul-results-summary
  4. Copy resulting plugin bazel-bin/plugins/zuul-results-summary/zuul-results-summary.jar to Gerrit plugins directory
  5. Issue a reload ssh -p 29418 admin@<host> gerrit plugin reload zuul-results-summary