-
New Feature
-
Resolution: Fixed
-
Minor
-
None
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here https://github.com/jenkinsci/jep/pull/249
The main goal is to have a new permission called `Jenkins.MANAGE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`.
The draft PR with this new permission implementation is https://github.com/jenkinsci/jenkins/pull/4374
[JENKINS-60266] Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER
Description |
Original:
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249] The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation will be proposed soon, I will update this Jira when it's done. |
New:
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249] The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation will be proposed soon, I will update this Jira when it's done. Feedback are welcome, you can also see the announcement on the dev list: https://groups.google.com/forum/#!topic/jenkinsci-dev/lThSifB8G4k |
Description |
Original:
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249] The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation will be proposed soon, I will update this Jira when it's done. Feedback are welcome, you can also see the announcement on the dev list: https://groups.google.com/forum/#!topic/jenkinsci-dev/lThSifB8G4k |
New:
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249] The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation is https://github.com/jenkinsci/jenkins/pull/4374 |
Description |
Original:
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249] The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation is https://github.com/jenkinsci/jenkins/pull/4374 |
New:
I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249] The main goal is to have a new permission called `Jenkins.MANAGE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation is [https://github.com/jenkinsci/jenkins/pull/4374] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Released As | New: 2.221 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
Released As | Original: 2.221 | New: Jenkins 2.222 |
Updating description to match the name agreed on Jep and google group discussion (from CONFIGURE to MANAGE). CONFIGURE should not be anywhere anymore.