[
https://issues.jenkins-ci.org/browse/JENKINS-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158859#comment-158859
]
Mike Winters commented on JENKINS-12423:
----------------------------------------
In the case of the Perforce passwords, the issue was happening before I
installed the Mask Passwords plugin (I only installed that in an attempt to
hide the passwords). It seems that perhaps the Perforce plugin (and plugins for
other source control systems?) are exposing the passwords in a way that the
EnvInject plugin doesn't know to look for. I'm not sure where the best place to
fix this is, or what the optimal fix should be, as I am not familiar with the
Jenkins codebase or the code for any of the relevant plugins. However, the
quicker a solution can be implemented, the happier I will be :). Thanks!
> Password masked by Mask Passwords are visible when using envinject plugin
> -------------------------------------------------------------------------
>
> Key: JENKINS-12423
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12423
> Project: Jenkins
> Issue Type: Bug
> Components: envinject, mask-passwords, perforce
> Environment: envinject 1.9
> mask-passwords 2.7.2
> Jenkins ver. 1.424.1
> Windows
> Perforce plugin 1.3.7
> Reporter: Roger Myung
> Assignee: gbois
>
> If I use the mask-passwords plugin to create a masked password, and also use
> the envinject plugin to setup an environment, the masked password is visible
> from the "Injected Environment Variables" link for each build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
