Analysis updated 2026-08-08 · repo last pushed 2020-11-03
Build and run the RabbitMQ server from source to test changes across multiple components at once.
Test how a custom plugin interacts with the core broker using a unified development workflow.
Run the full RabbitMQ test suite after making changes to verify nothing is broken.
Develop and test multiple RabbitMQ plugins simultaneously without managing separate repositories.
| rabbitmq/rabbitmq-public-umbrella | dipodidae/resume | ruanyf/notes | |
|---|---|---|---|
| Stars | 32 | 25 | 22 |
| Language | Makefile | Makefile | Makefile |
| Last pushed | 2020-11-03 | — | 2026-06-07 |
| Maintenance | Dormant | — | Maintained |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 3/5 | 2/5 | 1/5 |
| Audience | developer | general | general |
Figures from each repo's GitHub metadata at analysis time.
Requires Erlang to be installed and familiarity with building Erlang projects from source.
RabbitMQ Public Umbrella is a convenience tool for developers who work on RabbitMQ, the popular messaging system that lets different applications communicate with each other. Rather than juggling the many separate pieces that make up RabbitMQ, the core broker, various plugins, client libraries, this repository pulls everything into one place so you can work on multiple components together without managing them individually. The repository is essentially a workspace organizer. When you first set it up, a single command downloads all the related sub-projects into a folder called deps. Each sub-project sits in its own directory with a name that roughly describes what it does. For example, rabbit is the main server, amqp_client is an Erlang-based client library, and rabbit_common is shared code used across multiple pieces. From there, you can build and run the server from source, test individual plugins, or start the broker with specific plugins enabled, all using straightforward build commands. This tool is aimed at people contributing to RabbitMQ itself or building custom plugins for it. If you're a developer who needs to test how a new plugin interacts with the core broker, or you want to run the server's full test suite after making changes, this setup gives you a unified workflow. The README notes that it's no longer required if you're only working on a single plugin, that can be done independently now, but the umbrella remains useful for anyone touching multiple parts of the project at once. One practical detail worth noting: running the full server test suite can take up to two hours depending on your hardware, though a faster subset of essential tests is available. The README also suggests checking whether a snapshot build already exists before going through the effort of building a full distribution from source, since merged changes typically get published as snapshots within minutes to hours.
A workspace tool that pulls together all RabbitMQ source code, the server, plugins, and client libraries, into one folder so developers can build, test, and modify multiple components together without managing them individually.
Mainly Makefile. The stack also includes Erlang, Makefile.
Dormant — no commits in 2+ years (last push 2020-11-03).
No license information is provided in the repository documentation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.