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,457,480
Community Members
 
Community Events
176
Community Groups

Optional steps in bitbucket pipelines

Edited

Hi,

I was building the CI/CD system, and I realized there was something lacking for our use case. Let me explain:

We have different teams with different test environments (deployments), like uat1, aut2, uat3.

When it's time to push the changes to the environment, ideally a team could trigger a custom pipeline that would do 2 steps: 1) build the image and 2) deploy it to their own environment.

So the way it'd be best, is to have an input variable to define where to deploy in step2

Something like a conditional step would work here, anytime the input variable could be used for the conditional.

Does anyone have the same workflow?

1 comment

I'd love to know if you found a good solution to this?

No good solution, but duplicating pipelines... it requires a conditional execution of deployment based on some var in the scope to do this in a good way. Ideally this thread could turn into a feature request. 

Thanks for the reply. I was considering using some sort of user account variable which would modify the pipeline to deploy to a different environment. Not ideal but a possible solution that I'll try later in the week.

There exsists an issue for further discussion.

Like # people like this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events