Coverage reporting stops with plugin parent pom 4.27?

[Mark Waite]

I've updated a few plugins from parent pom 4.26 to parent pom 4.26.  That update has disabled coverage reporting.

For example, in the platformlabeler plugin, I ran coverage reports with:

mvn -P enable-jacoco clean install jacoco:report

In 4.26, that worked and showed the coverage report

With parent pom 4.27, that now reports

[INFO] --- jacoco-maven-plugin:0.8.7:report (report) @ platformlabeler ---

[INFO] Skipping JaCoCo execution due to missing execution data file.

I've seen the behavior with the git plugin and the elastic axis plugin as well.  Any pointers to what mistake I'm making?

Mark Waite

[James Nord]

I've just take a look at 4.27 and yes it's broken.

It shouldn't be setting the Argeline to surefire without including any other argkine ('@{argLine} newopts' iirc.  Currently this will break a few different things, including din setting the surefire JVM args from a repository .mvn file.l as well as any settings in profiles like jacoco

I can probably take a look tomorrow, for now I would downgrade, or revert the change in the plugin-pom and cut a new release.

/James

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9c938ea2-0aa3-42f0-83b4-102f37702925n%40googlegroups.com.

[Mark Waite]

On Mon, Oct 4, 2021 at 2:36 PM James Nord <te...@teilo.net> wrote:

I've just take a look at 4.27 and yes it's broken.

It shouldn't be setting the Argeline to surefire without including any other argkine ('@{argLine} newopts' iirc.  Currently this will break a few different things, including din setting the surefire JVM args from a repository .mvn file.l as well as any settings in profiles like jacoco

I can probably take a look tomorrow, for now I would downgrade, or revert the change in the plugin-pom and cut a new release.

Thanks for investigating to understand the root of the problem.  I was completely baffled by how the differences between 4.26 and 4.27 could have caused that.  I'll happily wait for more expert hands to apply a fix in a new release of the parent pom.

Thanks again,

Mark Waite

 

/James

On Mon, 4 Oct 2021, 21:20 Mark Waite, <mark.ea...@gmail.com> wrote:

I've updated a few plugins from parent pom 4.26 to parent pom 4.26.  That update has disabled coverage reporting.

For example, in the platformlabeler plugin, I ran coverage reports with:

mvn -P enable-jacoco clean install jacoco:report

In 4.26, that worked and showed the coverage report

With parent pom 4.27, that now reports

[INFO] --- jacoco-maven-plugin:0.8.7:report (report) @ platformlabeler ---

[INFO] Skipping JaCoCo execution due to missing execution data file.

I've seen the behavior with the git plugin and the elastic axis plugin as well.  Any pointers to what mistake I'm making?

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9c938ea2-0aa3-42f0-83b4-102f37702925n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPzq3pfhz1mtRCeJ%3D4mH4FCAcsEdVbt1Dy%3DtLQWhAvJY62qeiA%40mail.gmail.com.

[Jesse Glick]

Proposed hotfix (roll-forward): https://github.com/jenkinsci/plugin-pom/pull/446