Deploy and Release currently supports RabbitMQ "Classic" Queues.
RabbitMQ has deprecated this type of queue. Quorum queues are the new methodology.
When it is released, RabbitMQ 4.0 will eliminate the availability of "Classic" queues completely.
See for more information.
https://support.digital.ai/hc/en-us/requests/193968
https://blog.rabbitmq.com/posts/2023/02/quorum-queues-migration/
by: Jason H. | 9 months ago | *All other
Comments
Today Deploy uses ActiveMQ internally and also supports configuring an external RabbitMQ instance. We communicate with these queues via JMS 2.0. We have scheduled an investigation of Quorum queues following our Denali release to determine whether we can use our existing interfaces or whether substantial refactoring is required.
Do you have RabbitMQ setup for both Release and Deploy, or Deploy only?
Jason manages my team; answering for him: In addition to Deploy, we have a RabbitMQ queue in place _ready_ to be used by Release, but we have not yet hooked Release up to use it. It's not hooked up for Release because we don't currently use the features that require it (webhooks of some sort?). Note for our team: this is "sle-releasewebhook"
2 / 2
Could customers who have upvoted this idea kindly specify whether they are interested in this update for the Deploy product, the Release product, or both, as it is a shared concept? It is crucial for us to understand which product is in demand so that we can prioritize accordingly.
Since RabbitMQ is available for both Deploy and Release, and the classic queues are being deprecated, I don't see why it would matter if we are interested in the update for one application or the other. Both of them *have* to be updated to continue to support RabbitMQ.
Support for RabbitMQ Quorum queues for Release and Deploy will be part of 24.1 General Availability release.