-
Improvement
-
Resolution: Fixed
-
Minor
-
None
When claiming a "historic" build with the Sticky flag should also claim all subsequent failed builds (stopping at the next passing build or the latest build).
Basically, assigning a "sticky" claim should be retroactive.
- is related to
-
JENKINS-26136 Claim for failed test disappears when a new build finishes
-
- Closed
-
[JENKINS-12437] "Sticky" Checkbox to Claim Failed Builds Following the Current One
Phillip Ponzer
created issue -
Phillip Ponzer
made changes -
| Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
| Assignee | New: Christian Bremer [ ki82 ] |
Michael Schaufelberger
added a comment - I wish this would work with the test failures. There is a checkbox "Sticky" but even for the test failure I claim directly it seems to forget my claim after a while.
... and I wonder why in the release notes (https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin) the feature "Option to sticky claim test failures if the failure is "similiar"" is struck through.
Michael Schaufelberger
added a comment - I wish this would work with the test failures. There is a checkbox "Sticky" but even for the test failure I claim directly it seems to forget my claim after a while.
... and I wonder why in the release notes ( https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin ) the feature "Option to sticky claim test failures if the failure is "similiar"" is struck through. [slightly reworded Description]
It's fairly common pattern for a dev to look at the first build failure and not the latest one to diagnose an issue. They then Claim it and, as mentioned, it does nothing to help the team.
another common usecase is to open the latest failed build #10, another build #11 runs in the background, then users Claim #10.
| Description | Original: When claiming a build that is a few failed builds back, clicking the "Sticky" checkbox should also claim the failed builds following the build you are currently claiming. |
New:
When claiming a "historic" build with the Sticky flag should also claim all subsequent _failed_ builds (stopping at the next passing build or the latest build). Basically, assigning a "sticky" claim should be retroactive. |
| Workflow | Original: JNJira [ 142803 ] | New: JNJira + In-Review [ 175756 ] |
| Link |
New:
This issue is related to |
| Assignee | Original: Christian Bremer [ ki82 ] | New: Arnaud TAMAILLON [ greybird ] |
I just put in two hours work going through all the tests for the "latest build" and claiming my tests after confirming that they were mine and then after I finished, I went to the latest build and only 3 of them were still claimed. So yes, I think I can agree with this improvement request.