[JIRA] (JENKINS-55052) Different behavior accessing user credentials using RunAs Specific vs. Triggered User

[michael.i.ah...@gmail.com (JIRA)]

Title: Message Title

Michael Ahern edited a comment on JENKINS-55052   Re: Different behavior accessing user credentials using RunAs Specific vs. Triggered User Apologies, so my use case is slightly different than JENKINS 24750. In that case it regards propagation of Credential Parameter values along a call chain: withCredentials([usernameColonPassword(credentialsId: '${CREDENTIAL_PARAM}', variable: 'SOME_VALUE')])   In my case, I am simply attempting to access the User's credential directly by id: withCredentials([usernameColonPassword(credentialsId: 'user-private-credential', variable: 'SOME_VALUE')])   After a bit of debugging, I discovered that the issue is that "Queue.WaitingItem.getCause()" is always empty (i.e. the "UserIdCause" is not propagated correctly): {code:java} if (item instanceof Queue.WaitingItem && item. getCauses().isEmpty()) { /* Always true for if (item instanceof Queue.WaitingItem) */ }{code} [~ikedam] - is this by design or a defect in the system?   Either way, I extended the plugin with an optional (false by default) checkbox which provides a workaround. Will follow up on a Pull Request with a request for assistance to either track down the underlying defect (if this behavior is not by design) or for pointers as to how to implement a suitable unit test to get the patch accepted.   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.