-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 1.505
Warnings-Plugin 4.32
It seems if there is no reference build the result of build is not set according specified status thresholds.
In configuration of job I have set
| Status thresholds (Totals) | All priorities | Priority high | Priority normal | Priority low |
|---|---|---|---|---|
| yellow | 0 | |||
| red |
and
Compute new warnings (based on reference build)
| Status thresholds (New warnings) | All priorities | Priority high | Priority normal | Priority low |
|---|---|---|---|---|
| yellow | ||||
| red | 0 |
Use delta for new warnings
Currently 782 warnings are found but build result is stable, expected unstable.
Excerpt from console:
[WARNINGS] Parsing warnings in files 'ccg.txt' with parser TTCN3_SCT_VALIDATOR
[WARNINGS] Finding all files that match the pattern ccg.txt
[WARNINGS] Parsing 1 files in /var/fpwork/xxx/jenkins/workspace/job_ccg
[WARNINGS] Successfully parsed file /var/fpwork/xxx/jenkins/workspace/job_ccg/ccg.txt of module with 782 warnings.
[WARNINGS] Skipping warning delta computation since no reference build is found
Please find configuration in attachment (warnings_config.jpg and warnings_config.xml ).
[JENKINS-19614] Result of build not always set correct
Hans-Juergen Hafner
created issue -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 151131 ] | New: JNJira + In-Review [ 206952 ] |