Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-658

Use Repository Permission Updater as a source of the maintainer info

    Details

    • Type: Improvement
    • Status: To Do (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: plugin-site
    • Labels:
      None
    • Similar Issues:

      Description

      Currently Maintainers info is being extracted from pom.xml, and it is not maintained well in many plugins. It would be great to source the data from https://github.com/jenkins-infra/repository-permissions-updater instead.

      Implementation idea:

      • Plugin site API checks out https://github.com/jenkins-infra/repository-permissions-updater on startup and then refreshes it periodically, e.g. every 24 hours
      • Any user with upload permission is considered as maintainer. The list might be merged with pom.xml metadata
      • There is an in-memory cache for maintainers so that we do not read the maintainer list every time

      Later we can use the same engine to pull more information from https://github.com/jenkins-infra/repository-permissions-updater

        Attachments

          Activity

          oleg_nenashev Oleg Nenashev created issue -
          oleg_nenashev Oleg Nenashev made changes -
          Field Original Value New Value
          Epic Link WEBSITE-637 [ 201403 ]
          Hide
          oleg_nenashev Oleg Nenashev added a comment -
          Show
          oleg_nenashev Oleg Nenashev added a comment - CC Daniel Beck
          oleg_nenashev Oleg Nenashev made changes -
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          Hide
          danielbeck Daniel Beck added a comment -

          Yup, great idea and long overdue!

          Show
          danielbeck Daniel Beck added a comment - Yup, great idea and long overdue!
          Hide
          danielbeck Daniel Beck added a comment -

          I wonder whether it wouldn't make sense to:

          • Implement this in update-center2 (which is where the current data is exposed)
          • Use RPU/LDAP as data source, as these are who we generally consider to be maintainers – you're not a maintainer if you cannot release.

           

          Show
          danielbeck Daniel Beck added a comment - I wonder whether it wouldn't make sense to: Implement this in update-center2 (which is where the current data is exposed) Use RPU/LDAP as data source, as these are who we generally consider to be maintainers – you're not a maintainer if you cannot release.  
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          LDAP is one f the ways. Another way is to generate a maintainers report on the Jenkins infrastructure and include it when generating the update center

          Show
          oleg_nenashev Oleg Nenashev added a comment - LDAP is one f the ways. Another way is to generate a maintainers report on the Jenkins infrastructure and include it when generating the update center

            People

            • Assignee:
              Unassigned
              Reporter:
              oleg_nenashev Oleg Nenashev
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: