Why only second step could be triggered manually?

Question

Just wondering, why there are the strange rule to trigger "manually" only second step in bitbucket-pipelines.yml ? For some reasons sometimes we need to have in the first step this option? Is there any workaround to setup this one in the first step, cause this empty first step to have second one is absolutely unnecessary and waste of bb minutes :)

Maybe someone has already found some workaround?

pipelines:
branches:
dev:
- step:
name: deploy to Staging
trigger: manual. <<<?
deployment: Staging
script:
- pipe: atlassian/rsync-deploy:0.5.0

Raju P.S · Answer

pipelines:custom:DevDeploy: - step:<<: *Database_migratename: Dev - Database_migratedeployment: DevUATDeploy: - step: <<: *Database_migratename: Staging - Database_migratedeployment: StagingThis will allow you to run both Dev and UAT deployments manually and independently.

Raimundas Ra · Answer

Hi Raju P_S , could you maybe share some examples ? Thank you :)

Raju P.S · Answer

Not sure, if it helps in your scenario, but we used "custom" flow, which will allow us to not only trigger manually, also to choose which individual step to run as well.