[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

[nissim.bitan@aquasec.com (JIRA)]

Nissim Bitan created an issue

Jenkins / JENKINS-58810 Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed Issue Type: Bug Assignee: Unassigned Components: bitbucket-plugin Created: 2019-08-05 12:29 Priority: Minor Reporter: Nissim Bitan Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed, error message  [Bitbucket] Notifying pull request build result ERROR: Could not send notifications java.io.IOException: Communication error at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.doRequest(BitbucketCloudApiClient.java:861) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:902) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postBuildStatus(BitbucketCloudApiClient.java:607) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketChangesetCommentNotifier.buildStatus(BitbucketChangesetCommentNotifier.java:50) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.createStatus(BitbucketBuildStatusNotifications.java:143) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.sendNotifications(BitbucketBuildStatusNotifications.java:185) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.access$000(BitbucketBuildStatusNotifications.java:60) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications$JobCompletedListener.onCompleted(BitbucketBuildStatusNotifications.java:257) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:209) at org.jenkinsci.plugins.workflow.job.WorkflowRun.finish(WorkflowRun.java:584) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1000(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:996) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1463) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:458) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:37) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.executeMethod(BitbucketCloudApiClient.java:759) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.doRequest(BitbucketCloudApiClient.java:843) ... 22 more Finished: SUCCESS Add Comment

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

[patrik.schalin@gmail.com (JIRA)]

Patrik Schalin commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed Also seeing this after Jenkins and Plugins upgrade. My current env: Jenkins : 2.187 blueocean-events : 1.18.1 azure-ad : 0.3.4 azure-vm-agents : 1.1.1 pipeline-stage-step : 2.3 github-api : 1.95 pam-auth : 1.5.1 windows-azure-storage : 1.1.0 ldap : 1.20 Office-365-Connector : 4.11.0 timestamper : 1.10 azure-container-agents : 1.1.0 ivy : 2.1 maven-plugin : 3.4 ant : 1.9 configuration-as-code-support : 1.18 configuration-as-code : 1.25 junit : 1.28 durable-task : 1.30 mstest : 1.0.0 sonar : 2.9 jackson2-api : 2.9.9.1 bitbucket : 1.1.10 git-parameter : 0.9.11 blueocean-pipeline-api-impl : 1.18.1 matrix-project : 1.14 token-macro : 2.8 git : 4.0.0-rc mailer : 1.24 workflow-basic-steps : 2.18 workflow-job : 2.33 blueocean-git-pipeline : 1.18.1 blueocean-pipeline-scm-api : 1.18.1 pipeline-milestone-step : 1.3.1 jquery-detached : 1.2.1 workflow-durable-task-step : 2.33 pipeline-utility-steps : 2.3.0 azure-publishersettings-credentials : 1.5 blueocean-rest-impl : 1.18.1 windows-slaves : 1.4 favorite : 2.3.2 xunit : 2.3.5 workflow-scm-step : 2.9 azure-app-service : 1.0.0 docker-commons : 1.15 trilead-api : 1.0.5 command-launcher : 1.3 role-strategy : 2.13 htmlpublisher : 1.18 jdk-tool : 1.3 resource-disposer : 0.13 ssh-agent : 1.17 blueocean-pipeline-editor : 1.18.1 blueocean-bitbucket-pipeline : 1.18.1 authentication-tokens : 1.3 external-monitor-job : 1.7 pipeline-input-step : 2.10 scm-api : 2.6.3 github-branch-source : 2.5.5 script-security : 1.62 pipeline-rest-api : 2.12 blueocean-commons : 1.18.1 bitbucket-filter-project-trait : 1.0 variant : 1.3 matrix-auth : 2.4.2 artifactory : 3.3.2 bitbucket-approval-filter : 1.0.2 lockable-resources : 2.5 ssh-credentials : 1.17.1 pipeline-model-definition : 1.3.9 mercurial : 2.8 azure-commons : 1.0.4 git-client : 3.0.0-rc azure-acs : 0.2.4 pipeline-build-step : 2.9 basic-branch-build-strategies : 1.3.2 cloudbees-folder : 6.9 azure-cli : 0.9 jsch : 0.1.55.1 blueocean-rest : 1.18.1 blueocean-jira : 1.18.1 copyartifact : 1.42.1 workflow-cps-global-lib : 2.15 jira : 3.0.8 blueocean-config : 1.18.1 gradle : 1.33 credentials : 2.2.1 build-timeout : 1.19 docker-java-api : 3.0.14 docker-workflow : 1.19 apache-httpcomponents-client-4-api : 4.5.5-3.0 structs : 1.20 cloud-stats : 0.24 credentials-binding : 1.19 azure-credentials : 1.6.1 http_request : 1.8.23 blueocean-autofavorite : 1.2.4 pipeline-stage-view : 2.12 workflow-api : 2.36 ws-cleanup : 0.37 jquery : 1.12.4-0 dtkit-api : 2.1.1-1 pipeline-stage-tags-metadata : 1.3.9 display-url-api : 2.3.2 handlebars : 1.1.1 kubernetes-cd : 1.0.0 blueocean-personalization : 1.18.1 plain-credentials : 1.5 thinBackup : 1.9 jenkins-design-language : 1.18.1 workflow-aggregator : 2.6 pipeline-graph-analysis : 1.10 pipeline-model-declarative-agent : 1.1.1 powershell : 1.3 config-file-provider : 3.6.2 workflow-support : 3.3 azure-function : 0.3.0 antisamy-markup-formatter : 1.5 workflow-step-api : 2.20 github : 1.29.4 sse-gateway : 1.19 azure-container-registry-tasks : 0.6.3 blueocean-jwt : 1.18.1 ace-editor : 1.1 handy-uri-templates-2-api : 2.1.7-1.0 blueocean-display-url : 2.3.0 workflow-multibranch : 2.21 momentjs : 1.1.1 jquery-ui : 1.0.2 blueocean-i18n : 1.18.1 javadoc : 1.5 blueocean : 1.18.1 saml : 1.1.2 branch-api : 2.5.4 pipeline-model-extensions : 1.3.9 bitbucket-scm-trait-commit-skip : 0.4.0 workflow-cps : 2.73 pipeline-model-api : 1.3.9 cloudbees-bitbucket-branch-source : 2.4.5 blueocean-dashboard : 1.18.1 blueocean-web : 1.18.1 pubsub-light : 1.12 bouncycastle-api : 2.17 git-server : 1.7 blueocean-core-js : 1.18.1 blueocean-github-pipeline : 1.18.1 tfs : 5.142.0 blueocean-executor-info : 1.18.1

Add Comment

[patrik.schalin@gmail.com (JIRA)]

Patrik Schalin edited a comment on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Also seeing this after Jenkins and Plugins upgrade.

Have the same traces in logs. Also seeing sporadic "glitches" in Jenkins picking up push notifications from Bitbucket (Cloud). Enabled request traces in BB but cannot see any errors and 200s are reported. Clicking on "re-send request" kicks off the build as expected. My current env: {code:java}

{code}

Add Comment

[thierry.montalbano@quebecormedia.com (JIRA)]

Thierry Montalbano commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Hi, I have the same issue with the same error message. It's intermittent. Often, when we rebuild manually, the notification is sent to bitbucket. It'd be nice if Jenkins could retry sending the notification if it fails. This started happening a about 15 days ago, maybe more.

Add Comment

[tpeck@rediker.com (JIRA)]

tom peck commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

We had this issue recently, I was able to fix it by deleting the "Bitbucket Endpoints" entry in the configure system page on jenkins.  Then I recreated them and it started working again.  We also changed our site's certificate recently, that's probably related.

Add Comment

[thierry.montalbano@quebecormedia.com (JIRA)]

Thierry Montalbano commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

tom peck Did not fix it for me. I deleted it and re-configured it. I still see the communication error happening now and then.

Add Comment

[joao.admiranda@gmail.com (JIRA)]

Joao Miranda commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Same problem here. It's very inconvenient! Please, anybody got fix this?

Add Comment

[joshua.bergeron@gmail.com (JIRA)]

Joshua Bergeron commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

I have also recently been experiencing this and it has been driving be crazy!

Add Comment

[joshua.bergeron@gmail.com (JIRA)]

Joshua Bergeron edited a comment on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

I have also recently been experiencing this and it has been driving be me crazy! It started happening in the last week and has been intermittent. Glad to find others running into similar issues.

Add Comment

[joshua.bergeron@gmail.com (JIRA)]

Joshua Bergeron edited a comment on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

I have also recently been experiencing this and it has been driving me crazy! It started happening in the last week and has been intermittent - both on the build notification end and build trigger side of things . Glad to find others running into similar issues.

Add Comment

[patrik.schalin@gmail.com (JIRA)]

Patrik Schalin commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Tried downgrading to no avail. Noticed that it was not all my jobs that were failing but only a select few with no useful information in the logs. Finally solved it by logging on to the master and forcefully delete the job dirs of the failing jobs and then run the folder scan. For the first time since this problem started the re-created jobs actually builds as expected.

Add Comment

[joshua.bergeron@gmail.com (JIRA)]

Joshua Bergeron commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Gave that a try and the first build after that went well, but subsequent builds have remained inconsistent - sometimes jobs fail to checkout, other times they fail to send the build status notification. Always the same java.io.IOException but not much other helpful information. Doing what I can to investigate on my end but I'm running short of ideas so if anyone has any

Add Comment

[alanjcastonguay@gmail.com (JIRA)]

Alan Castonguay commented on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Appears to be similar to some of the observations in https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/213

Add Comment

[alanjcastonguay@gmail.com (JIRA)]

Alan Castonguay edited a comment on JENKINS-58810

Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

Appears to be similar to some of the observations in  [ https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/213 ] - created [https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/217]

Add Comment