|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Paul Allen you need to specify @NameWith on P4Credentials or perhaps concrete subtypes such as P4PasswordImpl. See https://github.com/jenkinsci/plain-credentials-plugin/blob/445994d3d7f268731aca463887a4a835287901e2/src/main/java/org/jenkinsci/plugins/plaincredentials/StringCredentials.java#L37 as an example. From those screenshots it does not appear that you ever ask the user to select a particular credentials directly (perhaps you find one automatically based on field matches?), so you might not have ever had cause to call CredentialsNameProvider.name (or use something which does, such as <c:select>) and discover that the result is not helpful.
Sangeeta Narang you cannot expect the maintainer of an OSS plugin to even know what you are talking about when discussing an issue only reproducible in combination with Jenkins Enterprise plugins. When encountering issues like these it is better to file a support ticket so that CloudBees engineering can evaluate the situation and decide whether a fix in an OSS plugin is warranted, and if so to file it with adequate background information.
stephenconnolly do you know why StandardCredentials.NameProvider is not kicking in as a fallback here?