Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,296,650
Community Members
 
Community Events
165
Community Groups

Why Manual Deploy trigger cannot be clicked

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

 

1 answer

1 accepted

0 votes
Answer accepted

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:

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:

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,198 views 2 9
Read article

Community Events

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

Events near you