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
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.
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 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.
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.