-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Jenkins: 2.452.1
OS: Linux - 4.18.0-553.5.1.el8_10.x86_64
Java: 17.0.11 - Red Hat, Inc. (OpenJDK 64-Bit Server VM)
---
forensics-api:2.4.0
warnings-ng:11.3.0
{{discoverReferenceBuild }}will not update to the latest completed build after being called for the first time.
Scenario:
- Build A is completed
- Build B starts
- Build C starts and calls discoverReferenceJob -> points to A
- Build B publishes some report with the same ID as used in the other jobs
- Build C calls discoverReferenceJob again -> Reference Build switches to B but WarningsNG still uses A.
Behavior before the switch to Forensics API was that Job C's delta would have pointed to Job B as soon as it published the report. Now, even after calling discoverReferenceJob, it doesn't update.
The reference build is correctly set to the latest completed one, but warningsNG sticks with the one found when discoverReferenceBuild was called the first time.
-> Updating WarningsNG breaks some pipeline logic from us.
I am assuming you mean build and not job in your example?
Are you using discoverReferenceBuild multiple times in one build? The action is supposed to be called only once per build.
Can you please add the logging output of the warnings plugin?