Скачать или смотреть How to Solve the Jenkins Shell Script Hangs Issue When Running Sudo PM2 LS

Discover how to resolve the issue of Jenkins shell scripts hanging when using `sudo pm2 ls` by adjusting your remote command execution strategy.
---
This video is based on the question https://stackoverflow.com/q/64057339/ asked by the user 'reza' ( https://stackoverflow.com/u/496136/ ) and on the answer https://stackoverflow.com/a/64062273/ provided by the user 'Jens' ( https://stackoverflow.com/u/648658/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: why Jenkins shell script hangs when i run sudo pm2 ls

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Problem: Jenkins Shell Script Hangs

If you're a beginner to Jenkins and have encountered the frustrating problem where your shell script hangs when trying to run the command sudo pm2 ls, you are not alone. This is a common issue when executing commands on a remote server through Jenkins.

In this instance, you’ve correctly set up Jenkins on your Mac and established an SSH connection to a remote server for testing. However, the command sudo pm2 ls hangs indefinitely when triggered through your Jenkins script. This situation arises due to a misunderstanding of how Jenkins processes SSH commands. Let’s explore why this happens and how to fix it.

Why Does It Hang?

When you invoke ssh in your Jenkins script, the shell expects the SSH session to complete before it can move on to execute the next command—sudo pm2 ls. However, since the SSH session remains open (waiting for input), Jenkins perceives this as an ongoing process, leading to the so-called "hang." You don't experience this issue in the command line because you aren't requiring simultaneous command execution through a Jenkins pipeline.

Step-by-Step Solution

To resolve this hanging issue, there are a couple of methods you can use:

Method 1: Execute Commands Directly With SSH

If the number of commands you want to run is limited, you can combine them into a single SSH command. This method ensures everything runs in one go without waiting for one command to finish before starting the next.

Here's how to do that:

[[See Video to Reveal this Text or Code Snippet]]

By wrapping the command in single quotes, you ensure it's executed on the remote server directly, which prevents the hanging problem.

Method 2: Use a Remote Script

When dealing with multiple commands or a more complex setup, it’s better to create a script on the remote server that includes all the commands you need to execute. Once your script is ready, you can simply invoke it via SSH. Here’s how:

Create a Script on the Remote Server:
Save your commands in a script, for example:

[[See Video to Reveal this Text or Code Snippet]]

Make sure to give the script execution permissions:

[[See Video to Reveal this Text or Code Snippet]]

Execute the Script Through SSH:
You can run the entire script using:

[[See Video to Reveal this Text or Code Snippet]]

This method helps maintain clarity and organization in your automation setup.

Conclusion

Understanding the underlying issue of the hanging Jenkins shell script is crucial for effective troubleshooting and scripting. By either directly executing commands via SSH or creating a remote script, you can avoid the hanging problem and enhance your Jenkins automation workflow.

If you found this post helpful, consider sharing your own experiences with Jenkins or any additional tips you might have for resolving similar issues.