Menu

Snapshots Releases

RabbitMQ server builds that successfully went through our CI pipeline are published. These builds are available so that users can try out the latest features and bug fixes as soon as they become available.

Stability and Suitability of Snapshot Builds

Snapshot builds are produced from all supported release series branches and from the 'master' branch which will become the next feature release.

In the case of the 'master' branch, this represents the bleeding edge and therefore should not be considered complete (finished) or stable. It is quite possible that existing features, APIs and/or configuration data formats have been changed in ways that are not backwards compatible or even removed altogether.

In addition to the changes described above, it is also possible that incompatible changes have been made to the way persistent storage is handled. Such changes may mean that after installing a snapshot, your RabbitMQ installation cannot be rolled back to a previous (stable) version. To avoid conflicting with the existing installation, you should either remove it first, or configure the snapshot installation to use an alternative location for its persistent storage and (potentially) other configuration elements using the provided instructions.

Snapshot releases therefore are suitable for development and some QA environments but not intended to be used in production.

Documentation of the 'master' branch

Documentation for master branch of the broker is continuously published to next.rabbitmq.com. Note that master documentation can lag behind code changes, sometimes intentionally so.

Downloads and Installation

As with our published live releases, we continue to digitally sign the snapshot artefacts using GnuPG and our release public signing key.

Direct Downloads

All snapshot artefacts, indexed by their version, are available in the all-dev repository on Bintray:

Debian repository

Packages for many Debian-based Linux distributions are available from a Bintray repository called debian-dev.

You can use Debian components to select exactly what you want:

main
Gives access to all snapshots we produce, not only the RabbitMQ server.
rabbitmq
Gives access to all snapshots of the RabbitMQ server, no matter the branch.
rabbitmq-v3.6.x
Gives access to snapshots of the 3.6.x line of the RabbitMQ server.
rabbitmq-v3.7.x
Gives access to snapshots of the 3.7.x line of the RabbitMQ server.

For instance, if you want to use RabbitMQ 3.6.x snapshots on a Debian Wheezy:

wget -O- https://www.rabbitmq.com/rabbitmq-release-signing-key.asc | apt-key add -
cat >/etc/apt/sources.list.d/rabbitmq-dev.list <<EOF
deb http://dl.bintray.com/rabbitmq/debian-dev wheezy rabbitmq-server-v3.6.x
EOF
apt-get update
apt-get install rabbitmq-server

Yum repository

Packages for RPM-based Linux distributions are available from a Bintray repository called rpm-dev which serves several Yum repositories. There is a Yum repository per package we produce (the RabbitMQ server being one) and per version of supported distributions.

For instance, if you want to use RabbitMQ 3.6.x snapshots on a CentOS 7:

cat >/etc/yum.repos.d/rabbitmq-dev.repo <<EOF
[rabbitmq-dev]
name=rabbitmq-dev
baseurl=https://dl.bintray.com/rabbitmq/rpm-dev/rabbitmq-server/v3.6.x/el/7
gpgcheck=1
gpgkey=https://www.rabbitmq.com/rabbitmq-release-signing-key.asc
repo_gpgcheck=0
enabled=1
EOF
yum install rabbitmq-server

Providing Feedback

Team RabbitMQ appreciates community feedback on snapshot builds. Please post it to the RabbitMQ mailing list and specify what build was used plus as much context as possible:

  • Server log file(s)
  • A code snippet or terminal (shell) transcript that demonstrates steps to reproduce the observations
  • rabbitmqctl environment output
  • rabbitmqctl status output
  • OS and distribution version
  • Erlang version used
and so on. Thank you!