Common + specific functionality per branch for Bitbucket pipeline

We're creating our pipeline files to build docker images and push to repositories, but we have 3 environments, so three docker repos. 

 

Each branch needs to configure the environement variables (different credentials, repository urls, etc), but there are common commands that need to run once the variables have been set. Is it possible to have specific commands for each branch and then common functionality that each branch executes? Something like this below: 

 

pipelines:

  alpha:

    - step:

        -DOCKERFILE=Dockerfile_alpha

        - ACCESS_KEY=Access_key_alpha

        - DOCKER_REPO=alpha_repo...

  production:

    - step:

        -DOCKERFILE=Dockerfile_production

        - ACCESS_KEY=Access_key_production

        - DOCKER_REPO=production_repo...

default:

   #this should execute for any branch, but after the branch specific commands

    - DOCKER push --access-key $ACCESS_KEY --url $DOCKER-REPO

1 answer

I would also like to define different environment variable values per branch.  I don't need the "common functionality" part, but I do need to be able to define different, secured environment variable values per branch.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,069 views 5 10
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you