|
||||||||
|
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.
Please have a look at the discussion in https://github.com/jenkinsci/parameterized-trigger-plugin/pull/19 .
Behaviors you pointed are not ones introduced by mistake, but ones that maintainer at that time accepted.
Parameterized-trigger 2.17 was released in Feb 2013 (more than one year ago!) and many users already use parameterized-plugin > 2.16.
Simply reverting changes in 2.17 would cause a regression for many users and we should introduce another feature to work as 2.16.