Build Parameter hostname obscuration

Answered

I have an upstream build that generates a URL called custom branch using a powershell script in a build step.

 

The parameter shows up in build parameters as 

CustomBranch http://*******-ebmm.pull.6012.stg-oc.*******.com  

 

Is it teamcity that is doing the hostname substitution ?

My problem is that it is passing down the URL still with the ****** to the next build down the chain.

 

 

1 comment
Comment actions Permalink

Hello!

Could you please share the script used? Do the masked parts match any of the password-typed parameters?
In case you update parameter via setParameter service message, technically, this is a log output - and TeamCity would obscure any value in the logs which matches known password to avoid data leaks.

0

Please sign in to leave a comment.