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

Go to the end of the expanded log

    Details

    • Similar Issues:
    • Sprint:
      pannonian, iapetus, 1.0

      Description

      When clicking a failed stage (or directly going to it), the log does not scroll to the end, which is presumably where you could see an error.

      Noticed on ci: https://ci.blueocean.io/blue/organizations/jenkins/Pipeline%20Editor/detail/PR-15/1/pipeline/11

        Attachments

          Issue Links

            Activity

            Hide
            tscherler Thorsten Scherler added a comment - - edited
            Show
            tscherler Thorsten Scherler added a comment - - edited Keith Zantow that link is not working anymore. How can I reproduce this? e.g. https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/feature%2FJENKINS-38598-create-pipeline-from-github/4/pipeline works as expected
            Hide
            kzantow Keith Zantow added a comment -
            Show
            kzantow Keith Zantow added a comment - Thorsten Scherler I really should owe you a jenkinsfile, but noticed this again here: https://ci.blueocean.io/blue/organizations/jenkins/Pipeline%20Editor/detail/PR-17/16/pipeline
            Hide
            tscherler Thorsten Scherler added a comment -

            Is what I see for that link.

            chasing the dragon https://www.youtube.com/watch?v=uBVkk5rW0lw

            Show
            tscherler Thorsten Scherler added a comment - Is what I see for that link. chasing the dragon https://www.youtube.com/watch?v=uBVkk5rW0lw
            Hide
            michaelneale Michael Neale added a comment -

            I tried, but can't reproduce this. I made a long pipeline log with a failing step - and it jumped to it.

            If there is another example we can record a video of - should do it, but we can park this for now (I suspect there is some race condition)

            Show
            michaelneale Michael Neale added a comment - I tried, but can't reproduce this. I made a long pipeline log with a failing step - and it jumped to it. If there is another example we can record a video of - should do it, but we can park this for now (I suspect there is some race condition)
            Hide
            jamesdumay James Dumay added a comment -

            I think you were able to reproduce with the Jenkinsfile below but it seems to have been fixed.

            node {
               try {
                 stage('first') {
                     sh 'ls ../ && exit 1'
                 }
               } finally {
                 stage('second') {
                     sh 'ls ../ && exit 1'
                 }
               }
            }
            
            Show
            jamesdumay James Dumay added a comment - I think you were able to reproduce with the Jenkinsfile below but it seems to have been fixed. node { try { stage( 'first' ) { sh 'ls ../ && exit 1' } } finally { stage( 'second' ) { sh 'ls ../ && exit 1' } } }

              People

              • Assignee:
                tscherler Thorsten Scherler
                Reporter:
                kzantow Keith Zantow
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: