If you click on logs button of an stage, and you scroll up, you can see the log popup window, but if you try to expand the entries to see the logs, nothing happens.

          [JENKINS-33110] Log details are not shown

          Alex Soto created issue -

          Russell Gallop added a comment - - edited

          I also see this issue (workflow-aggregator 1.14, pipeline-stage-view 1.0).

          It seems to work if there is only one step in the stage, just not with more than one.

          Russell Gallop added a comment - - edited I also see this issue (workflow-aggregator 1.14, pipeline-stage-view 1.0). It seems to work if there is only one step in the stage, just not with more than one.

          Pipeline DSL examples.

          With 1 step the stage-logs are expanded (but won't contract) e.g.:

          stage 'test'
          echo 'Foo'
          

          With > 1 step the stage-logs are folded up (and won't expand) e.g.:

          stage 'test'
          echo 'Foo'
          echo 'Bar'
          

          Russell Gallop added a comment - Pipeline DSL examples. With 1 step the stage-logs are expanded (but won't contract) e.g.: stage 'test' echo 'Foo' With > 1 step the stage-logs are folded up (and won't expand) e.g.: stage 'test' echo 'Foo' echo 'Bar'
          Antonio Muñiz made changes -
          Assignee Original: Antonio Muñiz [ amuniz ]
          Sam Van Oort made changes -
          Assignee New: Sam Van Oort [ svanoort ]

          Jesse Glick added a comment -

          Easily reproduced in jenkinsci/workflow-demo:1.14-2. Browser console shows

          No "data-stageId" on stage.
          

          Also, the build history widget does not update build #1 to remove the progress bar even after the build completes, unless you reload the page (#2 is updated properly); not sure if that is related to this bug or not.

          Jesse Glick added a comment - Easily reproduced in jenkinsci/workflow-demo:1.14-2 . Browser console shows No "data-stageId" on stage. Also, the build history widget does not update build #1 to remove the progress bar even after the build completes, unless you reload the page (#2 is updated properly); not sure if that is related to this bug or not.
          Sam Van Oort made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Deniz Ugurlu added a comment -

          In addition to the mentioned warning in the browser console, it looks like the click event on .node-name is fired twice when clicked.
          This toggles activation/deactivation on the log entry twice, effectively returning to the initial state. See ui/src/main/js/view/stage-logs.js:

          [...]
          var nodeNameBars = $('.node-name', stageLogsDom);
          [...]
          
          nodeNameBars.click(function() {
            // this handler is getting called twice per click for me
          });
          

          Maybe it helps to extract the registration of the click-handler from dialog.show(onshow())?

          Deniz Ugurlu added a comment - In addition to the mentioned warning in the browser console, it looks like the click event on .node-name is fired twice when clicked. This toggles activation/deactivation on the log entry twice, effectively returning to the initial state. See ui/src/main/js/view/stage-logs.js : [...] var nodeNameBars = $( '.node-name' , stageLogsDom); [...] nodeNameBars.click( function () { // this handler is getting called twice per click for me }); Maybe it helps to extract the registration of the click-handler from dialog.show(onshow()) ?
          Antonio Muñiz made changes -
          Link New: This issue is duplicated by JENKINS-33354 [ JENKINS-33354 ]
          Antonio Muñiz made changes -
          Link New: This issue is duplicated by JENKINS-33656 [ JENKINS-33656 ]

            amuniz Antonio Muñiz
            asotobueno Alex Soto
            Votes:
            12 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: