jenkinsci / jenkinsci/junit-plugin

[JENKINS-25340] lost trend history after skipping build

Open
#969 40 comments 0 reactions 0 assignees View on GitHub
component:junit-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
87
Forks
351
Avg merge
1d 19h
Merged PRs (30d)
2

Description

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

---
Originally reported by integer, imported from: lost trend history after skipping build


  • status: Reopened
  • priority: Major
  • component(s): junit-plugin
  • resolution: Unresolved
  • votes: 30
  • watchers: 31
  • imported: 2025-11-26

Raw content of original issue

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

environment

```
core: 1.565.3 LTS

plugin: 0.6.0
```

Contributor guide

Open the contributing guide

Research direction

The payload names no source file or test. Start by reproducing the scenario in jenkinsci/junit-plugin with core 1.565.3 and plugin 0.6.0: run a job, abort two builds, and inspect the trend graph. Done means earlier trend history remains visible after aborted builds and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.