Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,338
Community Members
 
Community Events
184
Community Groups

Running multiple steps on branch push with same deployment variables

Here's bitbucket-pipelines.yml format I am working on

 

image: xx

steps:
- step: &build-container
script:
- <BUILD SOMETHING>
- step: &deploy-container
script:
- <DEPLOY SOMETHING>

branches:
develop:
- step:
<<: *build-container
deployment: dev-custom
- step:
<<: *deploy-container
deployment: dev-custom

This gives the error `The deployment environment 'dev-custom' in your bitbucket-pipelines.yml file occurs multiple times`

This is very genuine scenario where I want to use the same deployment variables in two different steps. I want to create modular steps instead of one giant monster step.

This feature has been open with Bitbucket for at-least 3 years now but there is no traction on it.

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 14, 2022

Hi Divyang,

I understand the need for this feature, our development team has been working on this and it is expected to be released in Q3 2022, please see our roadmap below:

In case you haven't done so already, you can add yourself as a watcher in the feature request here https://jira.atlassian.com/browse/BCLOUD-18261, by selecting the Start watching this issue link, so that you get notified via email on updates. When this feature is released, we will update this feature request.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events