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?
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:
name: build (null)
name: Deploy to Test-East
name: Deploy to Test-West
name: Deploy to Test-South
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.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
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