[
https://issues.jenkins-ci.org/browse/JENKINS-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Boissinot resolved JENKINS-12423.
-----------------------------------------
Resolution: Fixed
There is an incompatibility between the maskpassword plugin and the envinject
jenkins plugin. Both can't interact. MaskPasswork provides its own class and
EnvInject can't retreive them dynamically.
With the fix, EnvInject plugin incorporates all features of the Mask password
plugin.
You no longer need of the maskpasswords plugin. For now, you inject passwords
variables (global passwords - aka for all jobs, and job password) with only the
EnvInject plugin.
Process in your job configuration,
> Build Environment > Inject passwords to the build as environment variables
> 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: Gregory Boissinot
>
> 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
