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)

Caused by: org.apache.http.NoHttpResponseException: api.bitbucket.org:443 failed to respond