-
Bug
-
Resolution: Fixed
-
Critical
-
-
Jenkins 2.178
It is a placeholder for https://github.com/jenkinsci/docker/issues/698 and for https://github.com/jenkinsci/jenkins/pull/4000 which addresses it in the core
Using newer cores that have part of it moved to plugins and is now implied dependencies in other plugins is causing to have bad Jenkins installation.
- causes
-
JENKINS-58362 CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
-
- Resolved
-
- is related to
-
JENKINS-55582 Convert modules to plugins
-
- Resolved
-
- relates to
-
JENKINS-59552 Detached plugins installed are those with security warnings
-
- Closed
-
- links to
(2 links to)
I am not aware of which ancient versions or security warnings you are referring to here. All detached plugins are expected to be updated in tandem with security advisories. If you see differently, please file a bug report (or a patch). CC danielbeck
See discussion in JENKINS-28942. My standing proposal would require the plugin to be re-released, with metadata indicating the most recent core version against which it has been successfully tested, but would not require the minimum core version to be changed.