• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • claim-plugin
    • None
    • Jenkins 2.346.1
      xUnit plugin Version3.1.0
      xUnit Categories Extension plugin Version1.1
      Claim Version2.18.2

      Considering an run that is facing an issue (run over the timeout threshold for example), we are facing the below issue for the unit test foo : 

      • Run 0 : Test foo Passed
      • Run 1 : Test foo failing, Age 1 claimed to Bob
      • Run 2 : Test foo failing, age 2, claimed to Bob
      • Run 3 : Test foo failing, age 3, claimed to Bob
      • Run 4 : Run over the threshold (10mins), unit test foo has not beed played, no claim stored
      • Run 5 : Test foo failing, age 1 unclaimed
      • Run 6 : test foo failing age 2

      We wrongly believe that the run 5 has unclaimed unit test.

      I believe we should display the claim of the previous run

      This would requiere a paradigm shift : When a run is aborted and a status is different then Pass, we go through the previous run 

          [JENKINS-69429] Claim should not be reset on aborted run

          florian gouze added a comment -

          We did not manage to do any workaround with sticky version that doest not seem to work but it's another ticket not related to the improvement as it should be done regardless of the sticky part

          florian gouze added a comment - We did not manage to do any workaround with sticky version that doest not seem to work but it's another ticket not related to the improvement as it should be done regardless of the sticky part

            greybird Arnaud TAMAILLON
            fgouze080321 florian gouze
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: