Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can bitbucket-pipeline.yml refer another yml file

I am in need to configure bitbucket-pipeline for each of the branches.  While we can have branch based configuration, the file becomes too big and often results in conflicts due to frequent updates.

Is it possible for the bitbucket-pipeline.yml refer to other yml file. What i am looking for is the parent yml file indicate for branch1 refer this branch1.yml, and branch2 refer branch2.yml.?

Or any way to split into multiple yml files?

 

1 answer

1 accepted

0 votes
Answer accepted
Ronald C. Atlassian Team Apr 10, 2020

Hi Kiran,

I'm afraid that it's not possible to have multiple yml configurations within the repository.
A workaround you can do is by having a bash script with all your commands within it for a specific branch then use the yml configuration to run the bash script.

For example:

  1. Create bash script: Bash Scripting Tutorial - linuxconfig.org
    #!/bin/bash 

    echo "Commands for a specific branch"
    curl bitbucket.org
  2. Save the bash script within the repository
  3. Modify the yml configuration to run the bash script according to the branch
    pipelines:
      default:
        - step:
            script:
              - ./default-commands.sh 
      branches:
        master:
          - step:
              script:
                - ./master-commands.sh
        feature/*:
          - step:
              script:
                - ./feature-commands.sh 

     

You may also make use of Pipelines' default variables - $BITBUCKET_BRANCH
Variables in pipelines - Atlassian Documentation

pipelines:
  default:
    - step:
        script:
          - ./$BITBUCKET_BRANCH.sh 

 You may need to make sure the script's name is exactly the same as the branch name.

 

Hope this helps. :)

Regards,
Ronald

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

758 views 15 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you