Minor When calling POST /job/my-job/build with parameters on a parameterized buil, I don't get the queue item url back in the location header.
I consider this a bug since it doesn't follow the description of how the API should work according to the comments on JENKINS-12827
When triggering a non-parameterized build, the headers look like this:
[date] => Sat, 05 Sep 2015 07:55:45 GMT
[server] => Jetty(winstone-2.8)
[x-content-type-options] => nosniff
[location] => https://jenkins.mydomain/queue/item/15032/
[content-length] => 0
[connection] => close
[content-type] => text/plain; charset=UTF-8
but on a parameterized build the response headers look like this:
[date] => Sat, 05 Sep 2015 08:07:15 GMT
[server] => Jetty(winstone-2.8)
[x-content-type-options] => nosniff
[location] => https://jenkins.mydomain/job/my-parameterized-job/
[content-length] => 0
[connection] => close
[content-type] => text/plain; charset=UTF-8
[JENKINS-30317] api should return the queue url in location header for parameterized builds
Ulrik Johansson
created issue -
Ulrik Johansson
made changes -
| Description |
Original:
When calling {{POST /job/my-job/build}} with parameters on a parameterized buil, I don't get the queue item url back in the location header. When triggering a non-parameterized build, the headers look like this: {code} [date] => Sat, 05 Sep 2015 07:55:45 GMT [server] => Jetty(winstone-2.8) [x-content-type-options] => nosniff [location] => https://jenkins.mydomain/queue/item/15032/ [content-length] => 0 [connection] => close [content-type] => text/plain; charset=UTF-8 {code} but on a parameterized build the response headers look like this: {code} [date] => Sat, 05 Sep 2015 08:07:15 GMT [server] => Jetty(winstone-2.8) [x-content-type-options] => nosniff [location] => https://jenkins.mydomain/job/my-parameterized-job/ [content-length] => 0 [connection] => close [content-type] => text/plain; charset=UTF-8 {code} |
New:
When calling {{POST /job/my-job/build}} with parameters on a parameterized buil, I don't get the queue item url back in the location header. I consider this a bug since it doesn't follow the description of how the API should work according to the comments on When triggering a non-parameterized build, the headers look like this: {code} [date] => Sat, 05 Sep 2015 07:55:45 GMT [server] => Jetty(winstone-2.8) [x-content-type-options] => nosniff [location] => https://jenkins.mydomain/queue/item/15032/ [content-length] => 0 [connection] => close [content-type] => text/plain; charset=UTF-8 {code} but on a parameterized build the response headers look like this: {code} [date] => Sat, 05 Sep 2015 08:07:15 GMT [server] => Jetty(winstone-2.8) [x-content-type-options] => nosniff [location] => https://jenkins.mydomain/job/my-parameterized-job/ [content-length] => 0 [connection] => close [content-type] => text/plain; charset=UTF-8 {code} |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 165412 ] | New: JNJira + In-Review [ 197714 ] |