GSoC 2025 - Plugin Modernizer improvement - New repo for `metadata-plugin-modernizer`

[jonesbusy]

Hi,

This is related to https://www.jenkins.io/projects/gsoc/2025/projects/plugin-modernizer-improvements/

The goal of this second year of Plugin Modernizer is to collect data and have better visibility of modernization and migration of plugins.

The idea is to have a new repository that will contains JSON data (vs code on https://github.com/jenkins-infra/plugin-modernizer-tool).

When users run the CLI and a PR is open on the plugin repository, an other PR is open on this "metadata" repo. Some GH action validate those files and maintainers of plugin-modernizer-tool just merge PR.

Then this repo (an other GH action) will check the status or PR and update the data accordingly (also via PR). For example to identify PR that are failing, we collect the status.

Once done the final idea is to rely of the jenkins infra library to push consolidated data on https://reports.jenkins.io/

Perhaps a 3rd year GSoC would be to perform the UI and update of https://stats.jenkins.io to decide what is worth to display? But definitely not for this year :)

Permissions

• Same as https://github.com/jenkins-infra/plugin-modernizer-tool
• No secret needed

For the moment our mentee Raunak is doing his tests on is own repo: https://github.com/Raunak80Madan/metadata-plugin-modernizer

This is not an urgent issue, but I would be great to address it before the end of GSoC 2025.

If infra team is interested a demo will be performed on the Midterm status: https://www.meetup.com/jenkins-online-meetup/events/309057517/?eventOrigin=group_upcoming_events

FYI @CodexRaunak @gounthar @sridamul @TheMeinerLP

Thanks!

Valentin

[dduportal]

Hi @jonesbusy @gounthar , I've created https://github.com/jenkins-infra/metadata-plugin-modernizer and set it up.

You are both admins , along with the infra core team: I'll let you populate the content and/or invite collaborators based on your follows up on GSoc 2025 (and it will ensure that you have the right permissions :) ).

[jonesbusy]

Thanks! We will merge any open PR and then push the history to main.

And update the reference to target the new repo