/queue/item regression?

[Keith Thornhill]

starting a build returns a Location header with a path pointing to /queue/item/NUM/. following up with a request to /queue/item/NUM/api/json used to return a struct which could be polled to discover the build number once it starts.  it now returns a 404. 

is this a purposeful API change or a regression? in either case, it seems that we have lost the ability to reliably track jobs after they have been queued via the api.

last known working version: 1.598

using: 1.602

[Piotr Morgwai Kotarbiński]

it's a known bug:
https://issues.jenkins-ci.org/browse/JENKINS-27256
there's a link to a plugin which helps to work around the issue until fix is released.

Cheers!