[JIRA] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Leo Li commented on JENKINS-15769 Provide way to allow build icons without anonymous access. My use case, quoted directly from the plugin page "You can put this URL into other sites (such as GitHub README) so that people can see the current state of the build." With the restriction, of course, that the project being a private org repo. 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/groups/opt_out.
[JIRA] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Kohsuke Kawaguchi commented on JENKINS-15769 Provide way to allow build icons without anonymous access. A user without an overall read access to Jenkins is an user who is not supposed to see anything whatsoever in Jenkins. Letting them see the build status violates the access control model, and as a matter of fact the core doesn't even let us do that in the plugin. What's the use case for this? 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/groups/opt_out.
[JIRA] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Andrei Pozolotin commented on JENKINS-15769 Provide way to allow build icons without anonymous access. use case: publish public build status from private jenkins 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/groups/opt_out.
[JIRA] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Shawn Baker commented on JENKINS-15769 Provide way to allow build icons without anonymous access. My personal use case is that we have a Jenkins server that is separate from our Trac/Subversion server. Login information is different as well. But both systems are restricted to outside users. I would like to put the build status on the Trac wiki, but the user who is logged into Trac has different credentials on Jenkins, so the build status icons don't work. I hope this makes sense. 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/groups/opt_out.
[JIRA] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Leo Li
commented on JENKINS-15769
Provide way to allow build icons without anonymous access.
A very easy workaround would be that instead of having the entrypoint {JENKINS_URL}/job/{JOB_NAME}/badge/icon redirects to {JENKINS_URL}/static/{HASH?}/plugin/embeddable-build-status/status/{STATUS_IMAGE}, why not just generate the image and overwrite to a always fixed image link that is specified by the admin of the job/Jenkins server.
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/groups/opt_out.
[JIRA] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Shawn Baker created JENKINS-15769 Provide way to allow build icons without anonymous access. Issue Type: New Feature Affects Versions: current Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 08/Nov/12 2:34 PM Description: Currently, this plugin requires that the anonymous user has overall Read permissions on Jenkins. If you remove overall Read permission from the anonymous user, this plugin does not work. If the anonymous user has no Overall Read permissions, but has Job Read permissions, then the icons should still work. But it appears that Jenkins still wants the user to login. This might be a limitation of Jenkins authorization. Environment: Matrix-based security Project-based Matrix Authorization Strategy Project: Jenkins Labels: plugins Priority: Major Reporter: Shawn Baker 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
