Bug 2103981

Summary: Topology resource sidebar shows all Builds and should show just the last n
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: low Docs Contact:
Priority: medium    
Version: 4.9CC: nmukherj
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-17 19:51:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
pipelineruns.png
none
builds.png none

Description Christoph Jerolimov 2022-07-05 13:07:38 UTC 
Description of problem:
As a user I want quickly understand the status of my latest Builds in the topology sidebar. But it confuses the user by showing ALL builds instead of just the latest builds.

Version-Release number of selected component (if applicable):
All

How reproducible:
Always

Steps to Reproduce:
1. Import from Git
2. Open the topology sidebar for the new Deployment
3. Push the "Start Build" button 20 times

Actual results:
The user can see all 20 builds.

Expected results:
The user should see just the latest n builds.

For pipelines show just the latest 3 builds in the sidebar. The latest 3, 5, or 10 builds make sense to me. Using the same number of builds then pipelines would be consistent.

Additional info:
Comment 1 Christoph Jerolimov 2022-07-05 13:09:31 UTC 
Created attachment 1894685 [details]
pipelineruns.png
Comment 2 Christoph Jerolimov 2022-07-05 13:10:19 UTC 
Created attachment 1894686 [details]
builds.png
Comment 4 Christoph Jerolimov 2022-07-25 22:56:38 UTC 
Verified on 4.12.0-0.nightly-2022-07-25-122035
Comment 7 errata-xmlrpc 2023-01-17 19:51:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7399