[JIRA] (JENKINS-57584) NullPointerException generating Incident Key

0 Aufrufe
Direkt zur ersten ungelesenen Nachricht

Billy.Dawson1@ibm.com (JIRA)

ungelesen,
21.05.2019, 11:44:0221.05.19
an jenkinsc...@googlegroups.com
Billy Dawson created an issue
 
Jenkins / Bug JENKINS-57584
NullPointerException generating Incident Key
Issue Type: Bug Bug
Assignee: Alexander Leibzon
Attachments: Job Config.png, Stack Trace.png
Components: pagerduty-plugin
Created: 2019-05-21 15:43
Environment: Jenkins 2.164.2
Plugin Version 0.4.1
Priority: Major Major
Reporter: Billy Dawson

Hi, we've been using this plugin with no issues for some time however as of this morning one of our jobs has been failing consistently. We have a post-build action (included in screenshots) which, when the incidentKey field is blank, results in a NullPointerException (also included in screenshots) whilst trying to extract the incident key. For now, our workaround is to set a hard value in the incidentKey field.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

Billy.Dawson1@ibm.com (JIRA)

ungelesen,
23.05.2019, 11:25:0223.05.19
an jenkinsc...@googlegroups.com
Billy Dawson closed an issue as Cannot Reproduce
 

Tried unsuccessfully to reproduce the problem and observed that the problem has disappeared on the job in question. I now believe this may have been a problem with the PagerDuty API.

Change By: Billy Dawson
Status: Open Closed
Resolution: Cannot Reproduce

Billy.Dawson1@ibm.com (JIRA)

ungelesen,
06.06.2019, 05:48:0206.06.19
an jenkinsc...@googlegroups.com
Billy Dawson commented on Bug JENKINS-57584
 
Re: NullPointerException generating Incident Key

Was finally able to reproduce the problem, looks like 57798 also covers this

Billy.Dawson1@ibm.com (JIRA)

ungelesen,
06.06.2019, 05:49:0106.06.19
an jenkinsc...@googlegroups.com
Billy Dawson edited a comment on Bug JENKINS-57584
Tried unsuccessfully to reproduce the problem and observed that the problem has disappeared on the job in question. I now believe this may have been a problem with the PagerDuty API.
Allen antworten
Antwort an Autor
Weiterleiten
0 neue Nachrichten