Change By: A. Sam. (11/Dec/14 3:53 PM)
Description: related to JENKINS-23235 and JENKINS-13546.

When creating builds using /build, the result is a 201 response where the Location header points to the queue item that represents the new build. Example:

curl -X POST "https://myjenkins/job/plainJob/build" --insecure --include

HTTP/1.1 201 Created
Date: Thu, 11 Dec 2014 15:23:38 GMT 
Server: Jetty(winstone-2.8)
Location: https://myjenkins/queue/item/39/
Content-Length: 0
Content-Type: text/plain

For parameterized I would expect that parametrized  builds with  a  form submission  would point to  the  response however does not contain the  queue  item as well.
However
 location  header only contains the job link itself :

curl -X POST "https://myjenkins/job/formJob" --insecure  -F json='{"parameter": [{"name":"ID", "value":"260"}]}' --include

HTTP/1.1 100 Continue

HTTP/1.1 201 Created
Date: Thu, 11 Dec 2014 15:24:20 GMT 
Server: Jetty(winstone-2.8)
Location: https://myjenkins/job/formJob/
Content-Length: 0
Content-Type: text/plain
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.

Reply via email to