Issue:
With DevTest Jekins plugin, we are able to deploy LISA Tests & Virtual service functionalities, and they are working but it impacts the below plugins :
1) Sauce onDemand Plugin
2) Slack Notifier Plugin
Seeing the below errors :
hudson.model.FreeStyleProject@2ea8cc48[CST_folder/PEER1069Validation/LISATest]`
- ConversionException: com.ca.devtest.jenkins.plugin.buildstep.DefaultBuildStep : com.ca.devtest.jenkins.plugin.buildstep.DefaultBuildStep
---- Debugging information ----
message : com.ca.devtest.jenkins.plugin.buildstep.DefaultBuildStep
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message : com.ca.devtest.jenkins.plugin.buildstep.DefaultBuildStep
class : java.util.TreeMap
required-type : java.util.TreeMap
converter-type : com.thoughtworks.xstream.converters.collections.TreeMapConverter
path : /project/properties/com.cloudbees.hudson.plugins.modeling.impl.jobTemplate.JobPropertyImpl/instance/values/entry/com.ca.devtest.jenkins.plugin.buildstep.DefaultBuildStep-array
line number : 13
-------------------------------, MissingFieldException: No field 'entry' found in class 'com.cloudbees.hudson.plugins.modeling.impl.jobTemplate.JobPropertyImpl', MissingFieldException: No field 'entry' found in class 'com.cloudbees.hudson.plugins.modeling.impl.jobTemplate.JobPropertyImpl', MissingFieldException: No field 'entry' found in class 'com.cloudbees.hudson.plugins.modeling.impl.jobTemplate.JobPropertyImpl', MissingFieldException: No field 'entry' found in class 'com.cloudbees.hudson.plugins.modeling.impl.jobTemplate.JobPropertyImpl', MissingFieldException: No field 'entry' found in class 'com.cloudbees.hudson.plugins.modeling.impl.jobTemplate.JobPropertyImpl'
Environment:
CA Service virtualization Jenkins plugin version is : 1.0.2.3
Sauce On-Demand plugin version is 1.177
Salck Notification plugin version is 2.0.1
Cause:
Created job in Jenkins using the Custom cloud-bee template; it somehow creates job from template but fails for our build steps. Maybe because we use abstract class "DefaultBuildStep" for all plugin build steps and cloud bee is expecting something else.
Resolution:
We use abstract class "DefaultBuildStep" for all plugin build steps. When using Custom templates to create jobs, Cloud bee might be expecting a different class name. Please work with your cloud-bee team on resolving the class name.
Workaround:
Use the Free Style template in cloud bee instead of the Custom Template.
You would see the message after the job is completed:
main build action completed: SUCCESS