[JIRA] (JENKINS-15886) parameterized builds start default ant target in Ant-Task

[cjo9...@java.net (JIRA)]

cjo9900 commented on JENKINS-15886 parameterized builds start default ant target in Ant-Task Can you attach the config.xml for the job, and an example of of the build output where this occurs. As looking at the example of the logs(below) I have tested with the copy artifact plugin, I see that the value of BUILD_SELECTOR is added to the ant command. As I am not a ANT user by default, can you see if that extra parameter(s) passed in is causing the command line to be too long and truncated, and therefore the actual targets are are not included in the cmd. Also try running the ant command in the log, in a console session as the jenkins user in the workspace for the job and see if the same occurs. example output Building on master in workspace /home/jenkins/jenkins_dev/test Copied 1 artifact from "asdfgh" build number 2 [test] $ /bin/sh -xe /tmp/hudson5015636101750070796.sh + env + grep BUILD_SELECTOR BUILD_SELECTOR=<SpecificBuildSelector plugin="copyartifact@1.25"> <buildNumber>2</buildNumber></SpecificBuildSelector> [test] $ /home/jenkins/.jenkins/tools/Ant/1.8.4/bin/ant '-DBUILD_SELECTOR=<SpecificBuildSelector plugin="copyartifact@1.25"> <buildNumber>2</buildNumber></SpecificBuildSelector>' clean jar Buildfile: /home/jenkins/jenkins_dev/test/build.xml clean: [delete] Deleting directory /home/jenkins/jenkins_dev/test/build compile: [mkdir] Created dir: /home/jenkins/jenkins_dev/test/build/classes [javac] /home/jenkins/jenkins_dev/test/build.xml:19: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1 source file to /home/jenkins/jenkins_dev/test/build/classes jar: [mkdir] Created dir: /home/jenkins/jenkins_dev/test/build/jar [jar] Building jar: /home/jenkins/jenkins_dev/test/build/jar/HelloWorld.jar BUILD SUCCESSFUL Total time: 3 seconds Finished: SUCCESS

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