Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15769

Provide way to allow build icons without anonymous access.

    Details

    • Similar Issues:

      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.

        Attachments

          Issue Links

            Activity

            scb147 Shawn Baker created issue -
            Hide
            woozyking Leo Li added a comment -

            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.

            Show
            woozyking Leo Li added a comment - 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.
            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            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?

            Show
            kohsuke Kohsuke Kawaguchi added a comment - 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?
            Hide
            andrei_pozolotin Andrei Pozolotin added a comment -

            use case: publish public build status from private jenkins

            Show
            andrei_pozolotin Andrei Pozolotin added a comment - use case: publish public build status from private jenkins
            Hide
            scb147 Shawn Baker added a comment -

            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.

            Show
            scb147 Shawn Baker added a comment - 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.
            Hide
            woozyking Leo Li added a comment -

            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.

            Show
            woozyking Leo Li added a comment - 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.
            Hide
            rollup Maciej Gąsiorowski added a comment - - edited

            Publish build status on Gitlab/Trac etc.

            Show
            rollup Maciej Gąsiorowski added a comment - - edited Publish build status on Gitlab/Trac etc.
            Hide
            woozyking Leo Li added a comment - - edited

            Is this fixed by https://issues.jenkins-ci.org/browse/JENKINS-17798 ?

            EDIT: I think it did, at least provided a workaround good enough to close this ticket.

            Show
            woozyking Leo Li added a comment - - edited Is this fixed by https://issues.jenkins-ci.org/browse/JENKINS-17798 ? EDIT: I think it did, at least provided a workaround good enough to close this ticket.
            Hide
            rollup Maciej Gąsiorowski added a comment - - edited

            Thanks for the info Leo Li

            Works well.

            Show
            rollup Maciej Gąsiorowski added a comment - - edited Thanks for the info Leo Li Works well.
            Hide
            mgedmin Marius Gedminas added a comment -

            If I understand it correctly, this was fixed in version 1.4.

            Show
            mgedmin Marius Gedminas added a comment - If I understand it correctly, this was fixed in version 1.4.
            mgedmin Marius Gedminas made changes -
            Field Original Value New Value
            Link This issue duplicates JENKINS-17798 [ JENKINS-17798 ]
            Hide
            mgedmin Marius Gedminas added a comment -

            If I understand this issue correctly, it was fixed in version 1.4.

            Show
            mgedmin Marius Gedminas added a comment - If I understand this issue correctly, it was fixed in version 1.4.
            mgedmin Marius Gedminas made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Hide
            behcet Behcet Uyar added a comment -

            Sorry to bump this resolved ticket but this is not possible when using "Github Commiter Authorization Strategy"

            Show
            behcet Behcet Uyar added a comment - Sorry to bump this resolved ticket but this is not possible when using "Github Commiter Authorization Strategy"
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 146570 ] JNJira + In-Review [ 191981 ]

              People

              • Assignee:
                kohsuke Kohsuke Kawaguchi
                Reporter:
                scb147 Shawn Baker
              • Votes:
                3 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: