gerrit stream-events - Monitor events occuring in real time
Provides a portal into the major events occuring on the server, outputing activity data in real-time to the client. Events are filtered by the caller's access permissions, ensuring the caller only receives events for changes they can view on the web, or in the project repository.
Event output is in JSON, one event per line.
Any user who has configured an SSH key.
This command is intended to be used in scripts.
$ ssh -p 29418 review.example.com gerrit stream-events
{"type":"comment-added",change:{"project":"tools/gerrit", ...}, ...}
{"type":"comment-added",change:{"project":"tools/gerrit", ...}, ...}
The JSON messages consist of nested objects referencing the change, patchset, account involved, and other attributes as appropriate. The currently supported message types are patchset-added, comment-added, change-merged, and change-abandoned.
Note that any field may be missing in the JSON messages, so consumers of this JSON stream should deal with that appropriately.
| type | "patchset-added" |
| change | change attribute |
| patchset | patchset attribute |
| type | "change-abandoned" |
| change | change attribute |
| patchset | patchset attribute |
| abandoner | account attribute |
| type | "change-merged" |
| change | change attribute |
| patchset | patchset attribute |
| submitter | account attribute |
| type | "comment-added" |
| change | change attribute |
| patchset | patchset attribute |
| author | account attribute |
| comment | Comment text author had written |
Attributes are part events to give context related to the event.
| change |
The Gerrit change the event is related to
|
Part of Gerrit Code Review