From c026c7a3f058ba60bcf765db61771b7854303598 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Wed, 16 Sep 2015 09:04:14 -0700 Subject: [PATCH] Process ZUUL_VOTING parameter Read the ZUUL_VOTING parameter and add to the event before posting for log processing. The plan is that elastic-recheck will eventually use this field for filtering out non-voting jobs from the e-r uncategorized bugs page. Depends-On: I40746bb77aab900c1dd2637f940c14f72a904a61 Change-Id: I1f3c2a65104db39fdd7d786d421cded1b436a5f6 --- log_processor/client.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/log_processor/client.py b/log_processor/client.py index 8f5e985..2472c00 100644 --- a/log_processor/client.py +++ b/log_processor/client.py @@ -106,6 +106,8 @@ class EventProcessor(threading.Thread): fields["build_master"] = event["build"].get("host_name", "UNKNOWN") parameters = event["build"].get("parameters", {}) fields["project"] = parameters.get("ZUUL_PROJECT", "UNKNOWN") + # The voting value is "1" for voting, "0" for non-voting + fields["voting"] = parameters.get("ZUUL_VOTING", "UNKNOWN") # TODO(clarkb) can we do better without duplicated data here? fields["build_uuid"] = parameters.get("ZUUL_UUID", "UNKNOWN") fields["build_short_uuid"] = fields["build_uuid"][:7]