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

Optional Deployment Environments

Curtis
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.
June 20, 2024

Is there a way to configure a PIpeline where it doesn't require deploying to every deployment environment. For example, if we have 3 dev environments, and want to only go to 1 of them, before moving on to one of the several qa servers.

Currently, I can't get it to progress to allow deployment to a qa server until it has deployed to all dev servers. Is there a way to bypass the standard BItbucket PIpeline deployment flow?

2 answers

2 accepted

1 vote
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 24, 2024

Hi Curtis,

If these deployments are all steps of the same pipeline, I'm afraid that it is not possible to skip one step and continue to the next one.

We have a feature request that you can vote for here:

In the meantime, you could create a separate custom pipeline for each deployment step, and then manually trigger only the custom pipeline you want.

Kind regards,
Theodora

0 votes
Answer accepted
Curtis
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.
June 28, 2024

All the deployment projects can be set as parallel, then there is the option to deploy them in any order. To set deployments as parallel, they must be configured part of the same deployment group.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events