[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay resolved as Not A Defect Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Status: Open Resolved Resolution: Not A Defect 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: tasman 2 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: tasman 2 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: arctic 2 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: arctic 2 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: arctic 2 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: indian arctic 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: Michael Neale Sprint: indian 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: Michael Neale Sprint: atlantic 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: 1.0- b07/b08 beta-5 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
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)
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Cliff Meyers edited a comment on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API [~vivek] [~michaelneale] Sorry to introduce a bit of a tangent but this issue is relevant to some of the changes we want to make in the UI for JENKINS-37425. When the user initiates a run, we want to immediately display a Toast with an "OPEN" link that will launch the Run Details UI. In order for Run Details to work as it's built today, we need the build number. For reasons listed above we can't always count on it, so I just wanted to outline a few scenarios to see what you guys think:* 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?* For freestyle jobs, my understanding is that there can be only one item in the queue at once. Similarly then could we assume that the Run ID build number would be "eventually correct" once the item in the queue actually moves to the run state?* I don't know enough about other job types (e.g. Matrix) to know if there would be problems there. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Cliff Meyers commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Vivek Pandey Michael Neale Sorry to introduce a bit of a tangent but this issue is relevant to some of the changes we want to make in the UI for JENKINS-37425. When the user initiates a run, we want to immediately display a Toast with an "OPEN" link that will launch the Run Details UI. In order for Run Details to work as it's built today, we need the build number. For reasons listed above we can't always count on it, so I just wanted to outline a few scenarios to see what you guys think: 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? For freestyle jobs, my understanding is that there can be only one item in the queue at once. Similarly then could we assume that the Run ID be "eventually correct" once the item in the queue actually moves to the run state? I don't know enough about other job types (e.g. Matrix) to know if there would be problems there. 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
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Right, so there really is no way to launch a build (request) and get a number back immediately. Vivek Pandey so is there a way to take a queue item and "eventually" resolve it to a run number? (as per the question) 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Vivek Pandey edited a comment on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API [~luisfarzati] No there is no guarantee for that build number to be the same, its for informational purpose to clients and must not be used in /runs API calls. A pipeline could be distributed build where each node gets executed on different build machine and part of such pipeline could be queued if executors on the build machine are not available. Classic UI displays them as 'part of pipeline build#...". This ticket talks about this use case, where a pipeline is running but parts of it (nodes) are waiting for executors. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Vivek Pandey commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Luis Farzati No there is no guarantee for that build number to be the same, its for informational purpose to clients and must not be used in /runs API calls. A pipeline could be distributed build where each node gets executed on different build machine and part of such pipeline could be queued if executors on the build machine are not available. Classic UI displays them as 'part of pipeline build#...". This ticket talks about this use case, where a pipeline is running but parts of it (nodes) are waiting for executors. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Daniel Beck commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API I think JENKINS-12827 applies to this discussion. Build numbers don't get assigned to queued builds, and for good reason: Between QueueSorter, QueueTaskDispatcher, and plugins like Set Next Build Number, this is impossible to determine before actually starting the build. Then there's the issue of canceling queue items – they don't (and shouldn't) use up build numbers, which this change would necessitate (or result in wrong results, as a specific build number could be queued and canceled again multiple times). 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Luis Farzati yes I think you are correct (perhaps Cliff Meyers can confirm). There is a small window where there are things queued, and the expected number is what you say. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title
Luis Farzati edited a comment on JENKINS-37338
Re: Pipeline scripts that should appear in /queue are returned in /runs API
[~michaelneale] I get your point about why "Queued" shouldn't be relevant, but I'm a bit lost on how would I be able to map a queue item to a run item then.When I do a ` {{ POST ` }} to ` {{ /runs ` }} , the HAL link points to a queue item, and while it's true that I also get a ` {{ expectedBuildNumber ` }} , I guess this is not 100% guaranteed. Am I right? So my initial reaction was, ok no prob I query ` {{ /runs ` }} and lookup by queue item id. But there's no evidence of the originating queue item.Am I missing something here?
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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Luis Farzati commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Michael Neale I get your point about why "Queued" shouldn't be relevant, but I'm a bit lost on how would I be able to map a queue item to a run item then. When I do a `POST` to `/runs`, the HAL link points to a queue item, and while it's true that I also get a `expectedBuildNumber`, I guess this is not 100% guaranteed. Am I right? So my initial reaction was, ok no prob I query `/runs` and lookup by queue item id. But there's no evidence of the originating queue item. Am I missing something here? 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: 1.0-b07/b08 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: 1.0-b05/b-06 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: 1.0-beta-1 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: 1.0-beta-2 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Cliff Meyers Vivek Pandey if this requires extensive frontend work lets punt this to the next sprint 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Priority: Major Minor 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Change By: James Dumay Sprint: 1.0-beta-1 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Summary: for pipeline this is actually "correct" behavior, as there is no queue on a per pipeline basis. Much more work is needed to show what parts of it are in a piepline and where it is blocked. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API I think the missing piece is showing the activity of Jenkins in the not-yet-implemented GUI, this would make it clear... otherwise, if there was a way we could enquire as to what "parts" of a pipeline are doing... we could report more intelligently why it is waiting when it is in the RUNNING state... IN a sense we don't really want "Queued" anyway - it is an artifact of Jenkins internals that we don't always want to expose. What we may want to expose is that their build is in a bad way because of exahusted executors or mis configuration - that is really what it is about. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Vivek Pandey commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Cliff Meyers Based on what I discovered after experimenting with pipeline/nodes and its behavior w.r.t being in queue and its state running as well as being in queue, I think our api implementation tries to do such re-arrangment of pipeline run state is recipe for more confusion and errors. See my last mail. Fact that a pipeline is in RUNNING state is truth and should be represented that way because its indeed running. At the same time, based on how the script is, part of it might be in queue. I am not really sure what else can we do really. 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.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Cliff Meyers created an issue Jenkins / JENKINS-37338 Pipeline scripts that should appear in /queue are returned in /runs API Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Aug/11 12:42 PM Priority: Major Reporter: Cliff Meyers from Cliff Meyers: Hitting the /runs REST API for a Pipeline shows all the job runs, including those that probably should be in the /queue. The status of all jobs is "RUNNING" which also feels a bit misleading. from Vivek Pandey What needs to happen is that if a build item is in queue, should not be returned. We should not be mixing run object with queue because they are vastly different. There is already an API /pipeline/:id/activities Ivan implemented to give all runs and items in queue, so if this is what you look for you can use that. Add Comment
