[JIRA] (JENKINS-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Michael Neale closed an issue as Won't Fix lets close this until we know it is needed. Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Michael Neale Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work I can't see how these fix the underlying issue, but if it saves me doing something then 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Cliff Meyers commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work No, I believe that once JENKINS-38540 and JENKINS-37379 are implemented that this will be unnecessary. 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Cliff Meyers edited a comment on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work No, I believe that once JENKINS-38540 and JENKINS-37379 are implemented that this issue will be unnecessary. 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Michael Neale commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work Cliff Meyers is this something you still want tom to take a look at ? 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Michael Neale Sprint: 1.0-pre-beta-1, 1.0-beta-1, pacific, atlantic, 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: James Dumay Sprint: 1.0-pre-beta-1, 1.0-beta-1, 26-september, 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: James Dumay Sprint: 1.0-pre-beta-1, 1.0-beta-1 , 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Cliff Meyers commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work Tom FENNELLY: yep, let me see if I can unblock it myself, rather than having to make the pub/sub stuff more involved. Will let you know once I get to JENKINS-37379, should be later this week. 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Michael Neale commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work Should really see what cliff cooks up on JENKINS-37379 - before tackling this. May not be needed. 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: James Dumay Sprint: 1.0-pre-beta-1 , 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: James Dumay Priority: Major Critical 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Michael Neale commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work Cliff Meyers is this blocking favourite realtime stuff? 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Michael Neale Priority: Blocker Major 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY commented on JENKINS-37340 Re: Need another pubsub event to indicate that a job run has actually started doing some work The run_started event fires at the right time i.e. when the run moves out of the queue. The problem with pipeline runs is that this happens immediately as the run creates a "lightweight" run task that's not really doing anything yet. We need another pubsub event to let listeners know when the run has actually started "running" some of the pipeline steps. Please remember that the pubsub stuff should remain generic i.e. not specific to the UI needs, so when we hit things like this we need to address them in a general way Vs just having the UI goggles on. 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Tom FENNELLY From [~cliffmeyers]The server side events for Pipeline jobs fire immediately. If the user presses the "Build Now" from Classic UI eight times, the Blue Ocean UI will receive events showing status of "QUEUED", "ALLOCATED" and "RUNNING" for all eight jobs immediately. Meanwhile the classic UI shows six of the jobs as queued, while two are running (what the user would expect with only two executors active.Some implementation ideas, from [~cliffmeyers]Introduce custom logic in "pubsub-light" SyncRunListener to not fire start events for Pipeline jobs. Create some kind of new listener - "PipelineSyncRunListener, possibly in a new module like pipeline-pubsub-light" - when receives notification of Pipeline's step/stage start and then produces the proper start event as in SyncRunListener.and impl ideas from [~tfennelly]Keep the existing "started" event but add a new event called "running" which the Blue Ocean UI would use to transition the job from "queued" to "running" -From [~tfennelly] ... the run_started event fires at the right time i.e. when the run moves out of the queue. The problem with pipeline runs is that this happens immediately as the run creates a "lightweight" run task that's not really doing anything yet. We need another pubsub event to let listeners know when the run has actually started "running" some of the pipeline steps.Please remember that the pubsub stuff should remain generic i.e. not specific to the UI needs, so when we hit things like this we need to address them in a general way Vs just having the UI goggles on. Add Comment
[JIRA] (JENKINS-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Tom FENNELLY From [~cliffmeyers]The server side events for Pipeline jobs fire immediately. If the user presses the "Build Now" from Classic UI eight times, the Blue Ocean UI will receive events showing status of "QUEUED", "ALLOCATED" and "RUNNING" for all eight jobs immediately. Meanwhile the classic UI shows six of the jobs as queued, while two are running (what the user would expect with only two executors active.Some implementation ideas, from [~cliffmeyers]Introduce custom logic in "pubsub-light" SyncRunListener to not fire start events for Pipeline jobs. Create some kind of new listener - "PipelineSyncRunListener, possibly in a new module like pipeline-pubsub-light" - when receives notification of Pipeline's step/stage start and then produces the proper start event as in SyncRunListener.and impl ideas from [~tfennelly]Keep the existing "started" event but add a new event called "running" which the Blue Ocean UI would use to transition the job from "queued" to "running" - From [~tfennelly] ... the run_started event fires at the right time i.e. when the run moves out of the queue. The problem with pipeline runs is that this happens immediately as the run creates a "lightweight" run task that's not really doing anything yet. We need another pubsub event to let listeners know when the run has actually started "running" some of the pipeline steps.Please remember that the pubsub stuff should remain generic i.e. not specific to the UI needs, so when we hit things like this we need to address them in a general way Vs just having the UI goggles on. Add Comment
[JIRA] (JENKINS-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Tom FENNELLY Component/s: sse-gateway-plugin 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-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Tom FENNELLY From [~cliffmeyers]The server side events for Pipeline jobs fire immediately. If the user presses the "Build Now" from Classic UI eight times, the Blue Ocean UI will receive events showing status of "QUEUED", "ALLOCATED" and "RUNNING" for all eight jobs immediately. Meanwhile the classic UI shows six of the jobs as queued, while two are running (what the user would expect with only two executors active.Some implementation ideas, from [~cliffmeyers]Introduce custom logic in "pubsub-light" SyncRunListener to not fire start events for Pipeline jobs. Create some kind of new listener - "PipelineSyncRunListener, possibly in a new module like pipeline-pubsub-light" - when receives notification of Pipeline's step/stage start and then produces the proper start event as in SyncRunListener.and impl ideas from [~tfennelly]Keep the existing "started" event but add a new event called "running" which the Blue Ocean UI would use to transition the job from "queued" to "running" From [~tfennelly] ... the run_started event fires at the right time i.e. when the run moves out of the queue. The problem with pipeline runs is that this happens immediately as the run creates a "lightweight" run task that's not really doing anything yet. We need another pubsub event to let listeners know when the run has actually started "running" some of the pipeline steps.Please remember that the pubsub stuff should remain generic i.e. not specific to the UI needs, so when we hit things like this we need to address them in a general way Vs just having the UI goggles on. Add Comment
[JIRA] (JENKINS-37340) Need another pubsub event to indicate that a job run has actually started doing some work
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-37340 Need another pubsub event to indicate that a job run has actually started doing some work Change By: Tom FENNELLY Summary: Pipeline jobs fire SSE " Need another pubsub event to indicate that a job run has actually started " events prematurely when classic UI shows the runs as "queued" doing some work 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.
