[JENKINS-36629] Use the run map to optimize calculating recent build health

If we use the run map and its index we can reduce the number of build required to be checked from 5 to 2 in the event that there are no recent failed builds.

Originally reported by stephenconnolly, imported from: Use the run map to optimize calculating recent build health

assignee: stephenconnolly
status: Closed
priority: Minor
component(s): core
label(s): health, lazy-loading, performance
resolution: Fixed
resolved: 2016-07-19T11:07:38+00:00
votes: 0
watchers: 3
imported: 2025-11-24

Raw content of original issue

If we use the run map and its index we can reduce the number of build required to be checked from 5 to 2 in the event that there are no recent failed builds.

Remote links associated with this issue:
- PR 2451
- CloudBees Internal OSS-939

saucistophe:

Original comment link

Raw content of original comment:

stephenconnolly : Still shown as In Progress, while it's in the latest changelog; is it ok?

stephenconnolly:

Original comment link
Raw content of original comment:
```
sorry forgot to mark issue as resolved
```

sorry forgot to mark issue as resolved

[Original relates_to from Jira: JENKINS-25075]

[Original relates_to from Jira: JENKINS-25078]

Navigation Menu

Repository navigation

[JENKINS-36629] Use the run map to optimize calculating recent build health #17326

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[JENKINS-36629] Use the run map to optimize calculating recent build health #17326

Description

Activity

jenkins-infra-bot commented on Jul 12, 2016

jenkins-infra-bot commented on Jul 19, 2016

jenkins-infra-bot commented on Jul 19, 2016

jenkins-infra-bot commented on Nov 24, 2025

jenkins-infra-bot commented on Nov 24, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions