-
Bug
-
Resolution: Not A Defect
-
Major
-
org.jenkins-ci.plugins:claim:2.5
org.jenkins-ci.main:jenkins-war:1.584
If I claim a failed test in the latest build (say #128), this claim gets lost as soon as the next build (say #129) finishes.
The expected behaviour is, that the claim remains (in #128) and - if the "Sticky" checkbox was selected - a claim gets created for the same test in the new build (#129), if it still fails.
I'm willing to help with the fix because this would be a very useful feature for our team if it worked as expected.
- is related to
-
JENKINS-12437 "Sticky" Checkbox to Claim Failed Builds Following the Current One
-
- Resolved
-
-
JENKINS-30413 Failed test age is incorrect if same test name exist in different package
-
- Resolved
-
Apparently we are also affected by this problem, even though we are currently using a newer version of the plugin (2.13) and Jenkins (2.19.4). The claim gets lost in the subsequent build even if the option "sticky" is selected. The problem does not show up in every job, but rather only in some.
We are using the claim plugin inside scripted pipeline.