From 64059f5f47bde5dcb65494b09b88b0e323110b9c Mon Sep 17 00:00:00 2001 From: Edwin Kempin Date: Thu, 31 Oct 2013 13:49:25 +0100 Subject: [PATCH] Document how plugins can listen to stream-events Change-Id: I7db0cab69eb0087ccac186b8ae258ad06eb37ac6 Signed-off-by: Edwin Kempin --- Documentation/cmd-stream-events.txt | 1 + Documentation/dev-plugins.txt | 6 ++++++ 2 files changed, 7 insertions(+) diff --git a/Documentation/cmd-stream-events.txt b/Documentation/cmd-stream-events.txt index 10689b6f47..2a3265e8bf 100644 --- a/Documentation/cmd-stream-events.txt +++ b/Documentation/cmd-stream-events.txt @@ -52,6 +52,7 @@ The currently supported message types are *patchset-created*, Note that any field may be missing in the JSON messages, so consumers of this JSON stream should deal with that appropriately. +[[events]] Events ~~~~~~ Patchset Created diff --git a/Documentation/dev-plugins.txt b/Documentation/dev-plugins.txt index 5e10a622d9..d0e361aded 100644 --- a/Documentation/dev-plugins.txt +++ b/Documentation/dev-plugins.txt @@ -323,6 +323,12 @@ Certain operations in Gerrit trigger events. Plugins may receive notifications of these events by implementing the corresponding listeners. +* `com.google.gerrit.common.ChangeListener`: ++ +Allows to listen to change events. These are the same +link:cmd-stream-events.html#events[events] that are also streamed by +the link:cmd-stream-events.html[gerrit stream-events] command. + * `com.google.gerrit.extensions.events.LifecycleListener`: + Gerrit server startup and shutdown