Can we use same branch name twice on a bitbucket pipeline file?

[Aashish41]

I have a bitbucket pipeline file as below;

pipelines:

    branches:

      dev:

        - step:

            name: Test1

            script:

              - echo "Test"  

      dev:

        - step:

            name: Test2

            script:

              - echo "Test"

 When the pipeline is triggered only first step runs i.e. Test1 but Test2 doesn't. Is there any way that I can use same branch name twice?

[Theodora Boudale · Accepted solution]

Hi @Aashish41 and welcome to the community!

I don't believe that this is possible, however, a pipeline for a certain branch can have multiple steps.

If you want to execute both steps when a commit is pushed to dev branch, you can modify your bitbucket-pipelines.yml file as follows:

pipelines:
  branches:
    dev:
      - step:
          name: Test1
          script:
            - echo "Test" 
      - step:
          name: Test2
          script:
            - echo "Test"

Is this what you are looking for?

Kind regards,
Theodora

[Aashish41]

Hi @Theodora Boudale , Thank you for your response.

I have already opted using multiple steps for a single branch. I just wanted to know if it is possible to use same branch multiple times. Unfortunately, it is not possible.

Anyway your response was helpful for me. 

Have a great day !

[Tridev Rai]

Hi @Theodora Boudale

Is there an alternative other than you create a unique branch name for your pipeline?

[Theodora Boudale]

Hi Tridev,

You can create (multiple) custom pipelines:

• https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/#Custom--manual--pipelines

Please keep in mind though that these can only be triggered manually or on a schedule, they don't run automatically on every push.

It is also possible to configure a default pipeline that will run automatically on every push if no branch-specific pipeline is defined:

• https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/#Default

The page I shared has all available options about Pipeline start conditions.

Kind regards,
Theodora

[Tridev Rai]

Thank you @Theodora Boudale for your quick response.

I will go through this and let you know if any confusion arises.

[Tridev Rai]

I had below requirements:

1. whenever the master/ hotfix branch is pushed it should be deployed in UAT environments.

2. After the QA team verifies the changes in UAT, the master branch should be deployed into production

since I couldn't use the same branch name in the pipelines. 

I used the custom pipeline to build and deploy in the production.

I also added a manual trigger in the deployment step and ensured it is only deployed by certain individuals.

Thanks @Theodora Boudale