|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Well, yes and no.
http://myjenkins.example.com/job/myjob/site/xref/index.html and http://myjenkins.example.com/job/myjob/com.example.group$module/lastSuccessfulBuild/artifact/com.example.group/module/1.0.0-SNAPSHOT/module-1.0.0-SNAPSHOT-sources.jar can, I think, be considered "accessing sources from Jenkins", if only because these URLs start with http://myjenkins.example.com/job/myjob/
Still, the workspace is the workspace, so probably accessing these other source locations should just require its own permissions (different from Job/Read, I mean).
Anyway, I will try to come up with a better wording for the tooltip on this one.