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

Replay link is shown to users with push access to repo, but replay page shows no script editor

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • github-oauth-plugin
    • None

      We have a user with push/pull access to a given Github repository. They can see a "Replay" link for a given build on that repo, but when they click it, they do not see any "Main Script" script editor box or label on the loaded page.

      I assume the plugin is restricting replay to admins only, but it's inconsistent given that the link is shown/available to them.

      Not sure if the "fix" would be to hide the link or show the script editor and allow users with push access to edit/replay.

      Seems related to JENKINS-47310

          [JENKINS-63080] Replay link is shown to users with push access to repo, but replay page shows no script editor

          Reinhold Füreder added a comment - - edited

          I stumbled over this bug as well, but it IMHO is not caused by component "github-oauth-plugin" (as we do not use it and it is not even installed):

          • We are using project-based security (via "Matrix Authorization Strategy" plugin) and even though the user does not have the permission "Run/Replay" the button is available and – as seadub reported – triggering unfortunately incorrectly even works (without the possibility to edit the script/s)

           => Maybe this ticket should be edited: update of title and involved component/s?

          Oh wait!

          • There are other related (open) issues (that are maybe much more appropriate for my use case: actually permission "Run/Update" is granted, but not "Job/Configure"):

          Reinhold Füreder added a comment - - edited I stumbled over this bug as well, but it IMHO is not caused by component "github-oauth-plugin" (as we do not use it and it is not even installed): We are using project-based security (via "Matrix Authorization Strategy" plugin) and even though the user does not have the permission "Run/Replay" the button is available and – as seadub reported – triggering unfortunately incorrectly even works (without the possibility to edit the script/s)  => Maybe this ticket should be edited: update of title and involved component/s? Oh wait! There are other related (open) issues (that are maybe much more appropriate for my use case: actually permission "Run/Update" is granted, but not "Job/Configure"): JENKINS-50855 JENKINS-47339 JENKINS-39874

            sag47 Sam Gleske
            seadub Chris Williams
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: