CODEWITHSUNDEEP
jenkinscontinuous-integrationautomated-testsrobotframework
Arun Ramachandran
Arun Ramachandran

Reputation: 1372

Jenkins Build Is Hanging

We are using jenkins for the continuous integration.

But now, Build jobs are not getting executed after running for a few seconds, at the same time it's not at all showing any error messages also( Not getting any error messages in it's web console ). Seems like build process is hanging for a long time.

.

Here is the screenshot of the web console & jenkins log file ( /var/log/jenkins.log) enter image description here

enter image description here

I just went through the jenkins -> Manage jenkins -> manage nodes sections & did not find any disk space issues here : Currently there are 2 executors in master node.

enter image description here

Have you ever faced this kind of issue before ? What will be the reason for this problem ? Is it due to any disk space / memory problems ?

Upvotes: 2

Views: 24876

Answers (2)

jrc16
jrc16

Reputation: 107

In my case, I found that the batch script I was kicking off from Jenkins was the problem.

I'm using Katalon Studio to run a suite of test cases and found that the '-consoleLog' flag was causing the job to hang. Once I'd removed the flag I could see the test case was able to print to the Jenkins console output.

Example with:

katalon -noSplash -runMode=console -consoleLog
-projectPath="%USERPROFILE%\repository\katalon-testing\test-project\test-project-one.prj" 
-retry=0 -testSuitePath="Test Suites/test-project/test-project-one" 
-executionProfile="uat" -browserType="Chrome"

Example without:

katalon -noSplash -runMode=console 
-projectPath="%USERPROFILE%\repository\katalon-testing\test-project\test-project-one.prj" 
-retry=0 -testSuitePath="Test Suites/test-project/test-project-one" 
-executionProfile="uat" -browserType="Chrome"

Before solving the issue, I was confused as my tests were passing on the server it was just that Jenkins wasn't able to see them passing so it would hang.

I assume that when Jenkins sees the output in the console it is able to stop the job as intended.

Upvotes: 2

Vendrov
Vendrov

Reputation: 61

From my experience one of the reasons why Jenkins build got stuck, is that you call from your job to another one and don't provide it with all of it's parameters, or one of you steps make it stuck.

My advice it go with the elimination strategy. Try to execute a simple test job, if it passed good we know that the problem is with your job. If not we probebly dealing with some infrastructure issue. If you got into conclusion that your problem is with your job try to run each step apart and try to figure what which one get you stuck. Then add some logging to it so you can point more accurately on the problem. When you get more details let me know, and I will try to assist as much as I can.

Upvotes: 0

Related Questions