Based on my previous cleanup of jira components, this actually wasn't that hard
https://gist.github.com/7f30c8385f28c40f99f66967ab74b42b Def not my best work but i'm happy with it for limited computer time. Its safe to run multiple times, so once everything is agreed upon, can update the hosting bot and run this again. All the populated data - https://github.com/jenkins-infra/repository-permissions-updater/pull/1793 Only a handful of plugins couldn't be matched up, so we'll need to create jira components (or prevent distribution). [MISSING] aio-tests is missing issues [MISSING] ApicaLoadtest is missing issues [MISSING] appetize is missing issues [MISSING] appscan is missing issues [MISSING] bigpanda-jenkins is missing issues [MISSING] bitbucket-scm-filter-aged-refs is missing issues [MISSING] bitbucket-scm-trait-commit-skip is missing issues [MISSING] blueocean-i18n is missing issues [MISSING] build-history-metrics-plugin is missing issues [MISSING] build-steps-from-json is missing issues [MISSING] bumblebee is missing issues [MISSING] ca-apm-parent is missing issues [MISSING] carl is missing issues [MISSING] codecommit-url-helper is missing issues [MISSING] codedx is missing issues [MISSING] compress-buildlog is missing issues [MISSING] cucumber-trends-report is missing issues [MISSING] custom-tools-plugin is missing issues [MISSING] diskcheck is missing issues [MISSING] environment-labels-setter is missing issues [MISSING] environment-manager is missing issues [MISSING] externalresource-dispatcher is missing issues [MISSING] failedJobDeactivator is missing issues [MISSING] github-scm-filter-jira-validator is missing issues [MISSING] google-deployment-manager is missing issues [MISSING] housekeeper is missing issues [MISSING] http-post is missing issues [MISSING] http_request is missing issues [MISSING] ibm-application-security is missing issues [MISSING] impersonation is missing issues [MISSING] itms-for-jira is missing issues [MISSING] jclouds-jenkins is missing issues [MISSING] jenkinsci-appspider-plugin is missing issues [MISSING] jenkins-infra-test is missing issues [MISSING] jenkins-jira-issue-updater is missing issues [MISSING] jobdelete-builder is missing issues [MISSING] jquery-detached is missing issues [MISSING] kanboard is missing issues [MISSING] keep-slave-disconnected is missing issues [MISSING] kubernetes-pipeline-devops-steps is missing issues [MISSING] lsf-cloud is missing issues [MISSING] mber is missing issues [MISSING] multi-branch-project-plugin is missing issues [MISSING] NegotiateSSO is missing issues [MISSING] paaslane-estimate is missing issues [MISSING] packagecloud is missing issues [MISSING] perforce is missing issues [MISSING] performance-signature-viewer is missing issues [MISSING] piketec-tpt is missing issues [MISSING] pipeline-classpath is missing issues [MISSING] pipeline-editor is missing issues [MISSING] pipeline-model-extensions is missing issues [MISSING] portshift-scanner is missing issues [MISSING] publish-over is missing issues [MISSING] qftest is missing issues [MISSING] rpi-build-status is missing issues [MISSING] sasunit-plugin is missing issues [MISSING] secondary-timestamper-plugin is missing issues [MISSING] send-stacktrace-to-eclipse-plugin is missing issues [MISSING] setenv is missing issues [MISSING] short-workspace-path is missing issues [MISSING] sidebar-update-notification is missing issues [MISSING] snakeyaml-api is missing issues [MISSING] spoonscript is missing issues [MISSING] srcclr-installer is missing issues [MISSING] TestComplete is missing issues [MISSING] testcomplete-xunit is missing issues [MISSING] testflo-for-jira-test-management-automation is missing issues [MISSING] teststudiomobiletesting is missing issues [MISSING] throttle-concurrents is missing issues [MISSING] tinfoil-scan is missing issues [MISSING] tusarnotifier is missing issues [MISSING] ui-test-capture is missing issues [MISSING] uno-choice is missing issues [MISSING] windows-cloud is missing issues [MISSING] workplace-notifier is missing issues [MISSING] zapper is missing issues On Sun, Dec 20, 2020 at 10:26 PM Gavin Mogan <[email protected]> wrote: > I love the idea but I'll put changing the directory structure to those in > charge of infra it doesn't break anything > > However adding new fields won't break things so I'm dusting off some > groovy skills to make a POC > > On Sat., Dec. 19, 2020, 3:52 p.m. Tim Van Holder, <[email protected]> > wrote: > >> If tweaking and renaming RPU, maybe also tweak the directory structure? >> >> For example, changing >> permissions/plugin-groovy-events-listener-plugin-master.yml to >> permissions/plugin/g/groovy-events-listener-plugin-master.yml >> >> This would make it a lot easier to browse on GH, which now truncates to >> 1000 items. >> >> >> On Fri, 18 Dec 2020 at 23:28, slide <[email protected]> wrote: >> >>> I think adding this information to the permissions files would be really >>> nice. I'd need to update the bot for the hosting process, so just let me >>> know what the syntax will be and I can get it place. >>> >>> On Thursday, December 17, 2020 at 3:20:47 PM UTC-7 Daniel Beck wrote: >>> >>>> >>>> >>>> > On 17. Dec 2020, at 23:01, 'Gavin Mogan' via Jenkins Developers < >>>> [email protected]> wrote: >>>> > >>>> > If a repo has github issues enabled, assume it uses that. >>>> > else If the plugin name has a jira component, assume it uses that. >>>> > else no issues link >>>> >>>> The beauty of the one time mass definition of issue trackers is that it >>>> can be arbitrarily sophisticated (read: convoluted and manual), since we >>>> don't need to re-run it once every 4 minutes on trusted.ci. >>>> >>>> Component name in Jira doesn't *exactly* match the plugin ID? No >>>> problem if I can match them up in a giant table. GH issues is enabled but >>>> has 0 total issues ever reported? Probably not relevant (and could even be >>>> disabled). Same with Jira components that could be deleted if 0 issues >>>> exist. But not both though. Plus we can purge Jira components without a >>>> corresponding published plugin (I already know these exist, it's great…). >>>> >>>> My desire to get this right, and a lack of spare time over the last 1-2 >>>> months has delayed this however :-/ Perhaps over the upcoming vacation. >>>> >>>> If others are willing to help with this, I can set something up for us >>>> to collaborate. >>>> >>>> > or to daniel's point (might be on the github draft PR), do we want to >>>> make it a hash style to support plugins that do both? Its not likely that a >>>> plugin will want two, but during a transitory period, it might be worth >>>> listing both >>>> >>>> FTR I wrote about that in >>>> https://github.com/jenkins-infra/plugin-site-api/pull/97#discussion_r544167455 >>>> and >>>> https://github.com/jenkins-infra/plugin-site-api/pull/97#issuecomment-747316256 >>>> -- some plugins do this deliberately. We also need to distinguish issue >>>> tracker references for reporting new issues (one tracker is likely >>>> preferred / enough to reference) and issue tracker references for existing >>>> issues (probably everything with open issues should be included, or even >>>> closed issues, depending on how it's used). >>>> >>>> While the vast majority of plugins will have a single tracker and >>>> that's it, GH issues seems to become more popular as well, and since that >>>> genie's out of the bottle by now, we should have proper support for folks >>>> wanting to switch over. >>>> >>>> > As a side note, it would be super easy to use that data to also fix >>>> SCM, so that things like the blueocean sub modules would have the right scm >>>> links since its already part of the metadata - >>>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-antisamy-markup-formatter.yml#L3 >>>> >>>> That's a great point. Correct; right now, update-center2 does not use >>>> RPU metadata at all, but would need it anyway once we define the issue >>>> tracker location there, so this should be a straightforward change on top. >>>> >>>> (Once we do this it's probably time to rename RPU to >>>> 'component-metadata' or similar, and move the permissions script out of it. >>>> IIUC we already have incrementals relying on it as well, that's what the >>>> 'github' field is for. What blocked this so far is the terrible file format >>>> that badly needs an overhaul as well to also better support the idea of a >>>> "plugin" semantically. So much to do, so little time :-( ) >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/048d3dab-7389-48d5-957e-7945dbb4a7c4n%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/048d3dab-7389-48d5-957e-7945dbb4a7c4n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAKMi--C1Q4SHgWLC2OrUv6FzSAMS4Zd4CvS7aSw2UOdqBChgHQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKMi--C1Q4SHgWLC2OrUv6FzSAMS4Zd4CvS7aSw2UOdqBChgHQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusLMbW6fk2MUdZ0BYRRAZoUmz-SoCAH8%3Do8mHRaK10hHw%40mail.gmail.com.
