Use variables in any part of your Pipelines .yaml

In the past, variables in Bitbucket Pipelines were scoped to only operate within script sections of a Pipelines workflow. This limited their usefulness and restricted users from being able to fully parameterize their workflows.

Today we are releasing an enhancement that will allow variables to be used within any section of a Pipelines .yaml file, and not just within scripts. This new capability will allow you to use variables to parameterize things like cache keys, artifact names, build images, and anything else you might need.

How it works

Templating variables into your .yaml file is done via a simple, standardized templating syntax (${{MY_VARIABLE_KEY}}) that many users will already be familiar with from other tools. Simply wrap the key of the variable you want to template into your .yaml between the ${{ }} tags, and the system will take care of the rest.

Example:

image: ${{IMAGE_NAME}}
definitions:
  caches:
    ${{CACHE_NAME}}: ${{CACHE_PATH}}

For more detailed information, check out the Variables and secrets help document.