-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins ver. 2.107.3 on 4.1.12-112.14.13.el6uek.x86_64
I have user emreporter which doesn't have build permission for job "EM Ops - OMS - MIGDC2 EM OMS Patch (Real Run)" but can read the build history of the job. So, from Jenkins UI, the user can check the job execution history and go into a execution for example #16 to get its information in console.
However, when I am using CLI to get the console for latest job execution result, it reported error about the user is missing build permission.
That is to say, the behavior of CLI is not same to UI.
Here is the command result:
+ java -jar jenkins-cli.jar -s
http://MyJenkinsServer:8080
-http -auth emreporter:******** console 'EM Ops - OMS - MIGDC2 EM OMS Patch (Real Run)' -f
ERROR: emreporter is missing the Job/Build permission
Please see attached screenshot for the comparison result on both UI and CLI.
It looks like a real defect/RFE. Item.READ should be enough in the current permission model.
Generally a patch needed here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/ConsoleCommand.java#L44
This change was introduced in 2012 by the original commit (https://github.com/jenkinsci/jenkins/commit/63b6e0bc89c1a5885dd132329e3f149d58ad76bc), so it's not a regression.
ericyu2018 It seems to be an easy patch. Would you be interested to propose a pull request for review?