Historic pipeline duration chart
Description
The speed of continuous integration tests are an important part of reducing cycle time of shipping a feature. Slow CI tests can significantly limit the speed of iteration, even ignoring the cost of context switching while waiting for tests to complete.
For most projects, however, the XP guideline of a ten minute build is perfectly within reason. Most of our modern projects achieve this. It's worth putting in concentrated effort to make it happen, because every minute you reduce off the build time is a minute saved for each developer every time they commit. Since CI demands frequent commits, this adds up to a lot of time.
The current cycle analytics don't provide sufficient information to help us evaluate if the situation is improving or worsening.
Proposal
Add a chart showing daily mean for last X months, so that we can see if we are improving or not.
- API provide historic data
- Rather than daily bar chart it might be better to have an hourly line chart because that would help reveal cyclic patterns during the day that might correspond to business hours.
- Interface: add chart to cycle analytics interface
Links / references
https://gitlab.com/gitlab-org/gitlab-ee/issues/3716
Documentation blurb
Overview
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
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