Pipeline is running wrong branch

schind

Hi,

I may have found a bug in the pipelines definition.

In my project, a specific build should run for the `feature/specific-feature` Branch, all other feature and testing branches should have the same steps. After reading the documentation (https://support.atlassian.com/bitbucket-cloud/docs/use-glob-patterns-on-the-pipelines-yaml-file/), I created a separate branch pipeline for this specific branch. But when pushing to this branch, the other pipeline runs.

I tried this with an example project and a very small bitbucket-pipelines.yml:

image: atlassian/default-image:2

pipelines:
default:
    - step:
script:
          - echo "default pipeline"
branches:
feature/specific-feature:
      - step:
script:
            - echo "specific feature pipeline"
    '{feature/*,testing/*}':
      - step:
script:
            - echo "pipeline for all other feature and testing branches"

But, when pushing to the `feature/specific-feature` branch, the pipeline outputs "pipeline for all other feature and testing branches". I have attached a screenshot of the pipeline output:

Could anyone help me?

Theodora Boudale

Hi @schind ,

I believe this may be a bug, as a pipeline for a specific branch should override a more generic expression that would match this branch.

I am going to reach out to the development team to confirm and will then raise a bug report.

Based on several attempts I made to reproduce and narrow down the scope of the issue, it looks that the problem is introduced when the curly brackets are used.

As a workaround, I would suggest using a yaml file like this instead:

image: atlassian/default-image:2

pipelines:
default:
    - step:
script:
          - echo "default pipeline"
branches:
feature/specific-feature:
      - step:
script:
            - echo "specific feature pipeline"
    feature/*:
      - step:
script:
            - echo "pipeline for all other feature and testing branches"
    testing/*:
      - step:
          script:
            - echo "pipeline for all other feature and testing branches"

 

This should work as expected. If the script for feature/* and testing/* has a lot of commands, you can use yaml anchors to improve readability and be able to make changes for both pipelines at the same place:

 

image: atlassian/default-image:2

definitions:
  steps:
    - step: &feature-testing
        script:
          - echo "pipeline for all other feature and testing branches"

pipelines:
default:
    - step:
script:
          - echo "default pipeline"
branches:
feature/specific-feature:
      - step:
script:
            - echo "specific feature pipeline"
    feature/*:
      - step: *feature-testing
    testing/*:
      - step: *feature-testing

 

Please feel free to let me know if this works for you, I will follow up with you also regarding the bug report.

Kind regards,
Theodora