When, for example, you are sharing a step between a custom and a branch pipeline which requires a variable to be set, then you can set this variable in the custom pipeline with a custom manual pipeline variable ↑, but this leaves the variable unset in the branch pipelines.
If the VERSION
variable is a static value in the branch pipelines, you can set it in the workspace ↑, deployment ↑ or repository ↑ variables configuration. But if it is a dynamic value, based on your repository content, then shell parameter expansion [↑](https://www.gnu.org/software/bash/m