Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Installing from docker image jenkins/jenkins:2.128 throws java.lang.IllegalArgumentException: No hudson.slaves.ComputerLauncher implementation found for SSHLauncher
See original GitHub issueReproduction repo at https://gitlab.com/jcrben-repro/jenkins-jcasc-docker
~~As of now, I believe this is loading 2.128 per https://hub.docker.com/r/jenkins/jenkins/tags/~~ locked down to 2.128
The repro case is a stripped down version of a more complex repo that I have internally at work, with agents and jobs and such.
I pulled down this repo and ran it from source locally on my mac (mvn hpi:run, etc) and it seemed to work, so possibly something to do with docker?
Noticed a tip for debugging jenkins docker https://github.com/jenkinsci/docker/commit/ec20d5ef79df648973d0a1e7c204da67c1813bae and will perhaps try that next.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
implied doesn’t mean it is necessarily installed. I had that issue with command-launcher hence why I mention it. 👍
I specifically had to install
in our plugins.txt
it’s not that weird, these two plugins I mentioned, used to inside the Jenkins core. Now they are plugins so hence they are implied after a certain Jenkins core.