jacoco-plugin
jacoco-plugin copied to clipboard
Jenkins JaCoCo Plugin
Bumps [plugin](https://github.com/jenkinsci/plugin-pom) from 4.19 to 4.46. Release notes Sourced from plugin's releases. 4.46 🐛 Bug fixes Add JUnit 4.x to dependency management (#596) @jetersen 📦 Dependency updates Bump jenkins-test-harness from...
Bumps [dashboard-view](https://github.com/jenkinsci/dashboard-view-plugin) from 2.17 to 2.447.vda_124dd35f11. Release notes Sourced from dashboard-view's releases. 2.447.vda_124dd35f11 👷 Changes for plugin developers Bump bom-2.289.x from 1438.v6a_2c29d73f82 to 1500.ve4d05cd32975 (#184) @jetersen 👻 Maintenance Make spotless...
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from 3.2.1 to 3.4.2. Release notes Sourced from plexus-utils's releases. 3.4.2 🚀 New features and improvements Provides a CachingOuptutStream and a CachingWriter (#184) @gnodet Use (already) precalculated value...
Add support for environment variables in source and class text fields in the plugin's configuration
I've met the problem, that when environment variables are used in the JaCoCo configuration in Jenkins. Exclusions variables is parsed and the value is sent to the JaCoCo report generation,...
#161 The log says > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M4:test (default-test) on project jacoco: Use useUnlimitedThreads=true, or only threadCount > 0, or (threadCountSuites > 0 and threadCountClasses > 0...
Provide an additional link in the coverage results page to download the aggregated `jacoco.xml` file. See the full description in [JENKINS-60356](https://issues.jenkins-ci.org/browse/JENKINS-60356).
As a project getting bigger, integer percentage is not enough. Sometimes we cover a lot more lines, it just increases only 0.1 percentage. Because of this, it seems that we...
The use case is a big application (more than 1 Gb, less than 2 gb), which collects metrics via jacoco-agent every night, to get statitics of functional test coverage. When...
Build parameter that would trigger the removal of the original exec file after it has been copied to the build job directory. Default setting being false, hence not backward incompatible...
This is basically a re-implementation of PR #77, or at least parts of it. Seems like it was already implemented except that the log messages still contained the unexpanded patterns...