|
||||||||
|
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.
For case (1), I don't know whether it is a problem in 2.23 or not. It turns out that the jobs that failed under 2.23 had both case (1) AND case (2). So I guess I'm just asking - how does your code (in 2.24, both with and without compatibilty mode) handle a trigger with an undefined parameter?