summaryrefslogtreecommitdiff
path: root/zuul/driver/mqtt/mqttreporter.py
diff options
context:
space:
mode:
authorJames E. Blair <jim@acmegating.com>2021-06-18 15:07:18 -0700
committerJames E. Blair <jim@acmegating.com>2021-06-18 15:07:18 -0700
commit3fbd61c0d5ccc7c35320a3770b687797a97a693e (patch)
treefa31bdce2a559e24649e1db175149c3d191bc301 /zuul/driver/mqtt/mqttreporter.py
parent0a5e330891655e4842cced250761b95ecbfdfe42 (diff)
downloadzuul-3fbd61c0d5ccc7c35320a3770b687797a97a693e.tar.gz
Add item UUID to MQTT reporter
Since the MQTT reporter can be used to emit start or enqueue events, it may be useful to match enqueue and dequeue events. That could be done with tenant+pipeline+change+patchset, but we also have a UUID for queue items, so to make it simpler for MQTT consumers, let's expose that. Change-Id: Iff88bcfd73e00f292e0cc947f548582a276a7975
Diffstat (limited to 'zuul/driver/mqtt/mqttreporter.py')
-rw-r--r--zuul/driver/mqtt/mqttreporter.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/zuul/driver/mqtt/mqttreporter.py b/zuul/driver/mqtt/mqttreporter.py
index 3376f1866..a53389337 100644
--- a/zuul/driver/mqtt/mqttreporter.py
+++ b/zuul/driver/mqtt/mqttreporter.py
@@ -48,6 +48,7 @@ class MQTTReporter(BaseReporter):
item, with_jobs=False),
'trigger_time': item.event.timestamp,
'enqueue_time': item.enqueue_time,
+ 'uuid': item.uuid,
'buildset': {
'uuid': item.current_build_set.uuid,
'result': item.current_build_set.result,