CODEWITHSUNDEEP
batch-filejenkinscmd
Fernando Rezk
Fernando Rezk

Reputation: 314

Jenkins job stuck after command start

I have a problem in my jenkins job and I isolated into one command. So I created another separate job to try to fix it.

So in this job, called "teste" I only have one single command:

start cmd /k call "C:\Program Files\myDir\myBat.bat"

This opens a separate cmd window running my bat file, which should keep running "forever".

But the problem is when I do it, my jenkins job keeps stuck into a "exit 0" operation that I have no idea from where it came from. Thats the console:

[EnvInject] - Loading node environment variables.
Building remotely on Machine01 in workspace C:\workspace\teste
[teste] $ cmd /c call C:\...dir\jenkins.bat

C:\workspace\teste>start cmd /k call "C:\Program Files\myDir\myBat.bat" 

C:\workspace\teste>exit 0

Then it keep stuck at that point.

Example of myBat.bat content:

echo hi
pause

There's any way to make this call in another window without waiting for its finish?

Upvotes: 0

Views: 2397

Answers (1)

Fernando Rezk
Fernando Rezk

Reputation: 314

I solve my problem changing the way I was calling my other .bat, calling it through powershell. But since I was from a bat file, I used the command to send a powershell command, calling my other bat file. Also, I've added another line changing the jenkins BUILD_ID to a fake one, so it doesn't kill it.

So I changed from this line:

start cmd /k call "C:\Program Files\myDir\myBat.bat"

To this :

set BUILD_ID=dontKillMe
powershell -Command "Start-Process 'C:\Program Files\myDir\myBat.bat'"

I hope it helps someone someday.

Upvotes: 1

Related Questions