commit | 30ef8e2467aeaf9bd1f965e104436e0f97960ab1 | [log] [tgz] |
---|---|---|
author | Rikard Almgren <rikardal@axis.com> | Wed Mar 12 13:56:13 2025 +0100 |
committer | Rikard Almgren <rikardal@axis.com> | Mon Mar 24 10:28:58 2025 +0100 |
tree | 39ed9df177cb47d82b74344225b19194ac82267a | |
parent | 1f36e4d155fc129dbf8a598b960706a4f07a5d21 [diff] |
Add consumers from previous broker API implementations The event-broker lib provides a default brokerapi implementation to facilitate startup before the real implementation is available. We should adopt all consumers that have registered to this or any other previous brokerapi when events-rabbitmq is loaded. This way we can safely load events-rabbitmq after plugins that sets up consumers without loosing events. Added some logging to help understanding load orders. Draws heavy inspiration from events-kafka's implementation. Change-Id: Iaffdbc662bee17de1714cbe19048c2d740805984
Publish gerrit stream events to a RabbitMQ queue. This plugin works with any version of Gerrit starting from v2.8. This plugin also implements most of the events-broker API, so RabbitMQ can be used as a message-broker in a multi-master setup. The one part that is missing is the implementation of the replayAllEvents method. However, this method is not needed by the multi-site plugin.
linux
java-1.8
Bazel
[amqp] uri = amqp://localhost [exchange] name = exchange-for-gerrit-queue [message] routingKey = com.foobar.www.gerrit [gerrit] name = foobar-gerrit hostname = www.foobar.com
3.14 (Freezed)
stable-2.10
master
is permanently latest but would not be updated by author anymore.3.1
3.0
2.0
1.4
1.3
1.2
1.1
monitor.failureCount
1.0
The Apache Software License, Version 2.0
Copyright (c) 2013 rinrinne a.k.a. rin_ne