Repository variables are case in-sensitive

Michal Czuper_3hod8e

When adding new repository variables we've noticed that they're case in-sensitive.
i.e. we're trying to add a `HTTPS_PROXY` variable along with a `https_proxy` variable.

However the second one fails with error `Variable name must be unique.`.
It does not, it's an environment variables and it's unique due to its case.

Unfortunately there is no standard for proxies in linux and different tools use one or the other version of the environment variables.

Theodora Boudale

Hi Michal and welcome to the community!

Environment variable names are case-sensitive in Linux, but they are not case-sensitive in Windows. We have customers who use repository variables in Pipelines builds running with self-hosted Windows runners.

If the value of HTTPS_PROXY is the same for all repos in the workspace, you could use a workspace variable for HTTPS_PROXY (and a repository variable for https_proxy). Another option is to define the second variable in the bitbucket-pipelines.yml file with a command in the script of the step that needs it. You could also define these variables in a file stored in your repo and then source the file in the yml file, in the script of the step that uses them.

Kind regards,
Theodora