-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
When using the Ant tasks for JaCoCo I have no problem specifying a directory containing JARs or an individual JAR in \\report\structure\classfiles. It seems the Jenkins JaCoCo plugin does not support this, JARs are ignored. As a workaround I have another post-build task first extracting the JAR into a temporary directory.
[JENKINS-19915] Support specifying one or more JARs in the classPattern
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
| Description |
Original:
When using the Ant tasks for JaCoCo I have no problem specifying a directory containing JARs or an individual JAR in \\report\structure\classfiles. It seems the Jenkins JaCoCo plugin does not support this, JARs are ignored. As a workaround I have another post-build task first extracting the JAR into a temporary directory, from which the plugin then copies them into builds/*/jacoco/classes. This seems unnecessary. |
New: When using the Ant tasks for JaCoCo I have no problem specifying a directory containing JARs or an individual JAR in \\report\structure\classfiles. It seems the Jenkins JaCoCo plugin does not support this, JARs are ignored. As a workaround I have another post-build task first extracting the JAR into a temporary directory. |
| Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Ognjen Bubalo
added a comment - We are planning to reimplement usage of reports generated by the JaCoCo itself. It would fix this.
Ognjen Bubalo
added a comment - We are planning to reimplement usage of reports generated by the JaCoCo itself. It would fix this. 
Josh Landin
added a comment - This feature would be particularly useful where an upstream job did the actual build and passed the final artifact(s) to a job performing integration (or functional) tests. This is quite common and the workaround mentioned above is rather messy. I'll look into getting a patch together for this.
Josh Landin
added a comment - This feature would be particularly useful where an upstream job did the actual build and passed the final artifact(s) to a job performing integration (or functional) tests. This is quite common and the workaround mentioned above is rather messy. I'll look into getting a patch together for this. | Workflow | Original: JNJira [ 151436 ] | New: JNJira + In-Review [ 177958 ] |
I recently started to try out the Jenkins JaCoCo plug-in, specified a directory ("Path to class directories") that contained only jar files, and it worked OK.