Open HeidiRechek2 opened 4 months ago
checks-api:2.2.0 cobertura:1.17 code-coverage-api:4.99.0 coverage:1.14.0 splunk-devops:1.10.1 splunk-devops-extend:1.10.1
Controller OS: Windows Server 2019 - 10.0 Agent OS: OS: Windows Server 2016 - 10.0
Run a build job, which checks for unit coverage level of 70%, fail the job if not met.
When a build job runs, and quality gates the coverage using this plugin, the data for that job should be sent to splunk.
When a build job runs, and quality gates the coverage using this plugin, the data for that job DOES NOT sent the type completed event to splunk.
discovered by missing data and removing pipeline stages/commands to find which one impacted the event getting to Splunk.
No response
Jenkins and plugins versions report
Jenkins: 2.440.3 OS: Windows Server 2019 - 10.0 Java: 17.0.9 - Azul Systems, Inc. (OpenJDK 64-Bit Server VM)
checks-api:2.2.0 cobertura:1.17 code-coverage-api:4.99.0 coverage:1.14.0 splunk-devops:1.10.1 splunk-devops-extend:1.10.1
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller OS: Windows Server 2019 - 10.0 Agent OS: OS: Windows Server 2016 - 10.0
Reproduction steps
Expected Results
Run a build job, which checks for unit coverage level of 70%, fail the job if not met.
When a build job runs, and quality gates the coverage using this plugin, the data for that job should be sent to splunk.
Actual Results
When a build job runs, and quality gates the coverage using this plugin, the data for that job DOES NOT sent the type completed event to splunk.
Anything else?
discovered by missing data and removing pipeline stages/commands to find which one impacted the event getting to Splunk.
Are you interested in contributing a fix?
No response