Status: Resolved (View Workflow)
Ubuntu Version: 16.04.5 LTS
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-0ubuntu0.16.04.1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
I have a Maven parent pom.xml which combines Java and non-Java builds. Non-Java builds are built using maven plugins. (The parent pom references child submodule in a profile for convenience, when I need to build everything, but these are not used during the release process).
- The parent module has <packaging>pom</packaging>, and it contains no java, so no coverage -.exec file is generated.
- Some of the child modules are standard Java, with unit test etc.
I have a single, generic build process for each of these types of module.
Since Version 3.0.1, JaCoCo is failing my build when no exec files are found, with the following exception:
ERROR: Build step failed with exception java.lang.IllegalStateException: basedir /var/lib/jenkins/jobs/releases/jobs/Release/builds/19/jacoco/classes does not exist
Shouldn't the plugin simply do nothing when there are no exec files to process?
If this is deemed to be a feature rather than a bug, then I request a configuration that controlls the behaviour, usable both from the UI "Record JaCoCo coverage report" form and also from the Groovy API, for use in pipeline steps.
|Summary||Jacoco Plugin 3.0.3 fails build when no Jacoco exec files were available||Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available|
|Status||Open [ 1 ]||Fixed but Unreleased [ 10203 ]|
|Resolution||Duplicate [ 3 ]|
|Status||Fixed but Unreleased [ 10203 ]||Resolved [ 5 ]|