Symptoms
Some text in the build logs that is not a password or token is masked with *.
Cause
When a build contains parameters of type password or secret, TeamCity does a basic replacement throughout the logs masking the actual password and/or secret values.
TeamCity runs external processes, and it doesn't have control over what those processes output to logs. As a result, TeamCity cannot define if the same strings as these parameters' values are output in places where they're not used as a secret or a password.
Resolution
Usually, such text replacement may indicate a weak password saved as a password-type parameter, or a parameter not intended to be secure (for example, URL) being saved with the password or secret type.
To resolve this, it is necessary to find which parameter is causing the masking and change it accordingly.
Additional information
Feature request for an easy way to see which parameter is causing the masking of the text in the logs: Easy way to see which parameter is causing the masking of the text in the logs
Comments
0 comments
Please sign in to leave a comment.