|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Actually this seems like a pure gradle plugin issue.
The class 'hudson.plugins.gradle.Gradle' defines a DataBoundConstuctor AND its descriptor also defines a newInstance() method.
Although this seems to work for the plugin itself, I think this against the contract/convention.
The condiontional-buildstep plugin only allows to add build steps which provide a DataBoundConstructor, because in the creation via the newInstance() method does not work in this usecase. I'm afraid, but the Gradle plugin should make the decision whether to provide the DataBoundConstructor or the newInstance() method - but NOT both.