Felix Edel f8fe86dd7e Switch to ZooKeeper backed merge result events ... This puts the merger result events (MergeCompleted, FilesChanged) into ZooKeeper. This is the first step to put the merge jobs into ZooKeeper, similar to the builds. This doesn't change the logic how the result events are processed. The main change is done in the scheduler callbacks (onMergeCompleted, onFilesChanged) which now put a serializable merge result event into the ZooKeeper result event queue rather than the local queue. The event handler methods are adapted to work with those new events. As the buildset is not serializable in its current state, we provide the buildset UUID to the events and look up the corresponding buildset in the event processing methods based on the provided pipeline and queue. Change-Id: I033cf27bc8035afbd743e37292da37fde6d0e0b8		2021-06-29 14:37:15 -07:00
..
__init__.py	Split the merger into a separate process	2014-02-17 11:47:15 -08:00
client.py	Match tag items against containing branches	2020-03-06 13:29:18 -08:00
merger.py	Switch to ZooKeeper backed merge result events	2021-06-29 14:37:15 -07:00
server.py	Improve component registry	2021-05-17 16:47:13 -07:00