Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Add-on Pipeline is not responding. Wait or cancel?

larry_geams
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 19, 2018

This was up and running yesterday but today when I merged my updates from staging to master and checked pipeline tab, it's not working anymore. Anyone know what might cause the issue?

Screen Shot 2018-10-20 at 3.06.04 AM.png

1 answer

0 votes
StannousBaratheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 22, 2018

Hi @larry_geams

There are a few things you can check.

Firstly, Pipelines uses the YML file that is present on the branch where the push occurred. Since you merged from staging to master can you please check that the bitbucket-pipelines.yml file does indeed exist on the master branch?

Next you can check if the Pipeline addon is still installed an enabled in your repository. To do this navigate to your repository settings and under Pipelines settings ensure the "Enable Pipelines" toggle is turned on.

Lastly after you push a change to your branch you can check if your repository received the webhook to trigger a pipeline build by again navigating to the repository settings > webhooks and then click on "View requests" on the Pipelines webhook to see if the request was received successfully. Note there might be 2 pipelines webhooks in which case the one you want has the URLhttps://bitbucket-pipelines.prod.public.atl-paas.net/rest/bitbucket/event/connect/onpush

If this does not solve the issue it should at least provide enough information for us to diagnose further.

I hope this helps!

Sam

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events