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

really hard to exit BO build page when build is ongoing and creates lots of console output.

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Chrome
      Blue Ocean 1.0.1

      I was sent a link to a build log in Blue Ocean and opened that.

      The build was spewing lots of data to the console (several thousand lines and almost a new line a second - which should be fine.

      When the page loaded it scrolled to the bottom of the console output in the last step (again not an issue)

      However I wanted to go to the Job not the Build page so I needed to go to the header.

      However everytime I scrolled up the page jumped back down because of the new console output in the sh step and Blue Ocean decided that I wanted to view that and not something else.

      This is clearly wrong and makes navigating back out of a page tedious.

      Video (only available to cloudbees employees (sorry it contians some sensitive data)) is at https://youtu.be/3S0CLgBc8qw

          [JENKINS-44182] really hard to exit BO build page when build is ongoing and creates lots of console output.

          James Dumay added a comment -

          We did a huge refactor of the running pipeline functionality as part of JENKINS-38523 that cleans up the quirky behaviour you are describing here.

          Would you mind giving 1.1.0-beta4 a try from the experimental update center and see how the new behaviour is to your liking?

          James Dumay added a comment - We did a huge refactor of the running pipeline functionality as part of JENKINS-38523 that cleans up the quirky behaviour you are describing here. Would you mind giving 1.1.0-beta4 a try from the experimental update center and see how the new behaviour is to your liking?

            Unassigned Unassigned
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: