Jenkins executes the shell command, sometimes prompting "command not found"

The problem is that environment variables are not accurately

(1) Check that the maven you set in Jenkins is accurate, and you can see if there is a MAVEN option in the new job with the "New Job" button, not exactly what you configured

If you download the plugin, also refer to the previous steps to see if the plugin works.

(2) Check that all the scripts executed in Jenkins are configured with the correct MAVEN path, because if a MAVEN path was previously configured and the environment variable is the one you installed, then only the environment variable that was first set in the script will be

Environment Variables Cat/etc/profile View and add

(3) Check whether the MAVEN environment on the server where Jenkins is installed is installed, or if the MAVEN environment is installed on the server where Jenkins compiles (primarily for Jenkins to call MAVEN commands for packaging)

(4) The situation is basically so much "no picture"

Jenkins executes the shell command, sometimes prompting "command not found"