I was able to duplicate the problem you describe based on the plugins list you provided, though I made the following modifications to the list of installed plugins:
- Removed console-log-to-workspace:1.2-SNAPSHOT plugin because it is not available to me
- Replaced dashboard-view:2.14 with dashboard-view:2.15 because it is a newer release
- Replaced gerrit-trigger:2.32.1 with gerrit-trigger:2.33.0 because it is required to satisfy dependencies
- Added jaxb:220.127.116.11 because it was not listed in the original plugins.txt but appeared as a plugin to be updated during my tests
- Replaced slack:2.45 with slack:2.46 because it is a newer release
- Replaced uno-choice:2.5.4 with uno-choice:2.5.5 because it is a newer release
With that plugin configuration, I was able to duplicate the problem.
I was able to resolve the problem by uninstalling the perforce plugin. The perforce plugin has been replaced by the p4 plugin. The perforce plugin is no longer listed on the plugins.jenkins.io site.
- Uninstall the perforce plugin. Use the p4 plugin instead (it is already installed in your environment)
- Create a custom fork of the perforce plugin that adapts to tables to divs. Since the perforce plugin was last released 5 years ago and depends on a very old version, that may be non-trivial
- Remain with Jenkins 2.263.x
The specific security issues with the perforce plugin are:
- SECURITY-536 - Perforce Plugin credentials can be obtained by users with Job/Extended Read permission
- SECURITY-373 - Perforce Plugin uses ineffective credentials encryption