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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Improvements to deployments

Hi there,

currently I configure my pipeline and I found several issues while working with the deployment feature. Here's what:


Why is it not possible to mark a parallel step as a deployment?

I have one step to build my project (composer install) and then two following parallel steps:

Bildschirmfoto 2018-12-13 um 10.38.59.png

I run them in parallel to save time. mortimer is a test stage and it takes a while to provision it, deploy the app and run the tests. So it is a deployment to test and it should be marked as such.

It is even your recommendation to run tests in parallel. Now, UI tests do not run in a black hole, but most of the time you need to spin up some environment and deploy the application there. I don't see why this cannot be part of a parallel step?


Why is it not possible to mark two steps as deployment to the same stage (e.g. staging)?

I have (at least) two staging servers where I want to have the possibility to manually test and review feature branches in isolation. How can I implement this in bitbucket pipelines? What I tried is to mark the two staging deployment steps as trigger: manual. This does not work as:

a) bitbucket restricts the deployment: staging flag to one occurence per pipeline(?)

b) bitbucket would not let me skip one step

It is definitely possible to skip a step in gitlab. For a scenario where I want to trigger manual deployments through the pipeline (which is quite common), this is a must. 


Could you please help me figure out how I can achieve my vision of our pipeline setup or how to work around this?



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events