[JENKINS-72825] Provide support for advanced action filtering

[jenkins-infra-bot]

I am using the forensics-api-plugin as part of the coverage-plugin for getting diffs. To determine the reference build, I call

discoverReferenceBuild()

in my pipeline.

Doing so revealed that sometimes I would not get diffs. The reason seems to be that coverage can be disabled on a per-build basis in my case, thus the reference build sometimes does not contain any coverage data.

For this reason, I would like to see support for some reference build filtering options, especially by action class and action ID.

---

Originally reported by stefan6419846, imported from: Provide support for advanced action filtering

• assignee: drulli
• status: Open
• priority: Minor
• component(s): coverage-plugin, forensics-api-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20260107-220949

Raw content of original issue

I am using the forensics-api-plugin as part of the coverage-plugin for getting diffs. To determine the reference build, I call 

discoverReferenceBuild()


in my pipeline.
Doing so revealed that sometimes I would not get diffs. The reason seems to be that coverage can be disabled on a per-build basis in my case, thus the reference build sometimes does not contain any coverage data.
For this reason, I would like to see support for some reference build filtering options, especially by action class and action ID.

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  In the warnings plugin I added a customization of the reference build
  
  https://github.com/jenkinsci/warnings-ng-plugin/blob/c538f186e085cd0ad58406a134aa9737982bb085/plugin/src/main/java/io/jenkins/plugins/analysis/core/steps/IssuesPublisher.java#L234
  
  It would make sense to use a similar way for the coverage plugin.
  
  I am not sure if this can or should be generalized in the forensics plugin. 
  

In the warnings plugin I added a customization of the reference build

https://github.com/jenkinsci/warnings-ng-plugin/blob/c538f186e085cd0ad58406a134aa9737982bb085/plugin/src/main/java/io/jenkins/plugins/analysis/core/steps/IssuesPublisher.java#L234

It would make sense to use a similar way for the coverage plugin.

I am not sure if this can or should be generalized in the forensics plugin.

[jenkins-infra-bot]

stefan6419846:

• Original comment link
• Raw content of original comment:

  I have not been sure where this makes more sense - as the forensics plugin took over the reference build handling, I decided to report it there. But I am completely fine with a implementation inside the coverage plugin as well.
  

I have not been sure where this makes more sense - as the forensics plugin took over the reference build handling, I decided to report it there. But I am completely fine with a implementation inside the coverage plugin as well.

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  When this is generalized, then we might need multiple reference builds, one for the warnings plugin and one for the coverage build. This is something I want to avoid. 
  
  What is the reason that your reference build does not contain valid results?
  

When this is generalized, then we might need multiple reference builds, one for the warnings plugin and one for the coverage build. This is something I want to avoid.

What is the reason that your reference build does not contain valid results?

[jenkins-infra-bot]

stefan6419846:

• Original comment link
• Raw content of original comment:

  Coverage collection and reporting is an optional pipeline parameter in our case as the impact on the execution speed is quite huge for some projects. Whenever this parameter is disabled, we skip recordCoverage completely and thus get "invalid" reference builds.
  

Coverage collection and reporting is an optional pipeline parameter in our case as the impact on the execution speed is quite huge for some projects. Whenever this parameter is disabled, we skip recordCoverage completely and thus get "invalid" reference builds.