|
||||||||
|
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.
There is only possibility to get information that build is failed, if you check only build status. So environment failures is seen as other failures. That why we used this BFA for getting information why it is failed. But in case of environment failure we don't want show those builds on radiators etc. So question is if BFS could abort the build in certain failure causes. Of course because BFA is run after other task so abort can be done only post build phase and in this case I think it is enough to mark build aborted, without really aborting anything.
So could this plugin get abort the build if certain failure found?