|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dear, @Daniel Not every bug is a really blocker. Btw it probably first my bug that i set to blocker. I appreciate your "comment every issue" efforts, but if you think that jenkins should not have such status, then feel free to open INFRA issue.
@ikedam I set issue status according to rules. You changed status without asking initial requestor why it was set to Blocker. So i set it back.
"But I don't know why this is a blocker, as users first should make publishers not to throw exceptions and flexible publish enables that with conditional executions" - read provided information in PR, boolean is deprecated method for returning publisher statuses and leads for broken flows in post-build actions that depends on correct build statuses. All this statuses is a total mess now, because part of plugins throw exception, part return boolean, part set build status directly, part set status and return failure and etc.
Ok, I will rework my initial PR. The only thing that i want to hear from maintainer is what behavior is expected for "On evaluation failure" -> "Failure build" because it influence on how we can catch and process this case.