Why can't the first step be manual in bitbucket pipeline? Can we add some random step to bypass it?

[Sudip Bhandari]

The first step of your bitbucket-pipelines.yml cannot be manual. Please remove this trigger from you

[Graham Gatus]

@Sudip Bhandari what is your use case for wanting to have a manual step appear first in your pipeline? You can configure custom steps (see https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html#Configurebitbucket-pipelines.yml-ci_custom ), and execute these against any branch in your repository manually as needed.

[Vipul Chaudhary]

The usecase is to avoid wasting build time for every commit we make

[SPence]

A more useful use case is to manually deploy only certain artifacts.  In deployment using a multi module maven project maybe you only want to deploy one or two or 5 etc...  Being limited to a step by step deployment to get to the 5th project makes this unusable

[Shubham Pai]

Who cares what our usecase is? This can't possibly be that difficult to enable as a feature. I feel like you'd intentionally have to put a rule in that the first step can't be manual. I feel like bitbucket managers have created this narrative of assumptions of their customers usecases and then have created a product with so many unintuitive roadblocks. Bitbucket pipelines are the sole reason I'm pushing my company to use gitlab CI or github Actions instead.