• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • junit-plugin
    • None
    • core: 1.565.3 LTS
      plugin: 0.6.0

      I had trend history, then aborted two builds (run job and press abort), after it trend history graph become clear.
      After 2 builds graph filled back with 2 results (but before abort results still doesn't appeared).

          [JENKINS-25340] lost trend history after skipping build

          Kanstantsin Shautsou created issue -

          James Nord added a comment -

          James Nord added a comment - hardly suprising... https://github.com/jenkinsci/jenkins/commit/8d8102036f4e52aada39db37c05025b9bb31516d
          James Nord made changes -
          Assignee Original: James Nord [ teilo ] New: Jesse Glick [ jglick ]
          James Nord made changes -
          Component/s New: junit-plugin [ 15499 ]
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-23945 [ JENKINS-23945 ]

          Jesse Glick added a comment -

          Yup. No plans to fix until core provides a safer way of looking for builds by number.

          Jesse Glick added a comment - Yup. No plans to fix until core provides a safer way of looking for builds by number.
          Jesse Glick made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          This is blocker for me. I'm limiting number of jobs to what i want see in trend - it's near 30, not sure what performance issues it may cause and what you want expect from core. Also we can't use Jenkins test results now.

          Do you have core issue that maybe linked to this issue?

          Kanstantsin Shautsou added a comment - This is blocker for me. I'm limiting number of jobs to what i want see in trend - it's near 30, not sure what performance issues it may cause and what you want expect from core. Also we can't use Jenkins test results now. Do you have core issue that maybe linked to this issue?
          Kanstantsin Shautsou made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          James Nord added a comment -

          the code that is broken in core (in 1.565) no longer lives in core - it now lives in the junit plugin.

          James Nord added a comment - the code that is broken in core (in 1.565) no longer lives in core - it now lives in the junit plugin.

            Unassigned Unassigned
            integer Kanstantsin Shautsou
            Votes:
            30 Vote for this issue
            Watchers:
            31 Start watching this issue

              Created:
              Updated: