[JIRA] (JENKINS-42137) BlueOcean making unnecessary requests for pipeline run details
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42137 BlueOcean making unnecessary requests for pipeline run details Change By: Michael Neale The BlueOcean main pipeline screen (https://ci.blueocean.io/blue/pipelines) has an event websocket thing that is connect appears to the Jenkins server be receiving events for running pipelines that are not visible, and then fetching data, creating more than expected traffic . On a regular basis this sends event from the backend to the frontend detailing things that are running. To reproduce: * Open /blue/pipelines/ in one tab* Run a job like bwalding-alwaysBlue from a classic screen in another tab* Note that /blue/pipelines/ receives events for this job and does requests. Some details: (I hope the 80shtgg3w8q5hpelba9k9 ID isn't something importanthttps://ci.blueocean.io/sse-gateway/listen/jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9{noformat}open {"dispatcherId":"jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9","dispatcherInst":1238701885} 16:15:00.445job {"jenkins_object_type":"org.jenkinsci.plugins.workflow.job.WorkflowRun","jenkins_event_uuid":"6c1358f1-f887-41bb-beb9-3228dda99df8","sse_subs_dispatcher_inst":"1238701885","job_run_status":"SUCCESS","job_name":"scratch/bwalding-alwaysBlue","jenkins_org":"jenkins","job_run_queueId":"5246","jenkins_object_name":"#2","blueocean_job_rest_url":"/blue/rest/organizations/jenkins/pipelines/scratch/pipelines/bwalding-alwaysBlue/","jenkins_object_id":"2","jenkins_event":"job_run_ended","sse_subs_dispatcher":"jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9","blueocean_job_pipeline_name":"scratch/bwalding-alwaysBlue","jenkins_object_url":"job/scratch/job/bwalding-alwaysBlue/2/","jenkins_channel":"job"} {noformat}Once the frontend receives those events, the frontend then makes a call to retrieve details about the run.https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/scratch/pipelines/bwalding-alwaysBlue/runs/2/However the important thing to note is that the bwalding-alwaysBlue job is not visible on the front screen - so the frontend is querying the backend for details on jobs that will not change the state of the front end (afaik)In a large instance that is running a lot of jobs all the time, this could be problematic.
[JIRA] (JENKINS-42137) BlueOcean making unnecessary requests for pipeline run details
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-42137 BlueOcean making unnecessary requests for pipeline run details Change By: Michael Neale Assignee: Tom FENNELLY 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-42137) BlueOcean making unnecessary requests for pipeline run details
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-42137 BlueOcean making unnecessary requests for pipeline run details Change By: Ben Walding The BlueOcean main pipeline screen (https://ci.blueocean.io/blue/pipelines) has an event websocket thing that is connect to the Jenkins server.On a regular basis this sends event from the backend to the frontend detailing things that are running.(I hope the 80shtgg3w8q5hpelba9k9 ID isn't something importanthttps://ci.blueocean.io/sse-gateway/listen/jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9{noformat}open {"dispatcherId":"jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9","dispatcherInst":1238701885} 16:15:00.445job {"jenkins_object_type":"org.jenkinsci.plugins.workflow.job.WorkflowRun","jenkins_event_uuid":"6c1358f1-f887-41bb-beb9-3228dda99df8","sse_subs_dispatcher_inst":"1238701885","job_run_status":"SUCCESS","job_name":"scratch/bwalding-alwaysBlue","jenkins_org":"jenkins","job_run_queueId":"5246","jenkins_object_name":"#2","blueocean_job_rest_url":"/blue/rest/organizations/jenkins/pipelines/scratch/pipelines/bwalding-alwaysBlue/","jenkins_object_id":"2","jenkins_event":"job_run_ended","sse_subs_dispatcher":"jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9","blueocean_job_pipeline_name":"scratch/bwalding-alwaysBlue","jenkins_object_url":"job/scratch/job/bwalding-alwaysBlue/2/","jenkins_channel":"job"} {noformat}Once the frontend receives those events, the frontend then makes a call to retrieve details about the run.https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/scratch/pipelines/bwalding-alwaysBlue/runs/2/However the important thing to note is that the bwalding-alwaysBlue job is not visible on the front screen - so the frontend is querying the backend for details on jobs that will not change the state of the front end (afaik)In a large instance that is running a lot of jobs all the time, this could be problematic. Add Comment
[JIRA] (JENKINS-42137) BlueOcean making unnecessary requests for pipeline run details
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42137 BlueOcean making unnecessary requests for pipeline run details Change By: Michael Neale Priority: Minor 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-42137) BlueOcean making unnecessary requests for pipeline run details
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-42137 BlueOcean making unnecessary requests for pipeline run details Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/17 6:23 AM Environment: b23 Priority: Minor Reporter: Ben Walding The BlueOcean main pipeline screen has an event websocket thing that is connect to the Jenkins server. On a regular basis this sends event from the backend to the frontend detailing things that are running. (I hope the 80shtgg3w8q5hpelba9k9 ID isn't something important https://ci.blueocean.io/sse-gateway/listen/jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9 open {"dispatcherId":"jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9","dispatcherInst":1238701885} 16:15:00.445 job {"jenkins_object_type":"org.jenkinsci.plugins.workflow.job.WorkflowRun","jenkins_event_uuid":"6c1358f1-f887-41bb-beb9-3228dda99df8","sse_subs_dispatcher_inst":"1238701885","job_run_status":"SUCCESS","job_name":"scratch/bwalding-alwaysBlue","jenkins_org":"jenkins","job_run_queueId":"5246","jenkins_object_name":"#2","blueocean_job_rest_url":"/blue/rest/organizations/jenkins/pipelines/scratch/pipelines/bwalding-alwaysBlue/","jenkins_object_id":"2","jenkins_event":"job_run_ended","sse_subs_dispatcher":"jenkins-blueocean-core-js-1487311928759-80shtgg3w8q5hpelba9k9","blueocean_job_pipeline_name":"scratch/bwalding-alwaysBlue","jenkins_object_url":"job/scratch/job/bwalding-alwaysBlue/2/","jenkins_channel":"job"}