[JIRA] [core] (JENKINS-13546) buildWithParameters: return a JSON string when client request it through content-type header

[jenkins-ci....@farialima.net (JIRA)]

François Granade commented on JENKINS-13546 buildWithParameters: return a JSON string when client request it through content-type header I'm able to consistently reproduce a case where the JSON return is incorrect. Here's how I get it, from a clean Jenkins install: I created a very simple job "myjob" with one parameter "param". Made it execute a shell that simply contains "sleep 3600" (one hour) I set the # of executors to 1, and I start one build (with parameter value "value0") to start the queue, for example running from the command line: curl -H 'Accept: application/json' -d 'param=value0' 'http://localhost:8080/job/myjob/buildWithParameters' Then I start two builds, one immediately after the other. From the command line, I simply run: curl -H 'Accept: application/json' -d 'param=value1' 'http://localhost:8080/job/myjob/buildWithParameters'; echo; curl -H 'Accept: application/json' -d 'param=value2' 'http://localhost:8080/job/myjob/buildWithParameters' The output for both commands are the same: they both return the queue item of the first of the two (the one with param=value1). So it's not possible to use the data returned as a way to look up in the queues, to later get the build id, etc... Does it help ?

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/d/optout.