Support for connecting to exchanges residing in a virtual host is missing

[t031276]

Bug

Please include the following info

• Version of the plugin 1.1.1 https://jitpack.io/com/github/praqma/tracey-jenkins-trigger-plugin/1.1.1/tracey-jenkins-trigger-plugin-1.1.1.hpi

• RabbitMQ server version 3.7.14

• Description of the problem and how it manifest itself

  There is no way to chose a different virtual host than '/' when connecting to the rabbitMQ server. This makes it impossible for to use exchanges that are run in the same rabbit MQ server but in a different virtual host. The job only allows for exchange name ,type and server to be configured.

• Scenario that we can use to reproduce the problem Recent LTS version of jenkins, Jenkins 2.263.3 and a rabbit MQ server

  In jenkins: Configure access to the rabbit MQ server in jenkins. Please configure "Message broker hosts configuration for Tracey" and set "Host name", "Host address", "Port", "Credentials" appropriately.

  Create a job that will be triggered by receiving a message from rabbit MQ. In Rabbit MQ: Create a virtual host Create an exchange in that virtual host Create a queue in that exchange.

  In jenkins: Create a job that can be triggered by rabbit MQ:

  RabbitMQ Trigger  

  • RabbitMQ exchange name
    • RabbitMQ exchange type
    •  RabbitMQ host

• Logs showing the problem There is no relevant log to show

• How often issue occurs and its impact on your workflow. What would happen if it won't be fixed? Always when trying to use an exchange residing in a virtual host. It lead to a more complicated setup with having multiple Rabbit MQ servers.

Feature

Please include the following info

• Problem that you are trying to solve/use case Triggering sw builds/test and other use cases, basically trying to run a job in jenkins that is triggered by a rabbit MQ message.

• Desired outcome An updated plugin with the possibility to select which virtual host the exchange is running on.

• Deadlines/priorities

• Ideas and thoughts about technical implementation Either add virtual host when setting up the job in jenkins. Or Specify the virtual host when setting up "Message broker hosts configuration for Tracey" in jenkins system configuration.

Apply tag - waiting for the feedback

[praqma-thi]

Hey David,

Thank you for the detailed write-up, but I'm afraid I'll have to disappoint you on this one. Tracey is an orphaned project. It hasn't moved in five years, and is unlikely to do so again.

I'd advise you to move on and look into alternatives for triggering your jobs. Perhaps the generic-webhook-trigger can help? It's a pretty flexible plugin for triggering on external events, as long as you can get them to drop their payload on its endpoint.

If anyone is interested in picking up the issue or forking the projects. I believe the RabbitMQ host configuration implementation actually resides in the tracey-broker project, a dependency of this project.