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

Not updated test reports reported as error

    XMLWordPrintable

Details

    • Improvement
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • junit-plugin
    • None
    • Java project with gradle as build tool

    Description

      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.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-5393 Jenkins falsely fails builds due to aggressive up-to-date check on junit artifacts

          • Major - Major loss of function.
          • Open
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-9438 Gradle CI builds fail when no test tasks are run

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-4931 Not updated test reports reported as error

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            stigkj Stig Kleppe-Jørgensen added a comment -

            This related issue has a fix for the xUnit plugin

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

            Another issue describing the same problem

            stigkj Stig Kleppe-Jørgensen added a comment - - edited Another issue describing the same problem
            ptomato 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.

            ptomato 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.
            bric3 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 {} ;'

            bric3 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 {} ;'

            People

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

              Dates

                Created:
                Updated: