Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • 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
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?
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

Run deploy step withou run previus one

I would like to know if there is a way to run one step without running the previous one.

Like in the picture below the last deploy is disabled until I run the seconde deploy.

Can I configure de pipelines to allow me to run this deploys without an order?



1 answer

The Deploy button is disabled unless the previous step in a pipeline was successful.

In your case this is the reason why the last Deploy button is still grayed out - the previous step Deploy XXX did not yet finish w/ success.

This obviously is by design but in context of your question this looks more like it is standing in your way.

By design means, you can create a ladder of deployments ( build -> test -> staging -> production) for which each step must pass before the next step can be triggered.

However your scenario might be to have the same kind of deployment just to different environments ( build -> test-east + test-west + test-south). In this case you can make use of parallel steps. This works as long as the deployments in parallel steps are from within the same deployment environment.

This looks then like this:


This is from a test pipeline, I didn't use manual steps which is why all is already with the Redeploy button state:

- step:
image: ktomk/pipelines:busybox
name: build (null)
- printenv
- parallel:
- step:
name: Deploy to Test-East
deployment: Test-East
- printenv
- step:
name: Deploy to Test-West
deployment: Test-West
- printenv
- step:
name: Deploy to Test-South
deployment: Test-South
- printenv

All those three deployment environments are Test environments here, screenshot from the deployment repository settings page:


If this matches your needs then parallel steps is the answer.

Suggest an answer

Log in or Sign up to answer
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...

992 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