Branch-Overrides doesn't work as expected

[Gabriele Papi-Jobs]

Goodmorning , 

I've a plan defined as follow 

version: 2

plan: !include 'variables/build/plan.yaml'

triggers: !include 'variables/triggers.yaml'

other:

  concurrent-build-plugin: system-default

  force-stop-build: true

  all-other-apps:

    custom.buildExpiryConfig:

      duration: '2'

      period: weeks

      expiryTypeResult: 'true'

      enabled: 'true'

branches:

  create: for-new-branch

  delete:

    after-inactive-days: 420

    after-deleted-days: 14

variables: !include 'variables/var.yaml'

repositories: !include 'variables/repository.yaml'

stages: !include 'variables/build/stages.yaml'

test-job: !include 'templates/test.yaml'

branch-overrides: 


  - develop: 

      triggers:

          - remote

      stages:

      - Different stage:

          - Different job

      Different job:

          tasks:

              - script: echo 'develop'

This is defined in a repository called "showcase-pipeline".

I have a repository with my application code called "showcase-app" ; in this repository i have different branches , and also one called develop .

When i run the plan associated with develop , i would expect to run what is inside "branch-overrides" flag, but still take the default configuration.

How can i solve ? Am i wrong ? 
Best regards

[Jyothi Charupalli · Accepted solution]

Hi @Gabriele Papi-Jobs ,

Hope you are doing great! Thanks for reaching out to Atlassian Community.

Please be informed that the repository where the specs code is stored should be linked to the Bamboo plan. Then, only the branches created in the specs repository where the specs code is stored can be created as specs branches in Bamboo, and branch overrides will be applied for those branches only created in the specs code repository.

The branches for the normal repository(without specs enabled in Bamboo) linked to the Bamboo plan will not be converted to specs branches, and branch overrides will not be applicable for repositories where specs are not enabled.

So, for plan branches to be converted to specs branches, the repository where branches are created should be a specs-enabled repository, and the plan should be published in Bamboo through that repository. That same repository should also need to be linked to the plan. Then, only branches will be converted to specs branches, and overrides configuration will be published to those branches.

Please also refer to this document: Enhanced Plan branch configuration , which explains the same and the prerequisites required for using an Enhanced plan branch configuration.

Best Regards,

Jyothi

**please don't forget to Accept the answer if your query was answered**