Caused: java.io.IOException: Cannot run program ““ (in directory “/var/jenkins_home/workspace/techUI

最新推荐文章于 2025-07-28 11:21:27 发布

原创最新推荐文章于 2025-07-28 11:21:27 发布 · 4.6k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#jenkins #java #git

这篇博客记录了在Docker环境下使用Jenkins执行Maven命令时遇到的错误，错误信息显示为'Nosuchfileordirectory'。问题源于构建过程中找不到指定的文件或目录。解决方案可能涉及检查工作空间路径、Git配置以及确保所有依赖项已正确安装和配置。此外，还可能需要验证执行的shell脚本是否存在。修复此问题对于持续集成流程至关重要。

docker版jenkins执行maven命令

在这里插入图片描述

报错：

Started by user admin-Linux
Running as SYSTEM
Building in workspace /var/jenkins_home/workspace/techUI
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/techUI/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gitee.com/WeiboGe2012/techUI.git # timeout=10
Fetching upstream changes from https://gitee.com/WeiboGe2012/techUI.git
 > git --version # timeout=10
 > git --version # 'git version 2.30.2'
 > git fetch --tags --force --progress -- https://gitee.com/WeiboGe2012/techUI.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 5bb5b83d2ccc4510f3a34aa6c3860fa75295f0d3 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5bb5b83d2ccc4510f3a34aa6c3860fa75295f0d3 # timeout=10
Commit message: "update src/test/java/TechTest.java. 更测试地址"
 > git rev-list --no-walk 5bb5b83d2ccc4510f3a34aa6c3860fa75295f0d3 # timeout=10
[techUI] $  /bin/bash /tmp/jenkins3633621652830721347.sh
FATAL: command execution failed
java.io.IOException: error=2, No such file or directory
	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:340)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:271)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)
Caused: java.io.IOException: Cannot run program "" (in directory "/var/jenkins_home/workspace/techUI"): error=2, No such file or directory
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
	at hudson.Proc$LocalProc.<init>(Proc.java:252)
	at hudson.Proc$LocalProc.<init>(Proc.java:221)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:996)
	at hudson.Launcher$ProcStarter.start(Launcher.java:508)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:143)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:812)
	at hudson.model.Build$BuildExecution.build(Build.java:198)
	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:520)
	at hudson.model.Run.execute(Run.java:1891)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:99)
	at hudson.model.Executor.run(Executor.java:440)
Build step 'Execute shell' marked build as failure
[techUI] $ /usr/local/allure-2.17.2/bin/allure generate -c -o /var/jenkins_home/workspace/techUI/allure-report
OpenJDK 64-Bit Server VM warning: Ignoring option PermSize; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
allure-results does not exist
Report successfully generated to /var/jenkins_home/workspace/techUI/allure-report
Allure report was successfully generated.
Creating artifact for the build.
Artifact was added to the build.
Finished: FAILURE