Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12437

"Sticky" Checkbox to Claim Failed Builds Following the Current One

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: claim-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            trejkaz trejkaz added a comment -

            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.

            Show
            trejkaz trejkaz added a comment - 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.
            Hide
            msa 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.

            Show
            msa 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.
            Hide
            drekbour Marc Carter added a comment -

            [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.

            Show
            drekbour Marc Carter added a comment - [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.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Arnaud
            Path:
            src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java
            src/main/java/hudson/plugins/claim/ClaimBuildAction.java
            src/main/java/hudson/plugins/claim/ClaimConfig.java
            src/main/java/hudson/plugins/claim/ClaimTestAction.java
            src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly
            src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.properties
            src/main/resources/hudson/plugins/claim/ClaimConfig/config.jelly
            src/main/resources/hudson/plugins/claim/ClaimConfig/config.properties
            src/main/webapp/help-propagateToFollowingBuilds.html
            src/main/webapp/help-propagateToFollowingBuildsByDefault.html
            src/test/java/hudson/plugins/claim/ClaimGroovyTest.java
            src/test/java/hudson/plugins/claim/ClaimTest.java
            src/test/java/hudson/plugins/claim/utils/TestBuilder.java
            http://jenkins-ci.org/commit/claim-plugin/88160fc8f6ceef218aae4cea87e78d228e2ddca8
            Log:
            JENKINS-12437 Allow propagating claims to following failed builds

            Compare: https://github.com/jenkinsci/claim-plugin/compare/78a4e5ddaa84...88160fc8f6ce

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Arnaud Path: src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimConfig.java src/main/java/hudson/plugins/claim/ClaimTestAction.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.properties src/main/resources/hudson/plugins/claim/ClaimConfig/config.jelly src/main/resources/hudson/plugins/claim/ClaimConfig/config.properties src/main/webapp/help-propagateToFollowingBuilds.html src/main/webapp/help-propagateToFollowingBuildsByDefault.html src/test/java/hudson/plugins/claim/ClaimGroovyTest.java src/test/java/hudson/plugins/claim/ClaimTest.java src/test/java/hudson/plugins/claim/utils/TestBuilder.java http://jenkins-ci.org/commit/claim-plugin/88160fc8f6ceef218aae4cea87e78d228e2ddca8 Log: JENKINS-12437 Allow propagating claims to following failed builds Compare: https://github.com/jenkinsci/claim-plugin/compare/78a4e5ddaa84...88160fc8f6ce
            Hide
            greybird Arnaud TAMAILLON added a comment -

            fixed in 2.13

            Show
            greybird Arnaud TAMAILLON added a comment - fixed in 2.13

              People

              Assignee:
              greybird Arnaud TAMAILLON
              Reporter:
              starryknight64 Phillip Ponzer
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: