Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44735

Builds not getting triggered by queue

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      RabbitMQ 3.6.9 on a Ubuntu Server 16.04
      Jenkins version 2.46.2
      RabbitMQ Build Trigger Plugin 2.3
    • Similar Issues:

      Description

      I have setup a RabbitMQ server on a VM in my machine - I have verified through Rabbit MQ web client as well as python code that I am able to publish and receive messages in and out of a queue.
       
      I have setup Jenkins in another VM and installed Jenkins. I have verified that from this machine I am able to publish/ subscribe messages using the RabbitMQ server. 
       
      I've installed RabbitMQ Build Trigger plugin and configured the Rabbit MQ queue in the settings section. I've also verified that the test connection is successful. The settings are as shown here: .
       
      I've configured a test job and set the token in build trigger to "TOKEN", as shown here:

       
      I am publishing a message using RabbitMQ's management web front end, as shown here:

       
      The issue is that I don't see a build getting triggered on Jenkins.
       
      Is there something I am missing in my setup?

      Any help will be greatly appreciated.

      ----------------------------------------------

      UPDATE -  June 7 2017: When I enabled debug logging in Jenkins settings for the plugin, the log indicates that it is receiving the message, thus:

       

      Jun 07, 2017 11:56:25 AM INFO org.jenkinsci.plugins.rabbitmqconsumer.logger.MessageLogger onReceive
      Receive: (application/json) {"project": "TestProject", "token": "TOKEN", "parameter": [\{"name": "key1", "value": "value1"}, \{"name": "key2", "value": "value2"}, \{"name": "key3", "value": "value3"}]}
      Jun 07, 2017 12:00:47 PM INFO org.jenkinsci.plugins.rabbitmqconsumer.logger.MessageLogger onReceive
      Receive: (application/json) {"project": "TestProject", "token": "TOKEN", "parameter": [\{"name": "key1", "value": "value1"}, \{"name": "key2", "value": "value2"}, \{"name": "key3", "value": "value3"}]}
      Jun 07, 2017 12:02:04 PM INFO org.jenkinsci.plugins.rabbitmqconsumer.logger.MessageLogger onReceive
      Receive: (application/json) {"project": "TestProject", "token": "TOKEN", "parameter": [\{"name": "key1", "value": "value1"}, \{"name": "key2", "value": "value2"}, \{"name": "key3", "value": "value3"}]}
       
      Is the way I set the token value in the above settings correct?

        Attachments

        1. RMQ-1.png
          48 kB
          Radha Krishna Srimanthula
        2. RMQ-2.png
          21 kB
          Radha Krishna Srimanthula
        3. RMQ-3.png
          27 kB
          Radha Krishna Srimanthula

          Activity

          Hide
          brejoc Jochen Breuer added a comment -

          We've had the same problem. After compiling the plugin from head it worked. There seems to be a bug in the 2.5 release version.

          Show
          brejoc Jochen Breuer added a comment - We've had the same problem. After compiling the plugin from head it worked. There seems to be a bug in the 2.5 release version.
          Hide
          adhitya Adhitya Iyer added a comment -

          Had the same issue, except that the messages were not being delivered at all despite specifying the right token, app-id, etc. Messages were just piling up in the queue. Resolved simply by restarting Jenkins. Not sure why I got this error, because I restarted Jenkins after installing the plugin. Just happy that it's working for now.

          Show
          adhitya Adhitya Iyer added a comment - Had the same issue, except that the messages were not being delivered at all despite specifying the right token, app-id, etc. Messages were just piling up in the queue. Resolved simply by restarting Jenkins. Not sure why I got this error, because I restarted Jenkins after installing the plugin. Just happy that it's working for now.

            People

            • Assignee:
              Unassigned
              Reporter:
              sradhakrishna Radha Krishna Srimanthula
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: