-
Bug
-
Resolution: Unresolved
-
Critical
-
None
If the classPattern fails to match any classes, the builds/*/jacoco/classes directory is never created, causing an exception later in the report generating stage. This is confusing. It should either generate an empty report or fail immediately and with a clear message when no classes were found.
- is duplicated by
-
JENKINS-27766 Jacoco with Jenkins on Apache Tomcat: /jacoco/classes does not exist
-
- Closed
-
- links to
[JENKINS-19916] Confusing failure mode when no classes found by classPattern
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Priority | Original: Minor [ 4 ] | New: Blocker [ 1 ] |
Link |
New:
This issue is duplicated by |
Priority | Original: Blocker [ 1 ] | New: Critical [ 2 ] |
Workflow | Original: JNJira [ 151437 ] | New: JNJira + In-Review [ 177959 ] |
Assignee | Original: Ognjen Bubalo [ ognjenb ] | New: Donald Woods [ drwoods ] |
Remote Link | New: This issue links to "CloudBees Internal OSS-245 (Web Link)" [ 18935 ] |