[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title

Vivek Pandey commented on JENKINS-37338   Re: Pipeline scripts that should appear in /queue are returned in /runs API Cliff Meyers: >My understanding is that all pipelines basically begin running immediately, so could we assume that the build number returned for a pipeline is reliable? If not, what scenario would this not hold true in? Generally yes, pipeline almost immediately get the run id. However in certain cases where you are throttling a pipeline build, it will end up in queue. For example try this pipeline script and click on build now few times and you will see it ends up in queue: node { echo 'Hello World' properties([[$class: 'JobPropertyImpl', throttle: [count: 1, durationName: 'hour']], pipelineTriggers([])]) } >For freestyle jobs, my understanding is that there can be only one item in the queue at once. No, you can have any number of items in queue for the same pipeline jobs. Each with its own projected/estimated build id and queue id - these are queued items. >Similarly then could we assume that the build number would be "eventually correct" once the item in the queue actually moves to the run state? yes. >I don't know enough about other job types (e.g. Matrix) to know if there would be problems there. jobs resulting from matrix jobs could be either pipeline or regular jobs so same rules apply. we are not displaying them so we can hold off on them for now. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.