I've not touched this in a while Daniel, but I found that if I was queuing multiple copies of the same job, I could give it a unique ID - whereas /build simply gives you the information it's queuing.
That's not to say that the queue API has improved to include information like this - like I say, it's been a while :) On 31 July 2014 11:08, Daniel Beck <[email protected]> wrote: > > On 21.11.2013, at 20:01, Stuart Davidson <[email protected]> > wrote: > > > The plugin allows you to request a build from the API but it returns a > JSON snippet with a UUID for the job. This allows you to track the status > of a job (using another part of the API) even before it has left the queue > and has been assigned a run id - being in the queue is a valid state. > > How is this plugin different from the queue item API whose ID/location is > provided in the Location header from /build? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/8nph2HKmiJA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
