Re: How to trace the debug breakpoints when job running any slave?

Hi Pierre, You tips work for me. Change suspend to y to start the agent, it will hold the listening at 8765 as I set, then start the remote java application with my remote host name and 8765 port, then the agent started. Backup to eclipse, create some breakpoints which the sources codes will r

Re: How to trace the debug breakpoints when job running any slave?

Hello Boyka You're currently not attaching a debugger to the agent VM. Currently you have one debugger attached to the master JVM, but none to the agent JVM. I'm not familiar with Eclipse itself but basically you want to create a Remote configuration that will attach to the agent VM (on port 8765

Re: How to trace the debug breakpoints when job running any slave?

Hi Ullrich, In the remote host, I use below command to start the agent. java -jar -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8765 agent.jar -jnlpUrl http://myjenkinshost:8080/jenkins/computer/hostname123.dev.com/slave-agent.jnlp -workDir "/home/boyka/JenkinsDev" >From my

Re: How to trace the debug breakpoints when job running any slave?

How do you connect the remote debugger with the agent? > Am 15.07.2019 um 07:00 schrieb Boyka Zhu : > > Hi Martin, > > Thanks. Still, no works for me. What I did below: > > 1. Use Eclipse to start the Jenkins debug instance. Keep it running. > 2. Add the remote slave. > 3. Use command to start

Re: How to trace the debug breakpoints when job running any slave?

Hi Martin, Thanks. Still, no works for me. What I did below: 1. Use Eclipse to start the Jenkins debug instance. Keep it running. 2. Add the remote slave. 3. Use command to start the agent on the remote slave. [root@hostname123 boyka]# java -jar -agentlib:jdwp=transport=dt_socket,server=y,suspe

Re: How to trace the debug breakpoints when job running any slave?

Am Montag, 8. Juli 2019, 07:27:43 CEST schrieb Boyka Zhu: > Thanks for the updates. > I tried below to launch the jar. > [root@hostname123 tmp]# java -jar > -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8765 > TESTPLUGIN.jar Just run agent.jar, not your plugin jar. You don't need T

Re: How to trace the debug breakpoints when job running any slave?

Thanks. 在 2019年7月6日星期六 UTC+8下午9:51:58，Ullrich Hafner写道： > > You can have a look at my docker based development environment for my > warnings plugin: > https://github.com/uhafner/warnings-ng-plugin-devenv > > It starts the master and agent with open debugger ports so you can debug > master and a

Re: How to trace the debug breakpoints when job running any slave?

Thanks for the updates. I tried below to launch the jar. [root@hostname123 tmp]# java -jar -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8765 TESTPLUGIN.jar Listening for transport dt_socket at address: 8765 no main manifest attribute, in TESTPLUGIN.jar [root@hostname123 tmp]# Is

Re: How to trace the debug breakpoints when job running any slave?

You can have a look at my docker based development environment for my warnings plugin: https://github.com/uhafner/warnings-ng-plugin-devenv It starts the master and agent with open debugger ports so you can debug master and agent code. (The

Re: How to trace the debug breakpoints when job running any slave?

Am Samstag, 6. Juli 2019, 03:28:53 CEST schrieb Boyka Zhu: > Hi, > > My plugin will run on remote slave, the java source codes which running on > master can be traced, but the codes which runs on slave cannot be traced, > all breakpoints will be skipped. You need remote debugging. Start the Jav

How to trace the debug breakpoints when job running any slave?

Hi, My plugin will run on remote slave, the java source codes which running on master can be traced, but the codes which runs on slave cannot be traced, all breakpoints will be skipped. If I setup the job running locally on master node, then all break points can be traced. How to handle this?