-
Bug
-
Resolution: Fixed
-
Major
The functionality from JENKINS-13652 hits a NullPointerException while looking up workflow actions:
FATAL: null java.lang.NullPointerException at hudson.plugins.jira.JiraSession.getActionIdForIssue(JiraSession.java:293) at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:472) at hudson.plugins.jira.JiraIssueUpdateBuilder.perform(JiraIssueUpdateBuilder.java:96) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239)
- is related to
-
JENKINS-13652 Support workflow steps as build actions and/or post-build notifiers
-
- Closed
-
[JENKINS-13998] NPE while looking up workflow actions
Link |
New:
This issue is related to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 144466 ] | New: JNJira + In-Review [ 191106 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
This happens when there are no workflow actions available to the Jenkins user. For some reason the SOAP API responds with a null entry instead of an empty array. The workaround is to grant the Jenkins user access to all necessary workflow steps (this is a requirement anyway!). I'm making a new change to at least handle this gracefully.