java.lang.NullPointerException during build about jenkins-plugin HOT 6 CLOSED

oops ... not sure what happened ... I'll take a look in a bit

from jenkins-plugin.

hmmm ... I wonder, was the job you ran the build from created before you installed the new version of the plugin?

Typically, for fields not explicitly set Jenkins has been passing in empty strings. But if the job was created prior to a new field being added, Jenkins may pass in a null in that case.

from jenkins-plugin.

Yep, I was able to reproduce this locally and verify my theory. Interesting side effect, which will occur whenever I add a new plugin field in the future.

I'll need to make a more generic, pervasive change on the assumptions build steps make on what Jenkins passes in.

from jenkins-plugin.

I will try to reproduce this problem (and maybe other), but at now - it is first case.
I have ten jobs, I will set it for executions for whole weekend.

from jenkins-plugin.

Based on my local reproduction / confirmation of my theory, I've created a new pre-release version of the plugin stored here that is based on 98c399a.

Closing this issue out - we can reopen / open issues for additional finds as they come up.

from jenkins-plugin.

It was very fast :)

from jenkins-plugin.