Browse Source
Verification failures are generally failures which verify correctness, e.g., failures caused by test, compilation, linting, etc. Non-verification failures are generally failures related to the build toolchain, e.g., failures caused by dependency resolution, build configuration, etc. Develocity attempts to classify failures based on context, but it doesn't always classify correctly. By default, most failures are classified as non-verification. By explicitly throwing a `VerificationException` for verification task failures, the failures will be appropriately classified. See gh-45187 See also: https://docs.gradle.com/develocity/failure-classification Signed-off-by: Eric Haag <ehaag@gradle.com>pull/45202/head
5 changed files with 12 additions and 12 deletions
Loading…
Reference in new issue