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

Admin users could be defined as organization*team too

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • github-oauth-plugin
    • None

      Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.

      Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful.

       

      edit: migrated description from environment by sag47

          [JENKINS-43078] Admin users could be defined as organization*team too

          Aleksi Aalto created issue -

          Sam Gleske added a comment -

          This is already possible using one of the matrix-based authorization schemes.

          Sam Gleske added a comment - This is already possible using one of the matrix-based authorization schemes.

          Aleksi Aalto added a comment -

          Thanks, how could I miss that!

          Would it still be useful to have it possible if someone wants to use the "GitHub Committer Authorization Strategy"?

          Aleksi Aalto added a comment - Thanks, how could I miss that! Would it still be useful to have it possible if someone wants to use the "GitHub Committer Authorization Strategy"?

          Sam Gleske added a comment -

          I think the GitHub Committer Authorization Strategy needs a complete overhaul.  The way I'd like to see it done is akin to the matrix based authorization strategy but allowing users to define what Jenkins permissions a user gets based on their access to a repository.  I don't really have off-hours time to commit at the moment to perform such an overhaul.

          Sam Gleske added a comment - I think the GitHub Committer Authorization Strategy needs a complete overhaul.  The way I'd like to see it done is akin to the matrix based authorization strategy but allowing users to define what Jenkins permissions a user gets based on their access to a repository.  I don't really have off-hours time to commit at the moment to perform such an overhaul.
          Sam Gleske made changes -
          Environment Original: Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.

          Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful.
          Sam Gleske made changes -
          Description New: Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.

          Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful.

           

          edit: migrated description from environment by [~sag47]

          Sam Gleske added a comment -

          Closing this issue in favor of JENKINS-27844 to completely overhaul the GitHub committer authorization strategy.  Subscribe and vote there so we can track it all in one place.

          Sam Gleske added a comment - Closing this issue in favor of  JENKINS-27844  to completely overhaul the GitHub committer authorization strategy.  Subscribe and vote there so we can track it all in one place.
          Sam Gleske made changes -
          Link New: This issue duplicates JENKINS-27844 [ JENKINS-27844 ]
          Sam Gleske made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            sag47 Sam Gleske
            aga Aleksi Aalto
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: