|
||||||||||||||||
|
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/groups/opt_out.
Since polling can't take parametrized inputs (that would require asking the user where to poll each time a poll commenced), there is no way of it knowing what your parameter resolves to, so it doesn't try and resolve the parameter.
The only way to try and get round this would be get the user to provide a default value for polling with, use the last run's value, or to poll everything in the repository. None of these are really suitable since they're either not going to turn up changes on branches we may be interested in, or will trigger for changes that we don't care about.