|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I agree that requiring reason for abort would be troublesome for quite a few people.
But why not do it in the same manner as giving a reason for offline node? It's optional, does not disrupt any workflow.
In my opinion feedback is always a good practice, the faster the better. If written down - cannot be forgotten.