Bitbucket Pipeline Hack: Wrapping multiline script command

[#1]

I had a really long command in my pipeline file, and being a programmer I can't tolerate anything longer than 120 columns (it was 80, but with modern screen real estate I think 120 is good number).

This is how my file looked like,

As you can see my really long command is going pass editor screen. So, how do we wrap this?

bitbuket-pipeline.yml file is YAML file, and after visiting and reading RFC for YAML, I had a eureka moment. The magical symbol is '>-' for non white space multiple lines.

So my file now look like this,

Isn't it more beautiful?

[jjmontgo]

The newlines get stripped out and your echo statement ends up displaying just 1 line.

How would I preserve the newlines?

[Josia]

https://yaml-multiline.info/ helps a lot with styling multiline yaml entries

[Jason Harrison]

If you want to have more than one command in your script you can start up the next command with a "-" prefix after the last newline:

pipelines: default:
  - step: 
      name: Run Default Unit Tests 
      caches: 
        - pip 
      script: 
        - ./scripts/bitbucket-log-time-and-version.bash 
        - >- if [ -z "${ENV_I2LStaging_base64}" ]; then 
                 echo "ENV_I2LStaging_base64 is not set or empty!"; 
                 exit 1; 
             fi 
         - echo $ENV_I2LStaging_base64 | base64 --decode --ignore-garbage > .env 
         - ./scripts/bitbucket-install-python-packages.bash --run-unit-tests 
         - ./scripts/bitbucket-run-benchmark.bash 
         - ./scripts/bitbucket-log-time-and-version.bash.