Clarify sorting
diff --git a/README.md b/README.md
index 2b93288..fa8eed9 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,12 @@
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
To run UI tests here will need install dependencies from both npm and bower.
diff --git a/zuul-results-summary/zuul-results-summary.js b/zuul-results-summary/zuul-results-summary.js
index 5de9e0a..b4bd3f7 100644
--- a/zuul-results-summary/zuul-results-summary.js
+++ b/zuul-results-summary/zuul-results-summary.js
@@ -12,6 +12,8 @@
// License for the specific language governing permissions and limitations
// under the License.
+
+// TODO(ianw) : find some way to make this configurable
const ZUUL_PRIORITY = [22348];
/*
@@ -106,15 +108,13 @@
}
_get_status_and_pipeline(message) {
- /* Look for the full Zuul-3ish build status message, e.g.:
- * Build succeeded (check pipeline).
- */
+ // Look for the full Zuul-3ish build status message, e.g.:
+ // Build succeeded (check pipeline).
const statusRe = /^Build (?<status>\w+) \((?<pipeline>[\w]+) pipeline\)\./gm;
let statusMatch = statusRe.exec(message.message);
if (!statusMatch) {
- /* Match non-pipeline CI comments, e.g.:
- * Build succeeded.
- */
+ // Match non-pipeline CI comments, e.g.:
+ // Build succeeded.
const statusRe = /^Build (?<status>\w+)\./gm;
statusMatch = statusRe.exec(message.message);
}
@@ -254,7 +254,6 @@
/*
* Install plugin
*/
-
Gerrit.install(plugin => {
'use strict';
