The username being part of the credentials, I believe it being masked like
the password is a correct behavior.
If you'd like it to behave differently, I think you want to use something
else then a credz type. But don't tell anyone I'm telling you to put your
username as a string parameter, I'm
On Tue, May 21, 2019 at 7:26 AM Tim Jaacks wrote:
> Thanks very much for the link. That is indeed exactly my issue.
>
> Is there an alternative to using the credentials binding plugin? I need
> the credentials to be inserted into an URL within the test script. How can
> I do this without the
Thanks very much for the link. That is indeed exactly my issue.
Is there an alternative to using the credentials binding plugin? I need the
credentials to be inserted into an URL within the test script. How can I do
this without the credentials binding plugin?
Am Dienstag, 21. Mai 2019
Based on https://issues.jenkins-ci.org/browse/JENKINS-44860 , it appears to
be the credentials binding plugin. Sorry for my misdirection.
On Tue, May 21, 2019 at 5:36 AM Tim Jaacks wrote:
> Thanks for your reply, Mark. I am using the credentials plugin to provide
> the stated credentials and I
Thanks for your reply, Mark. I am using the credentials plugin to provide
the stated credentials and I thought, that it is actually this plugin which
performs the masking. If not, which plugin does this? I did not find any
installed plugins in my instance which seem to do this.
Am Dienstag,
On Tue, May 21, 2019 at 5:24 AM Tim Jaacks wrote:
> While this makes sense for actual occurrences (i.e. where the asterisk'ed
> text REALLY is my user name), it is quite counterproductive in situations
> where the user name accidentally matches some other strings in the log.
>
> For example, my
