Ignore bitbucketpipelines.yml during branch merge

jawad_abbasi

I have two branches which have two separate bit bucket pipelines

  1. master

  2. develop 

when we try to merge the updated develop branch to the master, the pipeline in develop branch also merges with master and i don't want this happen because both pipelines are different from one another.

Thanks in advance if someone tell me how to get rid out of this ?

Daniel Santos_157bm4

Hi @jawad_abbasi,

As you already know you can have multiple different bitbucket-pipelines.yml files in your repository, one for each branch, but that will bring you the inconvenient situation you are facing now.

The easier/recommended approach would be considering all of them the same file, but eventually with different versions. It means that the bitbucket-pipelines.yml file would have the pipeline's configuration for every branch that needs dedicated steps to run.

 

Let's say the first configuration we have for pipelines is this on master:

pipelines:
  default:
    - step:
        script:
          - echo "this will run for EVERY OTHER repository branch"

Later we create develop branch and inherit it. We notice that we need a special pipeline for it. We then add and extra section to the bitbucket-pipelines which becomes this:

pipelines:
  default:
    - step:
        script:
          - echo "this will run for EVERY OTHER repository branch"
  branches:
    develop:
      - step:
          script:
            - echo "this step will only run in DEVELOP branch"

Merging the file back to master will still run only the first step (configured for default).

Please notice that what is in default will run for every branch other than develop.

At some point, you realize that you don't want new branches to run pipelines. In this case, you would change the default part to trigger only the master branch. The file would become like this:

pipelines:
  branches:
    master
      - step:
          script:
            - echo "this step will only run in MASTER branch"

    develop:
      - step:
          script:
            - echo "this step will only run in DEVELOP branch"

 

Following the same idea, you can keep updating the bitbucket-pipelines.yml file and merging it without causing undesired builds.

Please let me know if it makes sense to you now.