Change By: René Scheibe (14/Dec/14 2:41 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
{code}
HTTP/1.1
 100 Continue

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
{code}

I would expect that parametrized builds with form submission would point to the queue item as well.
However location header only contains the job link itself:

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

{code}
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

{code}
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to