Allow to enable Zuul integration per project

Skip parsing the messages, if project wasn't enabled for Zuul.

Expose project config entry to enable the Zuul integration from the
project page.

As the consequence of this change the deployment is changed from
JavaScript to JAR artifact.

Bug: Issue 13980
Change-Id: I85a132565af217b703c93988ed5de7f7628efead
7 files changed
tree: 535ae8be6e5fd3fb7e26f72c78ca53aeda1f8e50
  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.json
  12. 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.js to Gerrit plugins directory