-
Bug
-
Resolution: Fixed
-
Critical
https://github.com/jenkinsci/jenkins/commit/4de46465153dae1a9e804c0d526c44d528f00fb4 restored support for "kind" as a way to resolve descriptor matching a configured entity.
Side effect is : a descriptor which uses a custom string as ID (as recommended by hudson.model.Descriptor#getId) won't be resolved as hudson.model.Descriptor#find who will compare ID with $class, not kind=ID.
- depends on
-
JENKINS-28110 1.610 “Failed to instantiate” error
-
- Resolved
-
-
JENKINS-28093 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html
-
- Resolved
-
-
JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
-
- Closed
-
- is related to
-
JENKINS-27918 Unhelpful log warning about stapler-class
-
- Resolved
-
- links to
[JENKINS-26781] regression resolving Descriptor using "$class" vs "kind"
Component/s | New: core [ 15593 ] | |
Component/s | Original: cobertura-plugin [ 15500 ] | |
Assignee | Original: Stephen Connolly [ stephenconnolly ] | New: Nicolas De Loof [ ndeloof ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | New: api stapler |
Labels | Original: api stapler | New: api regression stapler |
This actually is an issue with Cloudbees-template plugin, which uses a distinct descriptor.id != descriptor.clazz. Issue will be fixed in cloudbees plugin.