-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-51991] - JCasC config Exporter fails on the latest version with Java 10, "No bean specified" #292
Comments
I encounter the same error when building from the official docker image
If I try to use the lts jenkins image, it fails to download the ConfigurationAsCode plugin. If you need anymore information, please tell me. Thanks :) |
@Eclar which version of CasC plugin are you running ? |
I am using 0.8-alpha. |
@Eclar this has been fixed already by #258 |
To reproduce this issue use...
|
this docker image uses 0.8-alpha constructor parameter name indeed doesn't match getter https://github.com/jenkinsci/ownership-plugin/blob/master/src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/OwnerNodeProperty.java |
@ndeloof ack. Will create ta ticket to Ownership plugin. |
I will test it, but I believe this issue can be resolved on the JCasC side. |
see #313 Not sure how we could handle this on JCasC side. I even can't find the config.jelly file to associate constructor parameter |
I agree. In this case it would be preferable to just fix the plugin. Will do that. |
Reposting https://issues.jenkins-ci.org/browse/JENKINS-51991 , I'd guess @ndeloof may want to take a look at it during the Java 10+ hackathon this week.
I cannot export configuration from oleg-nenashev/demo-jenkins-config-as-code#5 when running Jenkins on Java 10. OTOH the same configuration export works well when I run on Java 8.
Exporting Caused by: java.lang.IllegalArgumentException: No bean specified
The text was updated successfully, but these errors were encountered: