Jenkins remote deployment jar unresponsive problem

Reason: Jenkins will kill all processes about jenkins after it is built by default. So the jar must have been killed before execution. You can see the nohup.out log. You will find that only part of your project startup log is printed but not completely printed, indicating that the startup process was interrupted.

Solution: I have referenced a lot on the Internet, to tell the truth, most of them are copied posts, which are not used. Refer directly to this post: https://blog.csdn.net/draven1122/article/details/84971885

I solved it through the second solution in the above post.

Guess you like

Origin blog.csdn.net/zhaojunjie_cc/article/details/100031266