-
Improvement
-
Resolution: Unresolved
-
Critical
-
None
-
using cppcheck plugin version 1.24 & Jenkins version 2.138.3
The CppCheck plugin does not execute post build step Publish CppCheck results if the build is already marked as failure.
The plugin description sais: "This plug-in is not invoked for failed builds, it is only called for stable or unstable builds (i.e., a build with failed tests)."
This really disables us to have our custom logic for deciding failure conditions
- we do have many criteria and manage our own limit thresholds across more languages
- for example we cannot see the CppChecks that need fixing, when the build failed also due to other reasons, like: unit tests, java/js compilation errors, java/js code checker errors, ...
Can you please consider removing this restiction ?
IMHO, It may be an advanced option that I need to tick on or off.
[JENKINS-54870] Allow "Publish cppCheck results" for failed builds
| Description |
Original:
The CppCheck plugin does not execute post build step [*Publish CppCheck results*] if the build is already marked as failure. The plugin description sais: "_This plug-in is not invoked for failed builds, it is only called for stable or unstable builds (i.e., a build with failed tests)._" This really disables us to have our custom logic for deciding failure conditions * we do have many criteria and manage our own limit thresholds across more languages * for example we cannot see the CppChecks that need fixing, when the build failed also due to other reasons, like: unit tests, java/js compilation errors, java/js code checker errors, ... Can you please consider removing this restiction ? IMHO, It may be an advanced option that I need to tick on or off. |
New:
The CppCheck plugin does not execute post build step *Publish CppCheck results* if the build is already marked as failure. The plugin description sais: "_This plug-in is not invoked for failed builds, it is only called for stable or unstable builds (i.e., a build with failed tests)._" This really disables us to have our custom logic for deciding failure conditions * we do have many criteria and manage our own limit thresholds across more languages * for example we cannot see the CppChecks that need fixing, when the build failed also due to other reasons, like: unit tests, java/js compilation errors, java/js code checker errors, ... Can you please consider removing this restiction ? IMHO, It may be an advanced option that I need to tick on or off. |
