[JIRA] (JENKINS-58162) Pipeline stuck if git API is not responsible

[rangelov...@gmail.com (JIRA)]

Title: Message Title

Valeri Rangelov created an issue   Jenkins / JENKINS-58162 Pipeline stuck if git API is not responsible Issue Type: Improvement Assignee: Unassigned Components: notification-plugin Created: 2019-06-24 12:21 Environment: Jenkins Version: 2.176.1 Labels: jenkins pipeline Priority: Critical Reporter: Valeri Rangelov Pipeline is stay in a stuck state ( in progress ) if the GIT API is not responding. This happened with Bitbucket and manual stop of the running pipeline was needed. In our case Job 1 is triggering Job 2 and Job 1 is waiting for Job 2 to finish and report the status of the pipeline, but because of this issue Job 2 stuck which caused also Job 1 to stuck. In order to exit from this loop manual stop was needed and after that to start manual Job 2 in order to do the task properly and send a notification to Job 1. This was caused most probably because of a little downtime in the Bitbucket API. Maybe the solution will be to set a loop for a retry and if it is not possible to send a failure notification to the JOB 1.    Jenkins Version: 2.176.1 Log message:   [Bitbucket] Notifying commit build result[Bitbucket] Notifying commit build resultERROR: Could not send notificationsjava.io.IOException: Communication error at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.doRequest(BitbucketCloudApiClient.java:866) Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200213.1561378915000.7298.1561378920304%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.