[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception

0 views
Skip to first unread message

aaron.k.sua@gmail.com (JIRA)

unread,
May 24, 2019, 10:56:01 AM5/24/19
to jenkinsc...@googlegroups.com
Aaron Sua created an issue
 
Jenkins / Bug JENKINS-57664
On Release of a Version recieve a Null Pointer exception
Issue Type: Bug Bug
Assignee: Unassigned
Components: jira-plugin
Created: 2019-05-24 14:55
Environment: Jenkins version 2.164.3
Jira Plugin version 3.07
Priority: Major Major
Reporter: Aaron Sua

After upgrading from Jenkins 2.107 and Jira Plugin 2.5 when executing the Release A Version step in a Jenkins job the output simply states:

[JIRA] Marking version <foo> in project <bar> as released.
FATAL: Unable to release jira version <foo>/<bar>: java.lang.NullPointerException
Finished: FAILURE

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

radek.antoniuk@quiddia.com (JIRA)

unread,
May 25, 2019, 10:27:01 AM5/25/19
to jenkinsc...@googlegroups.com
Radek Antoniuk commented on Bug JENKINS-57664
 
Re: On Release of a Version recieve a Null Pointer exception

Can you attach full stacktrace from Jenkins logs?

aaron.k.sua@gmail.com (JIRA)

unread,
May 25, 2019, 11:24:02 AM5/25/19
to jenkinsc...@googlegroups.com

aaron.k.sua@gmail.com (JIRA)

unread,
May 25, 2019, 11:25:01 AM5/25/19
to jenkinsc...@googlegroups.com
Aaron Sua commented on Bug JENKINS-57664
 
Re: On Release of a Version recieve a Null Pointer exception

I discovered the individual jobs were not updated to use the new version of the plugin.  After editing the jobs to update Slack messages the proper plugin version is referenced in the job config.

radek.antoniuk@quiddia.com (JIRA)

unread,
May 25, 2019, 11:27:01 AM5/25/19
to jenkinsc...@googlegroups.com

Uhm, I'm confused, you're mentioning Slack now. Did the problem occur because of Slack plugin? 

radek.antoniuk@quiddia.com (JIRA)

unread,
May 25, 2019, 11:28:02 AM5/25/19
to jenkinsc...@googlegroups.com
Radek Antoniuk edited a comment on Bug JENKINS-57664
Uhm, I'm confused, you're mentioning Slack now. Did the problem occur because of Slack plugin?   Or do you mean that after re-saving the job configuration it just started working?

If the latter, are you able to dig out the full stacktrace still? It might help figuring out why the jobs needed to be re-saved after plugin update.

radek.antoniuk@quiddia.com (JIRA)

unread,
May 25, 2019, 11:31:02 AM5/25/19
to jenkinsc...@googlegroups.com
Radek Antoniuk updated an issue
 
Change By: Radek Antoniuk
Environment: Jenkins version 2.164.3
Jira Plugin version 3.
07 0.7

vilppu.vuorinen@jubic.fi (JIRA)

unread,
May 27, 2019, 3:45:02 AM5/27/19
to jenkinsc...@googlegroups.com
Vilppu Vuorinen commented on Bug JENKINS-57664
 
Re: On Release of a Version recieve a Null Pointer exception

Radek Antoniuk attaching full Jenkins log (from System log) is of no use here. The exception seems to be terminated and printed to build log without a stacktrace.

 

I have a setup without the Slack plugin with the same issue. The issue was not present with 3.0.6. I'm fairly confident 3.0.7 is the culprit here.

radek.antoniuk@quiddia.com (JIRA)

unread,
May 27, 2019, 7:25:02 PM5/27/19
to jenkinsc...@googlegroups.com

I was able to re-produce the NPE on a plain Jenkins instance that had no JIRA site defined in the Global settings. Can you try the following:

  • go to Global configuration and ensure connectivity to JIRA with the Validate button? (then Save configuration and re-run the build)
  • if that doesn't help, can you try removing and re-adding the JIRA site? 

vilppu.vuorinen@jubic.fi (JIRA)

unread,
May 28, 2019, 1:32:02 AM5/28/19
to jenkinsc...@googlegroups.com

Validate prints out a success. I tried recreating the site config, but I don't have a test project for validating this. I'll have to get back to this after there is an actual release build.

It looks like the config format was changed in 3.0.7 as I could not roll back to 3.0.6 without losing site config. It sure looks like everything is pointing back to the site config.

vilppu.vuorinen@jubic.fi (JIRA)

unread,
Jun 4, 2019, 8:59:02 AM6/4/19
to jenkinsc...@googlegroups.com

Looks like deleting the site config and creating it again fixed the issue. It sounds like config migration breaking existing configs.

vilppu.vuorinen@jubic.fi (JIRA)

unread,
Jun 7, 2019, 6:07:02 AM6/7/19
to jenkinsc...@googlegroups.com

After a single successful release the issue has resurfaced. I've now rolled back to 3.0.6 hoping I could get the releases rolling again.

olamy@apache.org (JIRA)

unread,
Jun 27, 2019, 11:17:03 PM6/27/19
to jenkinsc...@googlegroups.com

olamy@apache.org (JIRA)

unread,
Jun 27, 2019, 11:18:03 PM6/27/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages