[JIRA] (JENKINS-60478) When job fails, stack trace is Null

6 views

Skip to first unread message

gstock.public@gmail.com (JIRA)

unread,

Dec 13, 2019, 12:11:02 PM12/13/19

to jenkinsc...@googlegroups.com

aflat created an issue

Jenkins /

JENKINS-60478

When job fails, stack trace is Null

Issue Type:	Bug
Assignee:	Unassigned
Components:	pipeline
Created:	2019-12-13 17:10
Environment:	jenkins core: 2.200
Priority:	Major
Reporter:	aflat

My pipeline script has

 
                                                                try{
			
			jobToRun = build job: jobName, parameters: jobParameters
			jobStatus = jobToRun.result
			print "Job: ${jobName} completed, result was ${jobToRun.result}"
           
	}
	catch (Exception e){
			println "DEBUG: error message is: " + e.message
} 
                                                            

Which used to work about a month ago. Updated plugins and core, and now "e" == NULL

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

gstock.public@gmail.com (JIRA)

unread,

Dec 13, 2019, 1:40:02 PM12/13/19

to jenkinsc...@googlegroups.com

aflat updated an issue

Jenkins /

JENKINS-60478

When job fails, stack trace is Null

Change By:	aflat

My pipeline script has

{code}try{

   jobToRun = build job: jobName, parameters: jobParameters
   jobStatus = jobToRun.result
   print "Job: ${jobName} completed, result was ${jobToRun.result}"

}
catch (Exception e){
   println "DEBUG: error message is: " + e.message

}{code}

Which used to work about a month ago. Updated plugins and core, and now " e " .message == NULL

e == org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

This is when $jobName != SUCCESS. A bit annoying that a build call throws an exception in the first place

Add Comment

gstock.public@gmail.com (JIRA)

unread,

Dec 13, 2019, 2:02:02 PM12/13/19

to jenkinsc...@googlegroups.com

aflat updated an issue

Jenkins /

JENKINS-60478

When job fails, stack trace is Null

Change By:	aflat
Priority:	Major Minor

My pipeline script has

{code}try{

   jobToRun = build job: jobName, parameters: jobParameters
   jobStatus = jobToRun.result
   print "Job: ${jobName} completed, result was ${jobToRun.result}"

}
catch (Exception e){
   println "DEBUG: error message is: " + e.message
}{code}

Which used to work about a month ago. Updated plugins and core, and now e.message == NULL

e == org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

This is when $jobName != SUCCESS. A bit annoying that a build call throws an exception in the first place

Changing the severity, as I can use propagate which solves all the issues I was trying to solve by catching the exception in the first place.