[
https://issues.jenkins-ci.org/browse/JENKINS-8886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159531#comment-159531
]
Nicolas VINOT commented on JENKINS-8886:
----------------------------------------
Hum, not completely fixed.
Setting violation level to 0 don't lead to NPE when submit, but then related
violation fields on config page are empty, leading to another NPE if you
re-submit this page after no violation related changes.
> NPE when configure unstable level to 0
> --------------------------------------
>
> Key: JENKINS-8886
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8886
> Project: Jenkins
> Issue Type: Bug
> Components: violations
> Affects Versions: current
> Environment: Jenkins: 1.398
> Violation plugins: 0.7.7
> Reporter: Nicolas VINOT
> Assignee: peterkittreilly
> Priority: Minor
>
> When setting 0 in unstable level, NPE occur on save.
> java.lang.NullPointerException
> hudson.plugins.violations.TypeConfig.setUnstable(TypeConfig.java:109)
> sun.reflect.GeneratedMethodAccessor397.invoke(Unknown Source)
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Unstable level fields on the configuration page are empty and not "0" after
> that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
