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

Avoid duplicating deployment code for two branches in BitBucket pipelines

basvdijk I'm New Here Apr 29, 2021

I have the following BitBucket pipeline script which preserves some files, does deployment and restores the files.

As shown this applies to the master branch. For the development branch I need exactly the same script. The only difference is that deployment: production will become deployment: development since I need other environment variables, set in BitBucket.

I've looked into https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/ for YAML anchors to make this script as a function. But couldn't get it to work.

Is there a way to avoid this part being copied for the development branch?

branches:
master:
- step:
name: Deployment to production
deployment: production
trigger: manual
script:
- echo "Deploying to prod..."
- pipe: atlassian/scp-deploy:1.0.1
variables:
USER: $DOMAIN
SERVER: $SERVER
REMOTE_PATH: '~/public/prod'
LOCAL_PATH: 'dist/*'

 

1 answer

0 votes

Hi @basvdijk ,

Thank you for your question!

We have tested examples provided in the  YAML anchors guide and overrides works good, where variable NAME setup in different deployments (test, development, production):

definitions: 
steps:
- step: &build-test
name: Build and test
script:
- echo "Build and test"

- step: &deploy
name: Deploy
deployment: test
script:
- echo "Hello ${NAME}"

pipelines:
branches:
development:
- step: *build-test
- step: *deploy
- step:
<<: *deploy
name: Deploy development
deployment: development

master:
- step: *build-test
- step:
<<: *deploy
name: Deploy Test
- step:
<<: *deploy
deployment: production
trigger: manual

 

It could be useful to check names for your deployments, because by default it starts with capital letter but you use small instead: Test vs test, Production vs production.


It would be nice if you provide us with more details to help you.

Cheers,
Oleksandr Kyrdan

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...

1,000 views 20 11
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