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

Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Jenkins 2.222

      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

          A. Jard created issue -
          A. Jard made changes -
          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
          A. Jard made changes -
          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

          A. Jard added a comment -

          Updating description to match the name agreed on Jep and google group discussion (from CONFIGURE to MANAGE). CONFIGURE should not be anywhere anymore.

          A. Jard added a comment - Updating description to match the name agreed on Jep and google group discussion (from CONFIGURE to MANAGE). CONFIGURE should not be anywhere anymore.
          A. Jard made changes -
          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]
          Wadeck Follonier made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Wadeck Follonier made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]

          Simpler version proposed: https://github.com/jenkinsci/jenkins/pull/4501
          (next weekly release will be 2.221)

          Wadeck Follonier added a comment - Simpler version proposed: https://github.com/jenkinsci/jenkins/pull/4501 (next weekly release will be 2.221)
          Wadeck Follonier made changes -
          Released As New: 2.221
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Oleg Nenashev made changes -
          Released As Original: 2.221 New: Jenkins 2.222

            ajard A. Jard
            ajard A. Jard
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: