opendev/gerrit
Code Issues Proposed changes

Document how plugins can listen to stream-events

Browse Source 
Change-Id: I7db0cab69eb0087ccac186b8ae258ad06eb37ac6
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
This commit is contained in:
Edwin Kempin
2013-10-31 13:49:25 +01:00
parent 84487d5f79
commit 64059f5f47
2 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Documentation/cmd-stream-events.txt
View File

@@ -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 Note that any field may be missing in the JSON messages, so consumers of
this JSON stream should deal with that appropriately. this JSON stream should deal with that appropriately.
[[events]]
Events Events
~~~~~~ ~~~~~~
Patchset Created Patchset Created

6
Documentation/dev-plugins.txt
View File

@@ -323,6 +323,12 @@ Certain operations in Gerrit trigger events. Plugins may receive
notifications of these events by implementing the corresponding notifications of these events by implementing the corresponding
listeners. 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`: * `com.google.gerrit.extensions.events.LifecycleListener`:
+ +
Gerrit server startup and shutdown Gerrit server startup and shutdown