Closed dpollastrini closed 5 years ago
I think this should be incompatible with some plugins, I am using the official jenkins 2.176.2 and there is no problem.
@runzexia Thanks for the response. It is not clear what you mean by "I think this [emphasis added] should be incompatible with some plugins...". Does "this" mean using a Docker container via k8s, the specific Docker image referenced, or ??
Regarding the Docker image, my understanding is that https://hub.docker.com/r/h1kkan/jenkins-docker is actually derived from the official image https://hub.docker.com/r/jenkins/jenkins (the former merely adds some plugins). In any case, the LTS tags for both images use 2.176.X. I also verified the Jenkins version in my Jenkins installation: org.jenkins-ci.main:jenkins-war:2.176.3.
Presuming that you are referring to the Docker image I am using as being incompatible, I rebuilt my installation using the "official" LTS image (https://hub.docker.com/r/jenkins/jenkins). With a clean install of the latest Jenkins image running as a K8s Deployment, I'm seeing the same error referenced in the origin report.
Thanks again for your time.
Sorry, I think my previous answer is not very accurate. I also reproduced this problem. I will try to fix it today.
@runzexia You, sir, are a golden god. Thanks!
I'm running Jenkins (2.176.2) as a docker image (https://hub.docker.com/r/h1kkan/jenkins-docker, LTS). I've install the latest kubernetes-cd-plugin (2.1.0). My test pipeline script is configured as follows (redacted):
The plugin configuration validates successfully. However, the output is as follows:
Its seems the plugin is not actually emitting a catch-able error as the "ERROR!" message does not appear. Regardless the stack trace appears at the bottom of the console output.
I've verified the documented dependencies are present in the Jenkins plugin manager, but it would seem I'm missing something.
Thanks in advance for your help.