[JIRA] [core] (JENKINS-22051) build.xml not created after successful build

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev edited a comment on JENKINS-22051 build.xml not created after successful build the mailer plugin should not cause exceptions if one of its dependencies is not enabled. either the dependency should be forced-enabled, or the mailer plugin should be disabled. This is a common Jenkins behavior. It is not possible to check plugin dependencies excepting the runtime due to the plenty of unannotated "optional" dependencies. jenkins should NEVER fail to write a build.xml into the build directory. regardless of what plugins throw exceptions. a build.xml should ALWAYS be created. failure to create this file results in builds getting lost from the history, and at least 30 unsolved bug reports Sounds reasonable... I propose to leave this issue for the second case. Please create a separate issue for class dependencies if you don't agree.

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.