• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • junit-plugin
    • None
    • Java project with gradle as build tool

      Not updated test reports should not necessarily result in having the build marked as failed.

      The JUnit plugin and the Test framework in core is not built for the great up-to-date checks that is in gradle. That is, they were most likely designed on the premise that any change of anything in a project would make the build tool run the tests again. This is not true with gradle.

          [JENKINS-10035] Not updated test reports reported as error

          This related issue has a fix for the xUnit plugin

          Stig Kleppe-Jørgensen added a comment - This related issue has a fix for the xUnit plugin

          Stig Kleppe-Jørgensen added a comment - - edited

          Another issue describing the same problem

          Stig Kleppe-Jørgensen added a comment - - edited Another issue describing the same problem

          It would be nice to be able to configure whether these checks (https://github.com/jenkinsci/junit-plugin/search?utf8=%E2%9C%93&q=%22none+of+them+are+new%22) were run.

          Philip Chimento added a comment - It would be nice to be able to configure whether these checks ( https://github.com/jenkinsci/junit-plugin/search?utf8=%E2%9C%93&q=%22none+of+them+are+new%22 ) were run.

          Brice Dutheil added a comment - - edited

          Similar issue https://issues.jenkins-ci.org/browse/JENKINS-6268

          At this time the workaround is sh 'find . -name "TEST-*.xml" -exec touch {} ;'

          Brice Dutheil added a comment - - edited Similar issue https://issues.jenkins-ci.org/browse/JENKINS-6268 At this time the workaround is sh 'find . -name "TEST-*.xml" -exec touch {} ;'

            Unassigned Unassigned
            stigkj Stig Kleppe-Jørgensen
            Votes:
            7 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: