Problem with this page
https://plugins.jenkins.io/ui/search/
Expected behavior
Source Code Management should display its label options, at least:
Source Code Management
Source Code Management related
Those correspond to scm and scm-related in the current source.
Actual behavior
The category renders as an empty list on the live site.
I also verified that the live HTML currently contains an empty list for that category:
<li class="scm">
<label>...<span>Source Code Management</span></label>
<ul></ul>
</li>
Possible solution
This looks less like a frontend rendering issue and more like a data mismatch in the plugin-site build/deployment pipeline.
The live site renders the Source Code Management category, but does not render any matching child labels for it. Since the category definition in categories.json includes scm and scm-related, one possible cause is that the deployed JenkinsPluginLabel data is missing those label entries, or was generated from stale/inconsistent upstream data at build time.
I am intentionally not assuming this is a bug in Jenkins core itself, since Messages.properties is only used as a source of display names for label IDs.
Problem with this page
https://plugins.jenkins.io/ui/search/
Expected behavior
Source Code Managementshould display its label options, at least:Source Code ManagementSource Code Management relatedThose correspond to
scmandscm-relatedin the current source.Actual behavior
The category renders as an empty list on the live site.
I also verified that the live HTML currently contains an empty list for that category:
Possible solution
This looks less like a frontend rendering issue and more like a data mismatch in the
plugin-sitebuild/deployment pipeline.The live site renders the
Source Code Managementcategory, but does not render any matching child labels for it. Since the category definition incategories.jsonincludesscmandscm-related, one possible cause is that the deployedJenkinsPluginLabeldata is missing those label entries, or was generated from stale/inconsistent upstream data at build time.I am intentionally not assuming this is a bug in Jenkins core itself, since
Messages.propertiesis only used as a source of display names for label IDs.