-
Bug
-
Resolution: Unresolved
-
Major
-
None
Some exotic build steps (cloudbees templates ones, that are dynamically generated) aren't created using @DataBoundConstructor databinding, but by a custom newInstance implementation in constructor.
DefaultBuilderDescriptorLister is checking the buildStep for a @DataBoundConstructor, for some unknown reason (I've searched the git history, but this whole code was added as a single commit), but shouldn't imho
- depends on
-
JENKINS-18629 Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).
-
- Closed
-
- is blocking
-
JENKINS-16259 xUnit publisher not showing into conditional build steps
-
- Resolved
-
- is related to
-
JENKINS-6797 Add @DataBoundConstructor
-
- Resolved
-
- links to
Code changed in jenkins
User: Nicolas De Loof
Path:
src/main/java/org/jenkinsci/plugins/conditionalbuildstep/lister/DefaultBuilderDescriptorLister.java
http://jenkins-ci.org/commit/conditional-buildstep-plugin/fcfc219e627afaa8b19395674a756fe4dda43e7d
Log:
[FIXED JENKINS-15445] use Functions#getBuilderDescriptors to select the matching descriptors
don't check for @DataBoundConstructor. Descriptor may not use it to create instances