Quickly find failed
Description
In groups with many projects and different branches it very quickly becomes near impossible to find failed ci jobs.
Proposal
A group overview of failed CI jobs. A single page where all jobs that failed are listed.
Each failed pipeline is listed here, for all branches.
-
A failed pipeline gets removed if the same branch succeeds again (i.e. the error was corrected).
-
A failure can be marked as 'ignored' and will be removed from the board until a new failure on the branch surfaces.
Bous:
- a graph that tracks failures vs. success over time
- pie chart succeeding braches vs. failing branches
Links / references
Documentation blurb
Overview
What is it?
A way to keep an eye on overall group health and quickly identify pain points.
Why should someone use this feature?
Because clocking through 30 projects to see if any of the branches failed is super tidious.
What is the underlying (business) problem?
To deal with large codebases that use multi-branch development strategies.
How do you use this feature?
I click on the 'Failures' menu and see if there is anything that needs my attention or if I can go back to sipping coffee.
Use cases
Who is this for? Provide one or more use cases.
The gitlab org. As it stands now it's near impossible to find all the failing branches.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml