-
Suggestion
-
Resolution: Duplicate
-
None
I need to have an "optional: true/false" option available for steps. Imagine this scenario, where I have 5 DEV environments I can deploy to named DEV1, DEV2, DEV3, DEV4, DEV5. Right now, I'd set these up like so:
- parallel: - step: *Deploy-dev1 - step: *Deploy-dev2 - step: *Deploy-dev3 - step: *Deploy-dev4 - step: *Deploy-dev5
This works if all 5 steps are manual steps. The problem is however, what if I only want to deploy to DEV3? My only option is to go DEV1, then DEV2, then DEV3. I can't just click the button for DEV3.
I would like the option to mark all 5 of those steps as optional, so I can click them in any order to deploy to my chosen environment.
Another scenario is the following. Say I have two DEV environments DEV1, DEV2, one STG environment STG1, and one PROD environment PROD1. You cannot do this:
- parallel: - step: *Deploy-dev1 - step: *Deploy-dev2 - step: *Deploy-stg1 - step: *Deploy-prod1
Because bitbucket-pipelines will not allow you to mix DEV, STG, and PROD steps in a parallel group. I would really like the ability to set a step as optional or to be able to ignore a step and mark it as complete or some other similar functionality.
- duplicates
-
BCLOUD-20833 Skip steps based on condition - Include SKIP and RUN on manual steps
- Under Consideration
Optional Bitbucket Deploy Steps
-
Suggestion
-
Resolution: Duplicate
-
None
I need to have an "optional: true/false" option available for steps. Imagine this scenario, where I have 5 DEV environments I can deploy to named DEV1, DEV2, DEV3, DEV4, DEV5. Right now, I'd set these up like so:
- parallel: - step: *Deploy-dev1 - step: *Deploy-dev2 - step: *Deploy-dev3 - step: *Deploy-dev4 - step: *Deploy-dev5
This works if all 5 steps are manual steps. The problem is however, what if I only want to deploy to DEV3? My only option is to go DEV1, then DEV2, then DEV3. I can't just click the button for DEV3.
I would like the option to mark all 5 of those steps as optional, so I can click them in any order to deploy to my chosen environment.
Another scenario is the following. Say I have two DEV environments DEV1, DEV2, one STG environment STG1, and one PROD environment PROD1. You cannot do this:
- parallel: - step: *Deploy-dev1 - step: *Deploy-dev2 - step: *Deploy-stg1 - step: *Deploy-prod1
Because bitbucket-pipelines will not allow you to mix DEV, STG, and PROD steps in a parallel group. I would really like the ability to set a step as optional or to be able to ignore a step and mark it as complete or some other similar functionality.
- duplicates
-
BCLOUD-20833 Skip steps based on condition - Include SKIP and RUN on manual steps
- Under Consideration