Empty Jenkins Workspace causing Jenkins build failure

0 votes

I’m trying to run a Jenkins job on CI using “Delete workspace before build starts” but when I build the job, it fails.

Started by user [8mha:AAAAmR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZe/dLi1CL93MzCpMQcIwDWRQFzwgAAAA==[0mmosawi
Building remotely on [8mha:AAAArx+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAypEgYV/eT83ILSktQi/ZLsVN3kxJxkXaDdpRW6RRmpOWa6FWYmuoYA2b5uWNkAAAA=[0mtke-calc-linux-rhel6-x64-1 (rhel6-java7 rhel6) in workspace /jenkins/workspace/completeness_compiler_runtime_tests
Using remote perforce client: completeness_compiler_runtime_tests-217915412
[completeness_compiler_runtime_tests] $ p4 workspace -o completeness_compiler_runtime_tests-217915412
Last build changeset: 61685
[completeness_compiler_runtime_tests] $ p4 changes -s submitted -m 1 //completeness_compiler_runtime_tests-217915412/...
[completeness_compiler_runtime_tests] $ p4 -s changes -s submitted //completeness_compiler_runtime_tests-217915412/...@61686,@61695
[completeness_compiler_runtime_tests] $ p4 describe -s 61695
[completeness_compiler_runtime_tests] $ p4 -G where //...
[completeness_compiler_runtime_tests] $ p4 -s users mosawi
[completeness_compiler_runtime_tests] $ p4 user -o mosawi
Sync'ing workspace to changelist 61695.
[completeness_compiler_runtime_tests] $ p4 -s sync //completeness_compiler_runtime_tests-217915412/...@61695
Sync complete, took 382 ms
No emails were triggered.
[completeness_compiler_runtime_tests] $ /bin/sh -xe /tmp/hudson3579240812233061648.sh
+ cd /jenkins/workspace/completeness_compiler_runtime_tests/TPS/qel/automation/tools
/tmp/hudson3579240812233061648.sh: line 3: cd: /jenkins/workspace/completeness_compiler_runtime_tests/TPS/qel/automation/tools: No such file or directory
Build step 'Execute shell' marked build as failure
Sending e-mails to: mosawi@generalatomics.com
Email was triggered for: Failure
Sending email for trigger: Failure
Sending email to: mosawi_haddadian@generalatomics.com

Any help would be appreciated.

Aug 8, 2018 in Jenkins by Hannah
• 18,410 points

1 answer to this question.

0 votes
/tmp/hudson3579240812233061648.sh: line 3: cd: /jenkins/workspace/completeness_compiler_runtime_tests/TPS/qel/automation/tools

The error is in execute shell step.

On line 3, in your job config you are cd'ing to some directory that is relative to workspace root. Your wokrspace root is likely


With completeness_compiler_runtime_tests being the name of the job. Since you've just deleted everything stored inside of /jenkins/workspace/completeness_compiler_runtime_tests/ - you can't cd to the dir mentioned in the error because it does not exist.

answered Aug 8, 2018 by Kalgi
• 51,950 points

Related Questions In Jenkins

0 votes
1 answer

Why is it displaying Jenkins build failure for Android app

I think you should try this. Try Uninstalling ...READ MORE

answered Apr 12, 2018 in Jenkins by shubham
• 6,910 points
+2 votes
5 answers
0 votes
1 answer

sonar XML plugin installation failure in jenkins

You can try this link which SonarQube XML ...READ MORE

answered Jun 20, 2018 in Jenkins by Atul
• 10,240 points
0 votes
1 answer

Jenkins: Build Pipeline Plugin Scheduled Trigger

This can be done by setting the ...READ MORE

answered Jul 10, 2018 in Jenkins by Sophie may
• 10,100 points
+15 votes
2 answers

Git management technique when there are multiple customers and need multiple customization?

Consider this - In 'extended' Git-Flow, (Git-Multi-Flow, ...READ MORE

answered Mar 26, 2018 in DevOps & Agile by DragonLord999
• 8,450 points
+2 votes
1 answer
0 votes
1 answer

Jenkins - simply robocopy in Jenkins finishes marks build with failure

robocopy returns a bit map This is the ...READ MORE

answered Aug 6, 2018 in Jenkins by Kalgi
• 51,950 points
0 votes
2 answers

Jenkins - identify if build is tagged

Set refspec to: +refs/tags/*:refs/remotes/origin/tags/* branch specifier: ** Under build triggers check ...READ MORE

answered Oct 25, 2018 in Jenkins by kailash