|
||||||||
|
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.
Thanks for the zip!
I am unable to tackle this this week, but hopefully next week I can look into this.
I am wondering if I should add the feature behavior by default (with the risk of creating problems for existing users who want exit code of 2 or 3 to be errors) or add some sort of 'result profile' at the global level / or job level. A result profile would be a collection of [errorCode -> jenkinsJobResult] mappings.
I will probably go for the first one, i.e. start by forcing the Unity3d Unit testing mod to all users. I suspect that it i a good way to enforce some standard behavior. If I cause regressions, that will be a way to get in touch with other users, which I would really like to !