As I understand it, a build could be queued, cancelled, queued again and thus end up with the same build id. With this plugin, I'm appending a UUID to the build in order to identify a unique run no matter what happened in the queue.
However, you've shown a way of uniquely identifying a build by using the inQueueSince information under Location which would probably do the same thing. If you check build 25 and it's got a different inQueueSince, you can assume it's not the droid you are looking for. Nothing is likely to change the inQueueSince once a build joins a queue, is it? On 31 July 2014 11:19, Daniel Beck <[email protected]> wrote: > > On 31.07.2014, at 12:19, Stuart Davidson <[email protected]> > wrote: > > > 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 :) > > This was changed for parameterized builds in 1.561 to match the behavior > for unparameterized builds. Example how the core API works is in this Jira > comment: > > > https://issues.jenkins-ci.org/browse/JENKINS-12827?focusedCommentId=201381&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-201381 > > -- > 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.
