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

BuildChecks Dogfooding: Collect info from sample repos #10726

Open
Tracked by #10548
JanKrivanek opened this issue Sep 30, 2024 · 0 comments
Open
Tracked by #10548

BuildChecks Dogfooding: Collect info from sample repos #10726

JanKrivanek opened this issue Sep 30, 2024 · 0 comments
Assignees
Labels
Area: BuildCheck Cost:M Work that requires one engineer up to 2 weeks Priority:2 Work that is important, but not critical for the release triaged

Comments

@JanKrivanek
Copy link
Member

Context

As part of #10548 we want to invest into dogfooding of buildchecks.
As a first step towards it - we need to proactively run and collect issues and perf impact on some sample repos.

Goals

  • Prepare a list of sample repos - ideally 3 bigger ones (e.g. msbuild, roslyn, runtime) and 3 average ones (e.g. templating, debugger-contracts, crank)
  • Run build on those on a choosed version - make sure those are clean of errors. Collect 'wall clock time' perf stats for builds
  • Run the same builds on same versions of the repos with buildcheck opted in (/check)
    • Collect and log the issues
    • Collect the perfstats
  • Evaluate the perf impact and the blocking issues
@JanKrivanek JanKrivanek added Cost:M Work that requires one engineer up to 2 weeks Area: BuildCheck labels Sep 30, 2024
@JanKrivanek JanKrivanek changed the title BuildChecks Dogfooding: Collect infor from sample repos BuildChecks Dogfooding: Collect info from sample repos Sep 30, 2024
@AR-May AR-May added Priority:2 Work that is important, but not critical for the release triaged labels Oct 1, 2024
@YuliiaKovalova YuliiaKovalova self-assigned this Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: BuildCheck Cost:M Work that requires one engineer up to 2 weeks Priority:2 Work that is important, but not critical for the release triaged
Projects
None yet
Development

No branches or pull requests

3 participants