|
||||||||
|
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.
I am having the same issue. The only workaround for me is using the 'Execute Batch command' to execute Ant manually, which means I don't get the benefits of the 'Execute Ant' build step plugin.
In my situation, I want to have a job where users can enter the ClearCase config spec they want to use for that build (with Base ClearCase plugin) and the SCM uses that parameter for the build. I had that working correctly, but unfortunately the Ant step is then pasting in the large multi-line config spec into the Ant command line.
I do not know why parameterized builds automatically pass values through to Ant (or Maven) at all, as I would expect this to be up to the user to do -Dmy.ant.property=${MY_BUILD_PARAMETER}
Perhaps this can be changed to use a checkbox ('Automatically populate build parameters') that defaults to true to not break backwards compatibility, but allows us to turn it off.