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; } } }

Bitbucket has unexpected behaviour with masked variables

Kimberling Yarihuaman_hi3aur

Hi!

Bitbucket has unexpected behaviour when I use masked variables. The pipeline logs show the variable names. I attached some screenshots.

- Pipeline logs with masked variable

Captura de pantalla 2025-02-01 001634.png

- Masked variable into Repository Variables. The variable value is 1

Captura de pantalla 2025-02-01 001919.png

Can you help me with this issue?

Thans in advance.

Accepted answers

Ben

Hi @Kimberling Yarihuaman

This is by design. Secure variables are supposed to be secret and not exposed (for example: tokens/app passwords/ssh keys/passwords).

If you wish to see the value of that variable exposed in your build logs, you'll need to add it as a non-secured variable.

Cheers!

- Ben (Bitbucket Cloud Support)

All comments

Ben

Hi @Kimberling Yarihuaman

This is by design. Secure variables are supposed to be secret and not exposed (for example: tokens/app passwords/ssh keys/passwords).

If you wish to see the value of that variable exposed in your build logs, you'll need to add it as a non-secured variable.

Cheers!

- Ben (Bitbucket Cloud Support)

Kimberling Yarihuaman_hi3aur

Hi Ben!

I understand you, but my doubt is why the variable name is shown in logs if those datas shouldn´t be replaced by variables. For example, the following texts should only show the quantity failed and passed tests, not the variable name, because they are not related to that.

Captura de pantalla 2025-02-07 230427.png

If you need more information, please let me know.

Cheers!

Ben

Hi Kimberling,

Pipelines has no way of knowing if the data in your secured variable is related to the values in your tests.

It simply checks to see if any values in the output match secured variables and masks them to prevent exposure of these secured variables in the build logs.

If you store "1" as an unsecured variable - you won't see this problem anymore.

Cheers!

- Ben (Bitbucket Cloud Support)

Kimberling Yarihuaman_hi3aur

Hi Ben!

Thanks so much.

Cheers!

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

pipelines