[JIRA] (JENKINS-55120) Jenkins webhook stopped working

4 views
Skip to first unread message

limors@visualitynq.com (JIRA)

unread,
Dec 11, 2018, 3:40:02 AM12/11/18
to jenkinsc...@googlegroups.com
Limor Segal Shevah created an issue
 
Jenkins / Bug JENKINS-55120
Jenkins webhook stopped working
Issue Type: Bug Bug
Assignee: Chris Pitman
Attachments: requestError.png
Components: webhook-step-plugin
Created: 2018-12-11 08:39
Environment: Jenkins version 2.155 + all updated latest plugins relevant to 11.12.2018
Priority: Critical Critical
Reporter: Limor Segal Shevah

Hi,
 
I use Jenkins ver: 2.155
All relevant plugins were upgraded to the latest today, I restarted Jenkins machine.
I have webhook which is triggered on create\update pull request events which stopped working before 12 days. Till than it build was triggered automatically.
On bitbucket webhook send request history I can see three attempts for every event that is done, request fails with the following connection error. 
Please advice ASAP,
Thanks,
Limor
 

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

limors@visualitynq.com (JIRA)

unread,
Dec 11, 2018, 3:42:01 AM12/11/18
to jenkinsc...@googlegroups.com
Limor Segal Shevah updated an issue
Change By: Limor Segal Shevah
Attachment: requestError.png

limors@visualitynq.com (JIRA)

unread,
Dec 11, 2018, 3:42:02 AM12/11/18
to jenkinsc...@googlegroups.com

limors@visualitynq.com (JIRA)

unread,
Dec 11, 2018, 3:45:01 AM12/11/18
to jenkinsc...@googlegroups.com
Limor Segal Shevah updated an issue
Hi,
 
I use Jenkins ver: 2.155
All relevant plugins were upgraded to the latest today, I restarted Jenkins machine.
I have webhook which is triggered on create\update pull request events which stopped working before 12 days. Till than it build was triggered automatically.
On bitbucket webhook send request history I can see three attempts for every event that is done, request fails with the following connection error . :  
|X-Squid-Error|ERR_CONNECT_FAIL 110|

 
Please advice ASAP,
Thanks,
Limor
 

limors@visualitynq.com (JIRA)

unread,
Dec 11, 2018, 3:46:02 AM12/11/18
to jenkinsc...@googlegroups.com
Limor Segal Shevah updated an issue
Change By: Limor Segal Shevah
Priority: Critical Blocker

pfrick@columbia.com (JIRA)

unread,
Dec 17, 2018, 5:59:01 PM12/17/18
to jenkinsc...@googlegroups.com

pfrick@columbia.com (JIRA)

unread,
Dec 17, 2018, 6:00:02 PM12/17/18
to jenkinsc...@googlegroups.com
Patrick Frick edited a comment on Bug JENKINS-55120
We are also getting this issue. I have verified that other Bitbucket integrations are working as well. the only error I see is the one [~limors] is reporting.

limors@visualitynq.com (JIRA)

unread,
Dec 18, 2018, 1:45:03 AM12/18/18
to jenkinsc...@googlegroups.com

Bitbucket ip address had been changed and packets from webhook were blocked in our firewall. When opened new ip in firewall webhook worked ok. 

 

 

limors@visualitynq.com (JIRA)

unread,
Dec 18, 2018, 1:48:02 AM12/18/18
to jenkinsc...@googlegroups.com

I did not close this issue because maybe you have other reason for this behavior Patrick Frick.  If it is the same issue of blocked packets, please close this issue, thanks.

 

slide.o.mix@gmail.com (JIRA)

unread,
Sep 3, 2019, 7:53:02 PM9/3/19
to jenkinsc...@googlegroups.com
Alex Earl updated an issue
Change By: Alex Earl
Component/s: _unsorted
Component/s: webhook-step-plugin

slide.o.mix@gmail.com (JIRA)

unread,
Sep 3, 2019, 7:53:03 PM9/3/19
to jenkinsc...@googlegroups.com

This is unrelated to the webhook-step-plugin

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 29, 2020, 12:19:03 PM2/29/20
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Not A Defect
 

Configuration error in a firewall, not a Jenkins issue.

Change By: Mark Waite
Status: Open Closed
Resolution: Not A Defect
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages