Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why is my pipeline not running?

Heyo,

 

So just now I updated my pipeline and made the push/merge to the branch (dev). But the pipeline is not running. Could anyone help me out?

 

Heres the pipeline

image: node:10.15.3

pipelines:
branches:
dev:
- step: name: Build & Deploy PWA
caches: - node
deployment: dev
script:
- cd functions; npm i; cd ..; npm i
- npm run build:prod:pwa
- pipe: atlassian/firebase-deploy:0.3.4
variables:
FIREBASE_TOKEN: '$FIREBASE_TOKEN'

I'm fairly new to this, so any help is gladly appreciated!

1 answer

0 votes

Hi @Sebastian Montoya

This is odd. 
If I had to troubleshoot it I would:

  1. Check if the Pipelines feature is enabled.
    Repository settings >> Pipelines - Settings >> Enable
  2. Check if the webhooks are configured and are able to see the pushes for the branch specified.
    More details in section Checking Webhooks.
  3. Check if the bitbucket-pipelines.yml is valid using Bitbucket Pipelines - Validator.
  4. Check what messages you see in Pipelines section for the branch dev.

 

Checking Webhooks

Bitbucket will only trigger Pipelines if webhooks are properly set and they should be. They are configured by default but I heard that in some rare cases they were missing, so let's check them up.

Their location: Repository settings >> Workflow - Webhooks.

You should see two of them:

You should be able to enable the onpush one and watch the pushes/merges for the dev branch:

  1. Enable the History
    Screen_Shot_2019-11-20_at_12_34_05.png
  2. Commit the code to dev branch.
  3. Load the new requesScreenshot_20_11_19_12_37.pngts
  4. Check if the request is showing the correct branch in its body
    Screen_Shot_2019-11-20_at_12_47_03.png


The screenshots above are observed when things are working properly.


I hope one of the checks above can reveal some strangeness that will allow us to move forward in this investigation.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

717 views 15 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you