• Type: Improvement
• Resolution: Unresolved
• Priority: Major
• Component/s: jacoco-plugin
• Labels:

  None
• Environment:

  Windows Server 2008 R2 / Jenkins 1.469

[JENKINS-19197] Plug-in does not support matrix builds

Adrian Price created issue - 2013-08-14 15:30

Adrian Price made changes - 2013-08-14 15:32

Description

Original: The EMMA plug-in used to support (if I am not mistaken) use with the Jenkins/Hudson 2-dimensional matrix build job. The JaCoCo plug-in seems to expect to find the class and source files in some sub-directory of the build directory, which will almost certainly not be the case in the case of a matrix build, since there is one such build directory for each and every cell of the matrix. It would be nice if you could lift the sub-directory restriction and allow class and source files to be located in some arbitrary directory structure outside of the Jenkins build location. Also, it would be good if the classes could be loaded from JARs as well as directories - this is essential when testing Eclipse plug-ins, for example.

New: The EMMA plug-in used to support (if I am not mistaken) use with the Jenkins/Hudson 2-dimensional matrix build job. The JaCoCo plug-in seems to expect to find the class and source files in some sub-directory of the build directory, which will almost certainly not be the case for a matrix build, since there is one such build directory for each and every cell of the matrix for each and every build. It would be nice if you could lift the sub-directory restriction and allow class and source files to be located in some arbitrary directory structure outside of the Jenkins build location. Also, it would be good if the classes could be loaded from JARs as well as directories - this is essential when testing Eclipse plug-ins, for example.

Adrian Price made changes - 2013-08-14 15:35

Description	Original: The EMMA plug-in used to support (if I am not mistaken) use with the Jenkins/Hudson 2-dimensional matrix build job. The JaCoCo plug-in seems to expect to find the class and source files in some sub-directory of the build directory, which will almost certainly not be the case for a matrix build, since there is one such build directory for each and every cell of the matrix for each and every build. It would be nice if you could lift the sub-directory restriction and allow class and source files to be located in some arbitrary directory structure outside of the Jenkins build location. Also, it would be good if the classes could be loaded from JARs as well as directories - this is essential when testing Eclipse plug-ins, for example.	New: The EMMA plug-in used to support (if I am not mistaken) use with the Jenkins/Hudson multi-configuration build (the 2-dimensional matrix job kind). The JaCoCo plug-in seems to expect to find the class and source files in some sub-directory of the build directory, which will almost certainly not be the case for a matrix build, since there is one such build directory for each and every cell of the matrix for each and every build. It would be nice if you could lift the sub-directory restriction and allow class and source files to be located in some arbitrary directory structure outside of the Jenkins build location. Also, it would be good if the classes could be loaded from JARs as well as directories - this is essential when testing Eclipse plug-ins, for example.
Environment	Original: Windows Server 2008 SR2 / Jenkins 1.469	New: Windows Server 2008 R2 / Jenkins 1.469

Adrian Price made changes - 2013-09-17 15:44

Description

Original: The EMMA plug-in used to support (if I am not mistaken) use with the Jenkins/Hudson multi-configuration build (the 2-dimensional matrix job kind). The JaCoCo plug-in seems to expect to find the class and source files in some sub-directory of the build directory, which will almost certainly not be the case for a matrix build, since there is one such build directory for each and every cell of the matrix for each and every build. It would be nice if you could lift the sub-directory restriction and allow class and source files to be located in some arbitrary directory structure outside of the Jenkins build location. Also, it would be good if the classes could be loaded from JARs as well as directories - this is essential when testing Eclipse plug-ins, for example.

New: The EMMA plug-in used to support (if I am not mistaken) use with the Jenkins/Hudson multi-configuration build (the n-dimensional matrix job kind). The JaCoCo plug-in seems to expect to find the class and source files in some sub-directory of the build directory, which will almost certainly not be the case for a matrix build, since there is one such build directory for each and every cell of the matrix for each and every build. Furthermore, given that the JaCoCo plug-in *copies* all the class and source files to ${build}/jacoco/* directories, these files will be redundantly replicated across all matrix cells, leading to disk space wastage on a potentially massive scale. It would be nice if you could lift the sub-directory restriction and allow class and source files to be located in some arbitrary directory structure outside of the Jenkins build location. Also, it would be good if the classes could be loaded from JARs as well as directories - this is essential when testing Eclipse plug-ins, for example.

Collapse comment: Jason Stanley added a comment - 2015-12-03 19:38

Jason Stanley added a comment - 2015-12-03 19:38

Problem still exists with Jenkins version 1.615

Expand comment: Jason Stanley added a comment - 2015-12-03 19:38

Jason Stanley added a comment - 2015-12-03 19:38 Problem still exists with Jenkins version 1.615

Martin Heinzerling made changes - 2016-07-08 10:44

Issue Type

Original: Bug [ 1 ]

New: Improvement [ 4 ]

R. Tyler Croy made changes - 2016-07-25 23:50

Workflow

Original: JNJira [ 150645 ]

New: JNJira + In-Review [ 177720 ]