nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pipeline with multiple scripts runs only the last one (broken)

A360 Bitbucket Admin

The following script used to work perfectly fine up until a few days ago when it all of a sudden decided to only execute the most recent anchored script.

pipelines: 
  custom: 
    my-custom-pipeline: 
      - step: 
          script:
            - echo "FIRST"
          script:
            - echo "SECOND"

In the above example when my-custom-pipeline is run only "SECOND" is echoed. If I remove the second script then "FIRST" is echoed.

This is a fairly new issue as my pipeline of multiple scripts (anchored scripts, in fact) used to run flawlessly. Did someone put a bug in the YAML parser without documenting it?

Accepted answers

Steven Vaccarella

Hi Mostafa,

I'm not aware of any recent change to the parsing logic that would explain this change in behaviour. However I can say that we never intended to support duplicate map keys in a deterministic way, so I'd highly recommend updating your pipeline definitions to avoid duplicate keys.

Kind Regards,
Steven Vaccarella

All comments

Steven Vaccarella

Hi Mostafa,

Kind Regards,
Steven Vaccarella

A360 Bitbucket Admin

Thanks Steven. What about supporting multiple anchored scripts like below?

definitions: 
  script: &My-Script-A
    - ...
  script: &My-Script-B
    - ...
pipelines: 
  custom: 
    my-custom-pipeline: 
      - step: 
          script: *My-Script-A
          script: *My-Script-B

The above pipeline used to run just fine, but now only the last script gets executed.

If this is non-deterministic is there a way to make the keys unique and achieve the same result?

Steven Vaccarella

To my knowledge there is no way to do what you're trying to do directly in the yaml file in a robust way.

Our recommendation for reusing scripts is to move them to separate script files in your repo and then invoke the required scripts from a single "script" section in the yaml.

ie.

pipelines: 
  custom: 
    my-custom-pipeline: 
      - step: 
          script:
             - 'pipeline-scripts/my-script-a.sh'
             - 'pipeline-scripts/my-script-b.sh'

[OLD PREKARILABS] Timothy Blumberg

Posting this here so that the next person can see it directly. The above didn't work for me directly, I had to use the following:

pipelines:
  default:
    - step:
        script:
          - ./pipeline-scripts/common-build-test.sh

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines

atl-pipelines