Cross-Project Metrics For An Orb's Jobs
When orbs contain a job that is used in multiple repositories, it would be helpful if insights included aggregate metrics and test insights for the job cross-project. This would allow for easier detection of cross-project flaky tests and other potential issues.
Date Range Customization
I would like the ability to customize the date ranges for your insights tab. Essentially, the week, 30 day, 60, and 90 day options can be limiting.
Remove "All Branches" when viewing branch-specific metrics
When viewing insights for a particular selected branch or branches, insights for "All Branches" are still viewable. Allow users to remove these insights so that they can only view branch-specific insights.
Allow a workflow to be considered successful even without approvals
In some cases, approval gates are used for rollbacks or circumstantial deployments. As an option, if all jobs prior to the approval are successful, then the workflow should be considered successful.
Datadog metrics by branch
I'd like to show circleci job times and success rates filtered to just an individual branch. The new circleci insights pages are great, but we show these metrics alongside other code quality measures. Currently, it's not possible to filter by branch, which makes it hard to see if master is failing frequently or if it's only dev branches.
Search among most failed tests in insights
Hi, As a user, I recently saw a test suite failing in my nightly run and I'd like to know if this test has been failing before. So I'd like to search through the most failed test to find a specific test suite. It'd be nice to have the same feature on the slowest tests as well.
git clone --recursive https://github.com/dnSpy/dnSpy.git cd dnSpy # or dotnet build ./build.ps1 -NoMsbuild
Add When Test Became Flaky And Timeframes To Insights
It would be helpful if the flaky test information in Insights also included: A link to when the test first became flaky The ability to see flaky test information from a customized time period
Warning Status Code
My team is integrating performance metrics into the build and we would like the ability to have a job with a status of warning that turns yellow instead of just having the success/fail statuses so that we can warn developers when performance metrics are getting close to thresholds.