[HAP-660] ConversionException while loading saved Job configuration Created: 04/Nov/15  Updated: 06/Nov/15  Resolved: 05/Nov/15

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: Maven3
Affects Version/s: 2.4.0
Fix Version/s: 2.4.1

Type: Bug Priority: Critical
Reporter: Luca Menegus Assignee: Eyal Ben Moshe (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

Step to reproduce:

  • create a maven job
  • check "Resolve artifacts from Artifactory" box and configure instance and repositories
  • stop jenkins
  • start jenkins

"Resolve artifacts from Artifactory" is not checked anymore and instance and repositories configuration is lost.

  • go to administrativeMonitor/OldData/manage jenkins page and you will see the following message:

ConversionException: org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator cannot be cast to org.jfrog.hudson.DeployerOverrider : org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator cannot be cast to org.jfrog.hudson.DeployerOverrider ---- Debugging information ---- message : org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator cannot be cast to org.jfrog.hudson.DeployerOverrider cause-exception : java.lang.ClassCastException cause-message : org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator cannot be cast to org.jfrog.hudson.DeployerOverrider class : org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator required-type : org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator converter-type : hudson.util.XStream2$AssociatedConverterImpl path : /maven2-moduleset/buildWrappers/org.jfrog.hudson.maven3.ArtifactoryMaven3NativeConfigurator line number : 177 -------------------------------, InstantiationError: null



 Comments   
Comment by Luca Menegus [ 04/Nov/15 ]

Feel free to ask more information

Comment by Eyal Ben Moshe (Inactive) [ 04/Nov/15 ]

Thanks for reporting this. We are looking into this and will update soon.

Comment by Eyal Ben Moshe (Inactive) [ 05/Nov/15 ]

We will soon release 2.4.1 with this fix.

Comment by Luca Menegus [ 05/Nov/15 ]

Perfect! In case you have SNAPSHOT build available for testing tomorrow I could try it on our environment.

Comment by Eyal Ben Moshe (Inactive) [ 05/Nov/15 ]

Thanks. We would appreciate your feedback. Here's a download link to our release candidate:
http://repo.jfrog.org/artifactory/libs-snapshots-local/org/jenkins-ci/plugins/artifactory/2.4.1-SNAPSHOT/artifactory-2.4.1-20151105.191155-3.hpi

Comment by Luca Menegus [ 06/Nov/15 ]

Ok I tested the snapshot version and it doesn't crash anymore . But my test revealed another problem: after restart the value specified for the "Resolution releases repository" seems to applied to "Resolution snapshots repository" as well. To reproduce it you can create a maven project enable "Resolve artifacts from Artifactory" and configure two different repositories, save the job. You can check the job's config.xml and see that the selected values are correctly serialized to xml. Now restart jenkins. and you will find that the values for the release and snapshot repositories are the same (config.xml still show the correct values). Shell I open another issue?

Comment by Eyal Ben Moshe (Inactive) [ 06/Nov/15 ]

We also noticed that and thanks again Luca for the great feedback!
No need for another issue. The release will include this as well.

Comment by Eyal Ben Moshe (Inactive) [ 06/Nov/15 ]

Version 2.4.1 has been released and should be soon available on the Jenkins Update Center.

Generated at Sun Oct 20 12:35:03 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.