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! On Sunday, March 15, 2015 at 5:00:44 AM UTC+7, Keith Thornhill wrote: > > 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 > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/68f94d16-e9d2-4293-a763-8e5faa458dfa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
