[JIRA] (JENKINS-59722) Old scm-api included in Jenkins war file

० भ्यु
नपढिएको पहिलो सन्देशमा जानुहोस्

ftclausen@gmail.com (JIRA)

नपढिएको,
२०१९ अक्टोबर २१, २३:००:०३१९/१०/२१
प्रापक jenkinsc...@googlegroups.com
Friedrich Clausen updated an issue
 
Jenkins / Bug JENKINS-59722
Old scm-api included in Jenkins war file
Change By: Friedrich Clausen
Summary: Old scm-api included in Jenkins LTS war file
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

dbeck@cloudbees.com (JIRA)

नपढिएको,
२०१९ अक्टोबर २२, ०३:५३:०३१९/१०/२२
प्रापक jenkinsc...@googlegroups.com
Daniel Beck commented on Bug JENKINS-59722
 
Re: Old scm-api included in Jenkins war file

if any plugin specified in "jenkinsPlugins" depends on a plugin bundled in the Jenkins core war file then it'll use that even if a newer one is specified in "jenkinsPlugins".

This looks like a bug in your script.

I don't believe our usage is unsupported

As a core maintainer for the past five years I feel confident in saying that we do not support this use case and unless Oleg or Jesse chime in, this is probably the most authoritative answer you'll get.

dbeck@cloudbees.com (JIRA)

नपढिएको,
२०१९ अक्टोबर २२, ०३:५४:०४१९/१०/२२
प्रापक jenkinsc...@googlegroups.com
Daniel Beck closed an issue as Not A Defect
 

Please do not reopen unless you have new evidence that this kind of use has explicitly been supported in the past.
Change By: Daniel Beck
Status: Reopened Closed
Resolution: Not A Defect

robinverduijn.github@gmail.com (JIRA)

नपढिएको,
२०१९ अक्टोबर २२, २१:२४:०३१९/१०/२२
प्रापक jenkinsc...@googlegroups.com
Robin Verduijn commented on Bug JENKINS-59722
 
Re: Old scm-api included in Jenkins war file

It worked as recently as Jenkins 2.176.3, and only broke with Jenkins 2.190.1. This is a common use case for people using https://github.com/heremaps/gradle-jenkins-jobdsl-plugin to define (and generate) their Jenkins jobs from DSL out of a Git repository.

robinverduijn.github@gmail.com (JIRA)

नपढिएको,
२०१९ नोभेम्बर २२, २०:२३:०३१९/११/२२
प्रापक jenkinsc...@googlegroups.com

With a newer Jenkins 2.190.2 dependency, another similar error pops up, possibly caused by a similar version mismatch:

 

  10.797 [id=1] SEVERE  h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (main/1) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.
groovy.lang.MissingMethodException: No signature of method: javaposse.jobdsl.plugin.structs.DescribableListContext.git() is applicable for argument types: (learnsaas.captain.script$_run_closure1$_closure2$_closure6$_closure7$_closure8) values: [learnsaas.captain.script$_run_closure1$_closure2$_closure6$_closure7$_closure8@4507f4b8]
Possible solutions: wait(), wait(long), is(java.lang.Object), with(groovy.lang.Closure), grep(), any()
        at jdk.internal.reflect.GeneratedConstructorAccessor46.newInstance(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
        at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:266)
        at javaposse.jobdsl.plugin.structs.DescribableListContext.methodMissing(DescribableListContext.groovy:65)
सबैलाई जवाफ पठाउनुहोस्
लेखकलाई जवाफ
फर्वार्ड गर्नुहोस्
0 नयाँ म्यासेजहरू