[ https://issues.jenkins-ci.org/browse/JENKINS-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159063#comment-159063 ]
gbois commented on JENKINS-12423: --------------------------------- You're right. I forgot to test global passwords with the mask-passords plugin. However job password parameters (in the core and in the core passwords plugin) works as expected in the envinject plugin. I looked at the code. It's a big issue. Does it suit you if you manage global passwords by the EnvInject plugin. In my opinion, managing passwords directly in the envinject plugin is the best way to deal with this issue. > 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