Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2. Evaluate Findings #2920

Open
codecovdesign opened this issue Nov 14, 2024 · 2 comments
Open

2. Evaluate Findings #2920

codecovdesign opened this issue Nov 14, 2024 · 2 comments

Comments

@codecovdesign
Copy link
Contributor

codecovdesign commented Nov 14, 2024

<based on results from 1.a 1.b from 2702; eng/design/pm teams to evaluate findings and determine next steps>

  • Based on investigation results, the Eng/Design/PM team will assess next steps, such as showing an intermediary state, adjusting configuration defaults, or other potential improvements.
  • Consider a more standardized approach to report processing, potentially deprecating after_n_builds or setting default behavior without configuration. This will depend heavily on investigation outcomes.
@codecovdesign
Copy link
Contributor Author

WIP:

  • PR comment updates
  • App updates
  • Unresolved: end state (report finalized)

@codecovdesign
Copy link
Contributor Author

codecovdesign commented Jan 6, 2025

review with @Adal3n3 @eliatcodecov @rohan-at-sentry @aj-codecov

  • overview where we landed (platform/pr-comment and application/ui)
  • the part that is unknown is providing feedback to user when they have a completed report
    • rohan: question for the room, how would we feel about leaving this at the latest iterations
    • kyle: how this works is tbd, but feels like a big step forward in terms of giving user feedback. nevertheless a bit more investigation toward end-state would be helpful
    • eli: been a tough problem for years, but we've continued to push it a bit without terrible implications. suggest shipping this and seeing how it lands on support side. probably plan to keep moving on solving this, we don't necessarily need a step 2
    • adalene: some issue with dashboard data, therefore the latest commit presenting partial data as it's related to the processing state
      - rohan: other things to look at is suggesting after_n_builds. eli: issue is it's not just after_n_builds doesn't resolve everything, but it could help for a lot
      - @codecovdesign ToDo: create issue around this for discovery (suggestion to update yaml)

Summary: will review the feedback/outcomes from existing iterations. we can revisit further investigation in future quarters, per team sentiment / user feedback. todo discovery on improving leverage of after_n_builds to resolve/help this issue for most customers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant