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

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

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Similar Issues:
    • Released As:
      Jenkins 2.222

      Description

      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

        Attachments

          Activity

          ajard A. Jard created issue -
          ajard A. Jard made changes -
          Field Original Value New Value
          Description 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.
          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
          ajard A. Jard made changes -
          Description 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
          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
          ajard A. Jard made changes -
          Description 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
          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]
          wfollonier Wadeck Follonier made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          wfollonier Wadeck Follonier made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          wfollonier Wadeck Follonier made changes -
          Released As 2.221
          Resolution Fixed [ 1 ]
          Status In Review [ 10005 ] Resolved [ 5 ]
          oleg_nenashev Oleg Nenashev made changes -
          Released As 2.221 Jenkins 2.222
          ajard A. Jard made changes -
          Epic Link JENKINS-61454 [ 205133 ]

            People

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

              Dates

              Created:
              Updated:
              Resolved: