Closed ewelinawilkosz closed 6 years ago
The second looks like lack of jdk-tool
plugin implied dependency? https://plugins.jenkins.io/jdk-tool https://jenkins.io/changelog/#v2.112
SSHLauncher has implied deps on jdk-tool
and command-launcher
so you have to install those 😢
Covered previously here: https://github.com/jenkinsci/configuration-as-code-plugin/issues/294#issuecomment-39950098
thanks @casz and @daniel-beck am I right assuming we need https://github.com/jenkinsci/docker/issues/698 to get rid of those issues in the future? In such case I'll close that ticket
@ewelinawilkosz there is a wish from @ndeloof to actually suggest Jenkins core getting a plugin manager API/CLI to handle this and also understand the implied deps instead of writing bash. https://github.com/jenkinsci/docker/issues/698#issuecomment-399990101 https://github.com/jenkinsci/docker/pull/668#issuecomment-405938741
ok, we need an update in the documentation at least for now or maybe @oleg-nenashev the compatibility issues page you mentioned is the right place? what do you think?
Well, I do not see how it could be mentioned properly. It is not a JCasC-specific issue. If you use plugins.txt
, it is a pretty well known defect in its behavior.
ok! thanks for explanation
Sorry, long logs!
mvn hpi:run -Djenkins.version=2.121.1
fails with:I was on on off on vacation and maybe I missed some vital information I can't seem to find now?