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

JIRA Trigger not triggering on status change

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Won't Fix
    • Component/s: jira-trigger-plugin
    • Labels:
      None
    • Environment:
      Jenkins version: 2.164.2
      JIRA Trigger version: 1.0.0
      JIRA Plugin: 3.0.6
      Jenkins install on Linux
    • Similar Issues:

      Description

      The Jira Trigger in Jenkins is no longer working in our job.

      Jenkins job is setup to trigger when an issue is updated in JIRA.  JQL is very simple and does show the item in Jira when placed in "Search Issues".

      If Jira issue is edited, the trigger executes and Jenkins job starts.

      If the status of the Jira issue is changed, the trigger does NOT execute.  Even though the Post condition is set to trigger an issue updated event when the issue transition is done.

      Jenkins System log also shows Webhook is received as an issue_updated event.  But the job never starts.

      Webhook event body:
      May 22, 2019 2:50:41 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook

      { "timestamp": 1558551041306, "webhookEvent": "jira:issue_updated", "issue_event_type_name": "issue_updated", <Removed log content> }

      }
      May 22, 2019 2:50:41 PM FINE org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrap invoke
      Received Webhook callback from changelog. Event type: jira:issue_updated

        Attachments

          Activity

          Hide
          ceilfors Wisen Tanasa added a comment -

          That's weird. Can you help share the "Webhook event body" for both the one that is working, and the one that is not? Seeing the whole event body will be helpful for troubleshooting.

          Show
          ceilfors Wisen Tanasa added a comment - That's weird. Can you help share the "Webhook event body" for both the one that is working, and the one that is not? Seeing the whole event body will be helpful for troubleshooting.
          Hide
          calvinmichel Michel Calvin added a comment -

          Thanks for the quick response.  We have figured out the issue.  We have several Jenkins jobs that use the Jira trigger.  If one of them has a syntax error in the JQL, this causes all of the jobs not to trigger.  We have noticed this on our Windows Jenkins server which has dozens of jobs using the trigger.  But on Windows, the Jenkins System Log provides an error message and we can quickly determine that the JQL is causing the issue and what job needs to be fixed.  On Linux, no error is given in the logs.  We are using the same Jenkins version on Linux and Windows.

          By chance we decided to verify all of the JQLs were valid and found the error.  But we had to investigate every job until we discovered this.  Is there a way to make the Jira trigger logs the same as what we see on Windows?

          Example below:

          (Windows) 

           

           

           

          Show
          calvinmichel Michel Calvin added a comment - Thanks for the quick response.  We have figured out the issue.  We have several Jenkins jobs that use the Jira trigger.  If one of them has a syntax error in the JQL, this causes all of the jobs not to trigger.  We have noticed this on our Windows Jenkins server which has dozens of jobs using the trigger.  But on Windows, the Jenkins System Log provides an error message and we can quickly determine that the JQL is causing the issue and what job needs to be fixed.  On Linux, no error is given in the logs.  We are using the same Jenkins version on Linux and Windows. By chance we decided to verify all of the JQLs were valid and found the error.  But we had to investigate every job until we discovered this.  Is there a way to make the Jira trigger logs the same as what we see on Windows? Example below: (Windows)       
          Hide
          ceilfors Wisen Tanasa added a comment -

          I'm not sure about this one actually, sorry. It seems like configuration issue. Probably best to ask in Jenkins core community?

          Show
          ceilfors Wisen Tanasa added a comment - I'm not sure about this one actually, sorry. It seems like configuration issue. Probably best to ask in Jenkins core community?

            People

            • Assignee:
              ceilfors Wisen Tanasa
              Reporter:
              calvinmichel Michel Calvin
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: