Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65065

Stop fetching data after build finishes or pause when tab is inactive

    XMLWordPrintable

Details

    Description

      In build view in blue ocean 

      (e.g. https://anonymised/blue/organizations/jenkins/build-job/detail/build-job/5364/pipeline/830)

      pulling from a jenkins master continues even though a build already finished.

      Basically things like:

      Request URL:
      https://build-jenkins.kumoroku.com/sse-gateway/listen/jenkins-blueocean-core-js-1615302278422-5iyp3
       
      Event stream - hundreds/thousands of messages like:
      {{

      {"jenkins_event_uuid":"384d9c08-5114-427b-b701-cf67e3bfa454","sse_subs_dispatcher_inst":"1117208742","pipeline_job_name":"repository-builder-sumologic/PR-2342","pipeline_run_id":"1","jenkins_event_timestamp":"1615304586265","pipeline_step_name":"sh","pipeline_step_stage_id":"402","pipeline_step_is_paused":"false","pipeline_step_flownode_id":"402","jenkins_event":"pipeline_stage","pipeline_step_stage_name":"Checkout branch PR-2342","sse_subs_dispatcher":"jenkins-blueocean-core-js-1615302278422-5iyp3","pipeline_context":"2/3/4/10/11/12/13/14/15/16/17/18/19/150/151/152/156/160/161/166/167/169/360/362/363/364/365/370/371/372/373/394/395/396/397","jenkins_instance_url":"https://anonymised","jenkins_channel":"pipeline"}

      }}

      In our case tis is problematic because after some time we get timeouts on some middle layers we have (SSO in our case), thus whole build view gets frozen:

      After that happen, java script continues to send ping request to jenkins master.

       

      Ideally would be to stop sending requests after build finishes. And pause pulling if tab is not active (which I guess is a separate improvement proposal).

      Otherwise we're not able to use the view if tab was opened for some time.

      Attachments

        Activity

          mwos Michał Woś created issue -
          mwos Michał Woś made changes -
          Field Original Value New Value
          Summary Stop fetching data after build finishes Stop fetching data after build finishes and pause when tab is inactive
          mwos Michał Woś made changes -
          Summary Stop fetching data after build finishes and pause when tab is inactive Stop fetching data after build finishes or pause when tab is inactive
          mwos Michał Woś made changes -
          Description In build view in blue ocean 

          (e.g. [https://anonymised/blue/organizations/jenkins/build-job/detail/build-job/5364/pipeline/830])

          pulling from a jenkins master continues even though a build already finished.

          Basically things like:

          Request URL:
          [https://build-jenkins.kumoroku.com/sse-gateway/listen/jenkins-blueocean-core-js-1615302278422-5iyp3]
           
          Event stream - hundreds/thousands of messages like:
          {{

          {"jenkins_event_uuid":"384d9c08-5114-427b-b701-cf67e3bfa454","sse_subs_dispatcher_inst":"1117208742","pipeline_job_name":"repository-builder-sumologic/PR-2342","pipeline_run_id":"1","jenkins_event_timestamp":"1615304586265","pipeline_step_name":"sh","pipeline_step_stage_id":"402","pipeline_step_is_paused":"false","pipeline_step_flownode_id":"402","jenkins_event":"pipeline_stage","pipeline_step_stage_name":"Checkout branch PR-2342","sse_subs_dispatcher":"jenkins-blueocean-core-js-1615302278422-5iyp3","pipeline_context":"2/3/4/10/11/12/13/14/15/16/17/18/19/150/151/152/156/160/161/166/167/169/360/362/363/364/365/370/371/372/373/394/395/396/397","jenkins_instance_url":"https://anonymised","jenkins_channel":"pipeline"}

          }}

          In our case tis is problematic because after some time we get timeouts on some middle layers, thus whole broken view gets frozen:

          !image-2021-03-10-00-32-07-665.png!

          After that happen, java script continues to send _ping_ request to jenkins master.

           

          Ideally would be to stop sending requests after build finishes. And pause pulling if tab is not active. 

          Otherwise we're not able to use the view if tab was opened for some time.
          In build view in blue ocean 

          (e.g. [https://anonymised/blue/organizations/jenkins/build-job/detail/build-job/5364/pipeline/830])

          pulling from a jenkins master continues even though a build already finished.

          Basically things like:

          Request URL:
           [https://build-jenkins.kumoroku.com/sse-gateway/listen/jenkins-blueocean-core-js-1615302278422-5iyp3]
            
           Event stream - hundreds/thousands of messages like:
           {{

          {"jenkins_event_uuid":"384d9c08-5114-427b-b701-cf67e3bfa454","sse_subs_dispatcher_inst":"1117208742","pipeline_job_name":"repository-builder-sumologic/PR-2342","pipeline_run_id":"1","jenkins_event_timestamp":"1615304586265","pipeline_step_name":"sh","pipeline_step_stage_id":"402","pipeline_step_is_paused":"false","pipeline_step_flownode_id":"402","jenkins_event":"pipeline_stage","pipeline_step_stage_name":"Checkout branch PR-2342","sse_subs_dispatcher":"jenkins-blueocean-core-js-1615302278422-5iyp3","pipeline_context":"2/3/4/10/11/12/13/14/15/16/17/18/19/150/151/152/156/160/161/166/167/169/360/362/363/364/365/370/371/372/373/394/395/396/397","jenkins_instance_url":"https://anonymised","jenkins_channel":"pipeline"}

          }}

          In our case tis is problematic because after some time we get timeouts on some middle layers, thus whole broken view gets frozen:

          !image-2021-03-10-00-32-07-665.png!

          After that happen, java script continues to send _ping_ request to jenkins master.

           

          Ideally would be to stop sending requests after build finishes. And pause pulling if tab is not active (which I guess is a separate improvement proposal).

          Otherwise we're not able to use the view if tab was opened for some time.
          mwos Michał Woś made changes -
          Description In build view in blue ocean 

          (e.g. [https://anonymised/blue/organizations/jenkins/build-job/detail/build-job/5364/pipeline/830])

          pulling from a jenkins master continues even though a build already finished.

          Basically things like:

          Request URL:
           [https://build-jenkins.kumoroku.com/sse-gateway/listen/jenkins-blueocean-core-js-1615302278422-5iyp3]
            
           Event stream - hundreds/thousands of messages like:
           {{

          {"jenkins_event_uuid":"384d9c08-5114-427b-b701-cf67e3bfa454","sse_subs_dispatcher_inst":"1117208742","pipeline_job_name":"repository-builder-sumologic/PR-2342","pipeline_run_id":"1","jenkins_event_timestamp":"1615304586265","pipeline_step_name":"sh","pipeline_step_stage_id":"402","pipeline_step_is_paused":"false","pipeline_step_flownode_id":"402","jenkins_event":"pipeline_stage","pipeline_step_stage_name":"Checkout branch PR-2342","sse_subs_dispatcher":"jenkins-blueocean-core-js-1615302278422-5iyp3","pipeline_context":"2/3/4/10/11/12/13/14/15/16/17/18/19/150/151/152/156/160/161/166/167/169/360/362/363/364/365/370/371/372/373/394/395/396/397","jenkins_instance_url":"https://anonymised","jenkins_channel":"pipeline"}

          }}

          In our case tis is problematic because after some time we get timeouts on some middle layers, thus whole broken view gets frozen:

          !image-2021-03-10-00-32-07-665.png!

          After that happen, java script continues to send _ping_ request to jenkins master.

           

          Ideally would be to stop sending requests after build finishes. And pause pulling if tab is not active (which I guess is a separate improvement proposal).

          Otherwise we're not able to use the view if tab was opened for some time.
          In build view in blue ocean 

          (e.g. [https://anonymised/blue/organizations/jenkins/build-job/detail/build-job/5364/pipeline/830])

          pulling from a jenkins master continues even though a build already finished.

          Basically things like:

          Request URL:
           [https://build-jenkins.kumoroku.com/sse-gateway/listen/jenkins-blueocean-core-js-1615302278422-5iyp3]
            
           Event stream - hundreds/thousands of messages like:
           {{

          {"jenkins_event_uuid":"384d9c08-5114-427b-b701-cf67e3bfa454","sse_subs_dispatcher_inst":"1117208742","pipeline_job_name":"repository-builder-sumologic/PR-2342","pipeline_run_id":"1","jenkins_event_timestamp":"1615304586265","pipeline_step_name":"sh","pipeline_step_stage_id":"402","pipeline_step_is_paused":"false","pipeline_step_flownode_id":"402","jenkins_event":"pipeline_stage","pipeline_step_stage_name":"Checkout branch PR-2342","sse_subs_dispatcher":"jenkins-blueocean-core-js-1615302278422-5iyp3","pipeline_context":"2/3/4/10/11/12/13/14/15/16/17/18/19/150/151/152/156/160/161/166/167/169/360/362/363/364/365/370/371/372/373/394/395/396/397","jenkins_instance_url":"https://anonymised","jenkins_channel":"pipeline"}

          }}

          In our case tis is problematic because after some time we get timeouts on some middle layers we have (SSO in our case), thus whole build view gets frozen:

          !image-2021-03-10-00-32-07-665.png!

          After that happen, java script continues to send _ping_ request to jenkins master.

           

          Ideally would be to stop sending requests after build finishes. And pause pulling if tab is not active (which I guess is a separate improvement proposal).

          Otherwise we're not able to use the view if tab was opened for some time.
          oleg_nenashev Oleg Nenashev made changes -
          Labels performance

          People

            Unassigned Unassigned
            mwos Michał Woś
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: