I don't believe our usage is unsupported; I'll include some details. We are using gradle-jenkins-jobdsl-plugin to generate Job XML from Job DSL files. To do this gradle-jenkins-jobdsl-plugin will start an actual Jenkins instance using the war file. It is possible to include extra plugins using the "jenkinsPlugin" Gradle dependency configuration (see "How does it work" in link above). What we have been seeing is that, 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". In the case of "Git" depending on "scm-api", it uses the bundled one that is too old. Even if we specify a newer scm-api in the "jenkinsPlugin" configuration. Reproducible Project I have created a small example project that illustrates this issue: https://github.com/ftclausen/JENKINS-59722 See README.md for how to trigger. |