-
Bug
-
Resolution: Fixed
-
Minor
-
None
When the "properties" element isn't specified in the JSON form blob the Job processing logic hits a NPE.
This could happen if a Custom project type uses a form that overrides Job's configure.jelly, or if another tool is used to produce the JSON message.
FWIW, I manipulated the JSON message to drop every other field without a problem processing the forms for FreeStyleProject and MatrixProject, "properties" was the only one I couldn't remove and have it do the right thing.
I have a PR to fix this here: https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/891/
[JENKINS-23437] NPE when binding JSON form data without 'properties' field
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 156063 ] | New: JNJira + In-Review [ 195329 ] |