|
||||||||
|
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.
Doing a configuration-time access check on a literal project name (one without variable expansions) makes sense but any failure should just be displayed as a FormValidation.warning; the real check should always be done at runtime. You would need to depend on 1.560+ and call Tasks.getAuthenticationOf so you can get the authentication outside the context of a specific build (or else check for this method using reflection and fall back to no validation).
I would avoid introducing system properties unless there is no alternative.