-
Improvement
-
Resolution: Unresolved
-
Minor
-
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.
- duplicates
-
JENKINS-5393 Jenkins falsely fails builds due to aggressive up-to-date check on junit artifacts
- Open
- is duplicated by
-
JENKINS-9438 Gradle CI builds fail when no test tasks are run
- Closed
- is related to
-
JENKINS-4931 Not updated test reports reported as error
- Closed