[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change

9 views
Skip to first unread message

calvinmichel@bfusa.com (JIRA)

unread,
May 22, 2019, 2:53:03 PM5/22/19
to jenkinsc...@googlegroups.com
Michel Calvin created an issue
 
Jenkins / Bug JENKINS-57620
JIRA Trigger not triggering on status change
Issue Type: Bug Bug
Assignee: Wisen Tanasa
Attachments: image-2019-05-22-13-49-33-661.png
Components: jira-trigger-plugin
Created: 2019-05-22 18:52
Environment: Jenkins version: 2.164.2
JIRA Trigger version: 1.0.0
JIRA Plugin: 3.0.6
Jenkins install on Linux
Priority: Critical Critical
Reporter: Michel Calvin

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

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

wisen@ceilfors.com (JIRA)

unread,
May 22, 2019, 5:35:02 PM5/22/19
to jenkinsc...@googlegroups.com
Wisen Tanasa commented on Bug JENKINS-57620
 
Re: JIRA Trigger not triggering on status change

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.

calvinmichel@bfusa.com (JIRA)

unread,
May 22, 2019, 6:21:01 PM5/22/19
to jenkinsc...@googlegroups.com
Michel Calvin updated an issue
 
Change By: Michel Calvin
Attachment: image-2019-05-22-17-20-13-170.png

calvinmichel@bfusa.com (JIRA)

unread,
May 22, 2019, 6:23:02 PM5/22/19
to jenkinsc...@googlegroups.com
Michel Calvin commented on Bug JENKINS-57620
 
Re: JIRA Trigger not triggering on status change

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) 

 

 

 

wisen@ceilfors.com (JIRA)

unread,
May 25, 2019, 4:54:02 AM5/25/19
to jenkinsc...@googlegroups.com

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

wisen@ceilfors.com (JIRA)

unread,
May 25, 2019, 4:20:01 PM5/25/19
to jenkinsc...@googlegroups.com
Wisen Tanasa closed an issue as Won't Fix
 
Change By: Wisen Tanasa
Status: Open Closed
Resolution: Won't Fix
Reply all
Reply to author
Forward
0 new messages