| commit | 77426fde2e228e8012c3ac6d7e82efa6203498f1 | [log] [tgz] |
|---|---|---|
| author | Matthias Sohn <matthias.sohn@sap.com> | Thu Dec 01 01:09:49 2022 +0100 |
| committer | Matthias Sohn <matthias.sohn@sap.com> | Wed Dec 21 10:09:05 2022 +0100 |
| tree | a284e68270ebd131ea37f4c81350e8c0155c72d1 | |
| parent | 37e87c8f6688939d5e583aefa3dbeab358b30732 [diff] |
Fix deserialization of Event from raw message
This plugins allows to define a distributed stream of events published by Gerrit.
Events can be anything, from the traditional stream events to the Gerrit metrics.
This plugin requires Gerrit 3.6 or later.
linuxjava-11Bazelevents-nats plugin can be build as a regular ‘in-tree’ plugin. That means that is required to clone a Gerrit source tree first and then to have the events-nats plugin source directory into the /plugins path. Additionally, the plugins/external_plugin_deps.bzl file needs to be updated to match the events-nats plugin one.
git clone --recursive https://gerrit.googlesource.com/gerrit git clone https://gerrit.googlesource.com/plugins/events-nats gerrit/plugins/events-nats cd gerrit rm plugins/external_plugin_deps.bzl ln -s ./events-nats/external_plugin_deps.bzl plugins/.
To build the events-nats plugins, issue the command from the Gerrit source path:
bazel build plugins/events-nats
The output is created in
bazel-genfiles/plugins/events-nats/events-nats.jar
Assuming a running NATS JetStream broker on the same Gerrit host, add the following settings to gerrit.config:
[plugin "events-nats"]
server = nats://localhost:4222
Starting a local NATS JetStream server for testing:
docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats -js
You can use the NATS command line client to inspect and manage NATS.