[JIRA] (JENKINS-49643) java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79

499 views
Skip to first unread message

santhukundur@gmail.com (JIRA)

unread,
Feb 20, 2018, 5:22:02 AM2/20/18
to jenkinsc...@googlegroups.com
santhosh s created an issue
 
Jenkins / Bug JENKINS-49643
java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79
Issue Type: Bug Bug
Assignee: Unassigned
Components: pipeline
Created: 2018-02-20 10:21
Environment: Dev
Priority: Major Major
Reporter: santhosh s

Code :

 

pipeline {
agent
stages{
stage('Checkout'){
//steps {
echo "Hellow world"
//sh 'ls'
}
// }
}

post {
always {
step([$class: 'Mailer',
notifyEveryUnstableBuild: true,
recipients: "santhu...@gmail.com" ,
sendToIndividuals: true])
}
}
}

 

Getting the Below error while running the Pipeline code:

 
java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement(Lorg/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage;Z)Z
at org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStage.validate(ModelASTStage.java:78)
at org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStages.validate(ModelASTStages.java:41)
at org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStages.validate(ModelASTStages.java:35)
at org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTPipelineDef.validate(ModelASTPipelineDef.java:64)
at org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTPipelineDef$validate.call(Unknown Source)
at org.jenkinsci.plugins.pipeline.modeldefinition.parser.ModelParser.parse(ModelParser.groovy:204)
at org.jenkinsci.plugins.pipeline.modeldefinition.parser.ModelParser$parse.callCurrent(Unknown Source)
at org.jenkinsci.plugins.pipeline.modeldefinition.parser.ModelParser.parse(ModelParser.groovy:91)
at org.jenkinsci.plugins.pipeline.modeldefinition.parser.GroovyShellDecoratorImpl$1.call(GroovyShellDecoratorImpl.java:46)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:129)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:123)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:517)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:480)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:269)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:419)
Finished: FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 20, 2018, 6:10:03 AM2/20/18
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Bug JENKINS-49643
 
Re: java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79

Likely a binary compatibility issue between plugin versions.
Maybe updating to the latest versions of Pipeline plugins will resolve that.

CC Andrew Bayer Sam Van Oort

andrew.bayer@gmail.com (JIRA)

unread,
Feb 20, 2018, 7:01:03 AM2/20/18
to jenkinsc...@googlegroups.com
Andrew Bayer assigned an issue to Andrew Bayer
 
Change By: Andrew Bayer
Assignee: Andrew Bayer

andrew.bayer@gmail.com (JIRA)

unread,
Feb 20, 2018, 3:36:03 PM2/20/18
to jenkinsc...@googlegroups.com
Andrew Bayer updated an issue
Change By: Andrew Bayer
Component/s: pipeline-model-definition-plugin
Component/s: pipeline

andrew.bayer@gmail.com (JIRA)

unread,
Feb 20, 2018, 3:38:02 PM2/20/18
to jenkinsc...@googlegroups.com
Andrew Bayer commented on Bug JENKINS-49643
 
Re: java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79

Yeah, smells like a plugin version mismatch between pipeline-model-api and pipeline-model-definition - make sure to update to the latest versions and you should be fine.

santhukundur@gmail.com (JIRA)

unread,
Feb 21, 2018, 12:58:02 AM2/21/18
to jenkinsc...@googlegroups.com

Thanks Andrew for the update..

 

Is there any resolution without updating the plugins?

Regards,

Santhosh

andrew.bayer@gmail.com (JIRA)

unread,
Feb 21, 2018, 11:49:02 AM2/21/18
to jenkinsc...@googlegroups.com

What? No, if you've got a version mismatch between pipeline-model-api and pipeline-model-definition, you have to get them in sync.

andrew.bayer@gmail.com (JIRA)

unread,
Mar 8, 2018, 6:15:02 PM3/8/18
to jenkinsc...@googlegroups.com
Andrew Bayer resolved as Not A Defect
 
Change By: Andrew Bayer
Status: Open Resolved
Resolution: Not A Defect

bitwiseman@gmail.com (JIRA)

unread,
Oct 22, 2019, 11:25:06 PM10/22/19
to jenkinsc...@googlegroups.com
Liam Newman closed an issue as Not A Defect
 

Bulk closing resolved issues.

Change By: Liam Newman
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

alvizu@gmail.com (JIRA)

unread,
Nov 13, 2019, 11:03:02 PM11/13/19
to jenkinsc...@googlegroups.com
Dan Alvizu commented on Bug JENKINS-49643
 
Re: java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79

Today we had an issue where we rebuilt our Jenkins image using the https://github.com/jenkinsci/docker/blob/master/install-plugins.sh script. We had declared pipeline-model-definition to be version 1.3.9 – pipeline-model-api was also 1.3.9, but transitive (not in plugins.txt we provied to the script). When we rebuilt the image today this pulled in pipeline-model-api 1.4.0 which caused us to see the error above.

Our work-around here is to pin all versions of the plugin, which is probably a good idea in general. However, I wonder why this is a separate plugin.

>  if you've got a version mismatch between pipeline-model-api and pipeline-model-definition, you have to get them in sync.

Forgive me if this is a naive question – if these are required to be the same version or else they will never work, is there any value in having these as separate plugins?

alvizu@gmail.com (JIRA)

unread,
Nov 13, 2019, 11:04:03 PM11/13/19
to jenkinsc...@googlegroups.com
Dan Alvizu edited a comment on Bug JENKINS-49643
Today we had an issue where we rebuilt our Jenkins image . This image also installs plugins, which we do to speed up startup time of Jenkins. We do this using the [https://github.com/jenkinsci/docker/blob/master/install-plugins.sh] script in the image build . We had declared pipeline-model-definition to be version 1.3.9 – pipeline-model-api was also 1.3.9, but transitive (not in plugins.txt we provied to the script). When we rebuilt the image today this pulled in pipeline-model-api 1.4.0 which caused us to see the error above.

Our work-around here is to pin all versions of the plugin, which is probably a good idea in general. However, I wonder why this is a separate plugin . ?

>  if you've got a version mismatch between {{pipeline-model-api}} and {{pipeline-model-definition}}, you have to get them in sync.


Forgive me if this is a naive question – if these are required to be the same version or else they will never work, is there any value in having these as separate plugins?
Reply all
Reply to author
Forward
0 new messages