-
Improvement
-
Resolution: Fixed
-
Minor
For the new feature "Global name/password pairs", it seems the parameters cannot be accessed in a build step unless the check box "Mask passwords" is selected.
I think this should not be required. It is also confusing to the user, because the check box is labeled "Mask passwords", and the help says
"When enabled, allows masking passwords that may appear in the console."
But for global name/password pairs this check box has an additional functionality.
If think global parameters should always be accessible per default. Currently, for global passwords this is not the case.
[JENKINS-11924] Improve global passwords-related labels
Romain Seguy
added a comment - Delivered in 2.7.2 Code changed in jenkins
User: rseguy
Path:
src/main/resources/com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsBuildWrapper.properties
http://jenkins-ci.org/commit/mask-passwords-plugin/af704a362cec5376f1667b3107c6870126f7bd2a
Log:
[FIXED JENKINS-11924] Improve global passwords-related labels
"For the new feature "Global name/password pairs", it seems the parameters cannot be accessed in a build step unless the check box "Mask passwords" is selected" + "If think global parameters should always be accessible per default. Currently, for global passwords this is not the case"
==> It's technically impossible to mask global passwords if the build wrapper is not enabled. The Jenkins API doesn't provide facilities for that.
The only one thing I can do is to change the help message and to rename the "Mask passwords" label to something like "Mask passwords (and activate global passwords)".