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

junit step failures hidden in console output

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • junit-plugin
    • None
    • Jenkins ver. 2.73.3, Blue Ocean 1.3.2
    • Blue Ocean 1.4 - beta 3

      See the attached screenshots, for the Jenkinsfile below.

      I could have sworn this was fixed but I guess I was wrong 

      pipeline {
    agent { docker 'maven:3-alpine' }
    stages {
        stage('Build') {
            steps {
                sh 'mvn -B -U -e clean install'
            }
        }
    }
    post {
        always {
            junit '**/surefire-reports/**/*.xml'
        }
    }
}

        1. Selection_260.png
          Selection_260.png
          18 kB
        2. Selection_261.png
          Selection_261.png
          47 kB

          [JENKINS-48250] junit step failures hidden in console output

          R. Tyler Croy created issue -

          James Dumay added a comment -

          I wish the Pipeline model was sane.

          James Dumay added a comment - I wish the Pipeline model was sane.
          James Dumay made changes -
          Epic Link New: JENKINS-35759 [ 171771 ]
          James Dumay made changes -
          Sprint New: Blue Ocean 1.4 - beta 4 [ 441 ]

          Andrew Bayer added a comment -

          What exactly is expected here?

          Andrew Bayer added a comment - What exactly is expected here?

          James Dumay added a comment -

          abayer would you mind investigating?

          James Dumay added a comment - abayer would you mind investigating?
          James Dumay made changes -
          Assignee New: Andrew Bayer [ abayer ]
          James Dumay made changes -
          Sprint Original: Blue Ocean 1.4 - beta 4 [ 441 ] New: Blue Ocean 1.4 - beta 3 [ 416 ]
          James Dumay made changes -
          Rank New: Ranked lower

          Andrew Bayer added a comment -

          Ah, it looks like that error is being thrown in an exception in JUnitParser but not going to the listener for the step. Need to figure out how to capture that.

          Andrew Bayer added a comment - Ah, it looks like that error is being thrown in an exception in JUnitParser but not going to the listener for the step. Need to figure out how to capture that.

            abayer Andrew Bayer
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: