MVC Ideas for Pipeline Timing Data Test

Overview

This issue is to narrow down an approach to test the idea of the epic within some constraints. That test will be building to learn so we will likely "throw away" the feature for a proper implementation.

What do we want to learn?

1. Do customers interact with duration data for individual jobs/pipelines? (Primary Objective)
   • What drove customers to interact with the data?
   • What were they looking to learn?
   • Did they accomplish their task?
   • What else do they want from the feature?
2. What else would a customer want us to work on instead? (Secondary Objective)
   • Are there other problems the customer looking at this has that are more accute?

Why do we want to learn this?

1. We want to start towards our larger direction with a small but functional step to validate we're going the right way.
   • We have several open epics and issues to display pipeline data.
     • Present information around pipeline performance... (&5071 - closed)
     • CI/CD Observability with Open Telemetry/OpsTel ... (&7386 - closed)
     • CI/CD Reporting & Analytics improvements (&358 - closed)
     • Vintage Epic: Pipeline analytics and observability (&4915 - closed)
   • We have conducted many interviews and customers say they want this.

What constraints should we put on the MVC?

1. It can be built in 1 milestone by 1 developer.
2. It makes use of Job/Pipeline/Other data already available to the front end.
3. It is behind a FF so we can turn it off within 60 days of launch.
4. The feature must record data so we can track unique user usage.

What could we do?

These issues are in no particular order and are not the full list. The idea is to get ideas out there to discuss, we may come up with a new idea for the test.

• Metrics for pipeline jobs (#5228)
• CI Charts: Display Pipeline Running Time (#20833)
• Track the failure rate for a project's pipeline (#323101 - closed)
• MVC: Consider adding the duration of each job i... (#24272)
• Display the duration of each stage on the pipel... (#29439)

How will we decide?

1. Create a comment for an idea of what to build including how each constraint is addressed
2. Tag any engineers on grouppipeline execution you think should weigh in on the proposal
3. Give the comment a 👍
4. Give a 👍 to any other ideas you like
5. If you think the issue cannot fit within a constraint give it a 👎
6. The PM is the DRI on picking amongst the ideas we've validated we CAN build within the constraints.

When will we decide?

1. Issue circulated on May 17/18
2. Team has until May 24th to add comments
3. On May 25th DRI will confirm ideas with most 👍 are buildable/fit within constraints and decide / create issue.

When will we build it?

The target would be %15.2

Summary

Adding a pipeline insights button to the pipeline details page was the winning idea/fit the constraints. #363512 (closed) was created for design/implementation in %15.2 to be measured over 2 months.