Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Run deploy step withou run previus one

iurisoftfocus
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 2, 2020

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?

Seleção_046.png

 

1 answer

1 vote
ktomk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 5, 2020

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:

Selection_053.png

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

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

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

Selection_054.png

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events