I have a pipeline that i want all the branches steps run in a manual mode

[Deleted user]

definitions:

services:

# Define the default Docker service with 2 GB memory limit

docker:

memory: 1024

# Define the Docker service which requires 6 GB memory

docker-7g:

# You will have to define the service type if it is docker

type: docker

memory: 7168

pipelines:

custom:

sandbox:

- step:

name: Push

image: atlassian/pipelines-awscli

# Pass the Docker service with 7 GB

services:

- docker-7g

oidc: true

# Raise the Step limit from 4 GB to 8 GB.

size: 2x

script:

.

.

.

- step:

name: deploy

image: atlassian/pipelines-awscli

services:

- docker

oidc: true

script:

.

.

.

services:

- docker

>>>>>(I want from here that starts the branches mode to be manual)    <<<<<

branches:

staging:

- step:

deployment: staging

name: Push

image: atlassian/pipelines-awscli

# Pass the Docker service with 7 GB

services:

- docker-7g

oidc: true

# Raise the Step limit from 4 GB to 8 GB.

size: 2x

script:

.

.

.

.

- step:

name: deploy

image: atlassian/pipelines-awscli

services:

- docker

oidc: true

script:

.

.

.

services:

- docker

[Patrik S]

Hello @[deleted] ,

Thank you for reaching out to Atlassian Community!

If you want all the steps of your branch pipelines to be fully manual, my suggestion would be that you create them as custom pipelines, instead of branches. With custom pipelines, you can manually trigger them from the Pipelines page, and select from which branch you want them to run against. You can even give each custom pipelines the same name of the branch they are supposed to run, so it makes it easier from you to pick the correct pipeline for the correct branch when manually triggering it, as the example below : 

 custom: # Pipelines that can only be triggered manually
   master:
     - step:
        script:
         - echo "This is a custom pipeline"
   development:
     - step:
        script:
         - echo "This is a custom pipeline"

However, if what you want is to define just a set of steps to be manual, you can make use of the trigger: manual option in the steps that you want to be manually run : 

branches: 
 master:
  - step:
    name: 'First step'
    script:
     - echo "This step runs automatically"
  - step:
    name: 'Second step'
    trigger: 'manual'
    script:
    - echo "This step needs to be manually triggered"

Please note that the first step of a pipeline cannot be configured as manual. You have the option to create a dummy step in your first step as a workaround, but for full manual pipelines, the recommendation would be to use the custom trigger as mentioned above.

More details on pipeline triggers are in the documentation below : 

• https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/

Hope that helps! Let me know if you have any questions.

Thank you, Joao!

Kind regards,

Patrik S