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

Gradle CI builds fail when no test tasks are run


    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • gradle-plugin
    • None
    • Linux

      We have a gradle build with multiple subprojects.
      Gradle can check what has been build previously and will not build again if nothing changed.

      Now when changing a minor thing in the tree (like a properties file) the build will start to run, notices everyting is up to date and will not start compiling/testing/jar-ing

      But at the end of the build Jenkins says: Test reports were found but none of them are new. Did tests run?
      My answer is: no, because there was no use.

      How do I take care of this issue?

            gbois Gregory Boissinot
            bjansen bjansen
            5 Vote for this issue
            5 Start watching this issue