On 31.07.2014, at 12:36, Stuart Davidson <[email protected]> wrote:
> 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? Queue item ID is NOT the build number (that's basically the whole point of my Jira comment). It's unique Jenkins-wide, probably similar to your UUID. As you can see in the last XML snippet, it will even tell you information about queue items that are no longer in the queue (<leftItem>, the build number is at <executable/>). If cancelled from the queue, it'll be <canceled>true</canceled> and not have an executable. -- 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.
