I'm using atlassian/trigger-pipeline - can I request WAIT but not fail the entire build on failure?

[marklaff]

I have a master pipeline with many (33?) build steps that each invoke atlassian/trigger-pipeline. I want the results of each sub-build to be reported in this build, so I use the "WAIT=true' option.

I would like all 33 to run even though one or more of the sub-builds fail. Can I do that?

Here's an example of one of the 33 sub-build steps:

- step:
    script:
      - pipe: atlassian/trigger-pipeline:4.2.1
        variables: &base
          BITBUCKET_USERNAME: "${FOO_PIPELINE_USER}"
          BITBUCKET_APP_PASSWORD: "${FOO_PIPELINE_PASS}"
          BRANCH_NAME: "$BITBUCKET_BRANCH"
          WAIT: "true"
          DEBUG: "false"
          REPOSITORY: "foo-shared"

[Oleksandr Kyrdan · Accepted solution]

Hi @marklaff ,

Thank you for your question!

It's a good case for Set up or run parallel steps :

pipelines:
  default:
    parallel:
    - step:
        script:
          - pipe: atlassian/trigger-pipeline:4.2.1
            variables:
              BITBUCKET_USERNAME: "${FOO_PIPELINE_USER}"
              BITBUCKET_APP_PASSWORD: "${FOO_PIPELINE_PASS}"
              BRANCH_NAME: "$BITBUCKET_BRANCH"
              WAIT: "true"
              DEBUG: "false"
              REPOSITORY: "foo-shared-1"
    - step:
        script:
          - pipe: atlassian/trigger-pipeline:4.2.1
            variables:
              BITBUCKET_USERNAME: "${FOO_PIPELINE_USER}"
              BITBUCKET_APP_PASSWORD: "${FOO_PIPELINE_PASS}"
              BRANCH_NAME: "$BITBUCKET_BRANCH"
              WAIT: "true"
              DEBUG: "false"
              REPOSITORY: "foo-shared-2"

Cheers,
Oleksandr Kyrdan

[marklaff]

Hi @Oleksandr Kyrdan , thanks for your quick answer. That makes sense - I will try that.