Pipeline never runs on merge

[Dominick Marino]

Have 3 branches, Master, UAT, QA. Development is done in feature branch's that get created by Jira.

When feature branch pull request is merged from the feature branch to the QA branch the pipeline never runs. If I merge anything to Master the pipeline automatically runs.

Merge to QA pipeline never runs but I can run it manually and it succeeds 100%.

Below is my pipeline configuration. I have tried to resolve this problem now for two days and have no idea how to troubleshoot this issue. Any help would be appreciated.

image:
  name: salesforce/cli:2.16.0-full

pipelines:
  branches: # Pipelines automatically deploy from commits into branch
    master: #Production pipeline
      - step:
          name: Deploy to Production
          deployment: production
          script:
            - echo "Executing Production pipeline"
            - npm i shelljs
            - node ./deploymentFunctions/deploy.js --username=$SFDC_USERNAME --consumerKey=$SFDC_CONSUMER_KEY --loginURL=$SFDC_LOGIN_URL --branch=$BITBUCKET_BRANCH --checkDeploy=$CHECK_DEPLOY
    uat: #UAT Pipline
      - step:
          name: Deploy to UAT
          deployment: uat
          script:
            - echo "Executing UAT pipeline"
            - npm i shelljs
            - node ./deploymentFunctions/deploy.js --username=$SFDC_USERNAME --consumerKey=$SFDC_CONSUMER_KEY --loginURL=$SFDC_LOGIN_URL --branch=$BITBUCKET_BRANCH --checkDeploy=$CHECK_DEPLOY
    qa: #QA Pipline
      - step:
          name: Deploy to QA
          deployment: qa
          script:
            - echo "Executing QA pipeline"
            - npm i shelljs
            - node ./deploymentFunctions/deploy.js --username=$SFDC_USERNAME --consumerKey=$SFDC_CONSUMER_KEY --loginURL=$SFDC_LOGIN_URL --branch=$BITBUCKET_BRANCH --checkDeploy=$CHECK_DEPLOY
  custom: # Pipelines that are triggered manually
    Sandbox-TR: # The name that is displayed in the list in the Bitbucket Cloud GUI
      - step:
          name: Deploy to Sandbox TR
          deployment: sandbox-tr
          script:
           - echo "Executing Sandbox TR pipeline"
           - npm i shelljs
           - node ./deploymentFunctions/deploy.js --username=$SFDC_USERNAME --consumerKey=$SFDC_CONSUMER_KEY --loginURL=$SFDC_LOGIN_URL --branch=$BITBUCKET_BRANCH --checkDeploy=$CHECK_DEPLOY
    Sandbox-MR:
      - step:
          name: Deploy to Sandbox MR
          deployment: sandbox-mr
          script:
           - echo "Executing Sandbox MR pipeline"
           - npm i shelljs
           - node ./deploymentFunctions/deploy.js --username=$SFDC_USERNAME --consumerKey=$SFDC_CONSUMER_KEY --loginURL=$SFDC_LOGIN_URL --branch=$BITBUCKET_BRANCH --checkDeploy=$CHECK_DEPLOY

[Mark C]

Hi @Dominick Marino,

Welcome to the community.

Would you be able to confirm if the pull request's source branch is set to "qa"?
Also, when you try to push a commit directly to the "qa" branch, does it trigger a Pipelines build?

Regards,
Mark C

[Dominick Marino]

it's actually set to QA (caps) but this hasn't been an issue before. I have tried changing the "qa" in the pipeline to "QA" and it didn't make a difference. 

If I manually push a commit, it does not fire, but if I manually run the pipeline after that commit or merge it runs fines.

[Mark C]

Hi @Dominick Marino

I tried validating your YAML configuration using this link but it says it is valid. - https://bitbucket-pipelines.prod.public.atl-paas.net/validator

Could you confirm if pushing a commit to the "uat" branch triggers a Pipelines build?

Regards,
Mark C

[Dominick Marino]

No, a commit to UAT does not fire either. The only one that will fire automatically so far is the master.

I also ran the pipeline through the validator and got a valid result also.

[Mark C]

Thanks for the information, @Dominick Marino

I went ahead and created a support ticket for us to continue our discussion there.

You should be able to receive an email notification regarding that.

Regards,
Mark C

[Dominick Marino]

I created a support ticket on the 31st of October since responses were pretty slow and I need to get this issue resolved as soon as possible.

That ticket # is BBS-210432.

Unfortunately, responses in that ticket have been very slow also.