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

Matrix stages reported skipped instead of actual status.

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • pipeline
    • CentOS Linux release 7.5.1804 (Core)
      jenkins.noarch 2.222.1-1.1
      java-1.8.0-openjdk.i686 1:1.8.0.181-3.b13.el7_5
      Blue Ocean 1.23.0

    Description

      A matrix job where some stages are excluded is showing some of the stages as "skipped" in the Blue Ocean UI, or as having no steps in the traditional UI.

      The logs are showing that the steps have been run as expected.

      Even if a step fails in a stage, it does not show up in the UI.

      This makes the Jenkins Web UI useless for tracking the progress of a Matrix job.

      Attached is a Jenkinsfile that reproduces the problem with a single stage in the Matrix step.

      If more stages are added to the step, some of those additional stages are not shown on the web UI.

      This looks similar to:
      https://issues.jenkins-ci.org/browse/JENKINS-53816

      Attachments

        Activity

          wb8tyw John Malmberg added a comment -

          Also reproduced on Jenkins 2.231

          wb8tyw John Malmberg added a comment - Also reproduced on Jenkins 2.231
          bitwiseman Liam Newman added a comment -

          wb8tyw

           

          What does this look like in the non-Blue Ocean view? 

          What doest the full log show for your sample Jenkinsfile show? 

           

          bitwiseman Liam Newman added a comment - wb8tyw   What does this look like in the non-Blue Ocean view?  What doest the full log show for your sample Jenkinsfile show?   
          wb8tyw John Malmberg added a comment - - edited

          Jenkins_matrix_skip_bug2.PNG shows the matrix output where the no status is rendered for Matrix entry of COLOR='red' and 'SHAPE'='none' which failed in the build.

          Jenkins-62304_1_consoleText.txt shows that the job had an execution error for that cell.

          And stages that were skipped are showing up as taking 2 seconds in the traditional UI in Jenkins_matrix_skip_bug3.PNG

          wb8tyw John Malmberg added a comment - - edited Jenkins_matrix_skip_bug2.PNG shows the matrix output where the no status is rendered for Matrix entry of COLOR='red' and 'SHAPE'='none' which failed in the build. Jenkins-62304_1_consoleText.txt shows that the job had an execution error for that cell. And stages that were skipped are showing up as taking 2 seconds in the traditional UI in Jenkins_matrix_skip_bug3.PNG
          bitwiseman Liam Newman added a comment -

          wb8tyw
          I know this doesn't help you, but I suspect it would be possible to reproduce this with parallel stages, not just with matrix. It's just considerably more annoying with matrix. Thanks for the detail report!

          bitwiseman Liam Newman added a comment - wb8tyw I know this doesn't help you, but I suspect it would be possible to reproduce this with parallel stages, not just with matrix . It's just considerably more annoying with matrix. Thanks for the detail report!
          moritzboth2 Moritz Both added a comment -

          This seems to be related, so I will add my observations:

          I have a one-dimensional matrix job containing one axis with 5 or 6 stages. Some of the stages are indeed skipped, but each of the parallel runs occasionally contain stages which have been run, but are shown as "skipped". I cannot tell why these stages are shown that way, and on each run, it is different. Stages which are wrongly shown as skipped tend be be running for a longer time, though.

          The stages in question are shown as skipped (i.e. not shown with their execution time) in the regular view, too.

          Please tag or email me if you can make use of more information, such as logfiles, Jenkinsfile or screenshots.

          Regards,

          Moritz

          moritzboth2 Moritz Both added a comment - This seems to be related, so I will add my observations: I have a one-dimensional matrix job containing one axis with 5 or 6 stages. Some of the stages are indeed skipped, but each of the parallel runs occasionally contain stages which have been run, but are shown as "skipped". I cannot tell why these stages are shown that way, and on each run, it is different. Stages which are wrongly shown as skipped tend be be running for a longer time, though. The stages in question are shown as skipped (i.e. not shown with their execution time) in the regular view, too. Please tag or email me if you can make use of more information, such as logfiles, Jenkinsfile or screenshots. Regards, Moritz

          People

            Unassigned Unassigned
            wb8tyw John Malmberg
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: