|
||||||||
|
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.
Ah, I see the issues in my setup now. There are actually two cases:
(1) The "Trigger/call builds on other projects" had "predefined parameters", but not all the parameters existed in one of the jobs being triggered. This is actually a legitimate use case - I might be using one step to trigger several job, which have parameters in common, but not exactly the same set in each case.
(2) One of the jobs I was triggering had a parameter of type "Extensible Choice", where the Chooice Provider was a "Global Choice Parameter" which provided a list of strings. The value of the parameter being passed was not in the list of available values. This was intentional.
Case (2) looks like it is covered by the backwards compatibiliy option - does that also handle case (1)?