[JIRA] (JENKINS-13362) triggered parameterized run even though a parameter is not set. first it complains that is isn't set and isn't able to trigger it, then it triggers it.

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

cjo9900 commented on JENKINS-13362 triggered parameterized run even though a parameter is not set. first it complains that is isn't set and isn't able to trigger it, then it triggers it. The problem here is that the builds are always triggered by the build step, regardless of if there are parameters for it. The message is written to the log by the FileBuildParameter item which should just be indicating that the file does not exist. and the build step should handle the case when there are no parameters to pass.

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