Why Manual Deploy trigger cannot be clicked

[xicond]

Why Manual Deploy trigger cannot be clicked when intermediate step also manual trigger is not finished yet,

Somehow I need to skip intermediate step, as it optional,

Ex.

Below, the third step deploy cannot be click

- step:
    name: Build & Testing (v16)
    image: node:16-alpine3.11
    deployment: v16
    artifacts:
        - build/**
- step:
    name: Build & Testing (v14)
    image: node:16-alpine3.11
    trigger: manual
    deployment: v14
    artifacts:
        - build/**
- step:
    name: Deploy to S3
    deployment: production
    trigger: manual

 Or

- parallel:
    - step:
          name: Build & Testing (v16)
          image: node:16-alpine3.11
          deployment: v16
          artifacts:
              - build/**
    - step:
          name: Build & Testing (v14)
          image: node:16-alpine3.11
          trigger: manual
          deployment: v14
          artifacts:
              - build/**
- step:
      name: Deploy to S3
      deployment: production
      trigger: manual

[Theodora Boudale · Accepted solution]

Hi @xicond,

I'm afraid that it is not possible to skip a step in a pipeline that consists of multiple steps. This is the case for both the first example you posted (3 sequential steps) and also for the second one (the two parallel steps need to get completed in order to trigger the last one).

We have a feature request in our issue tracker for the ability to skip manual steps:

• https://jira.atlassian.com/browse/BCLOUD-20833

Since you'd be interested in that feature, I would suggest adding your vote to that feature request (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

In the meantime, a way to work around this issue would be by creating a custom pipeline for the step that is optional and another one for the deploy step, which can be triggered manually or scheduled from the Bitbucket Cloud interface:

• https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml/#custom

Kind regards,
Theodora