-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
Description
Context
The functionality provided by the BuildCheck module is increasing, hence as part of the #10316 we would like to stabilize the behaviour by running the tests (manual) and fixing bugs if appeared during the effort.
Goal
- Validate that documentation of BuildCheck is aligned with actual implementation.
- Validate that MSBuild with enabled BuildCheck runs successfully on Dotnet Repositories ( MSBuild including )
Part 1
Steps:
- Prepare repro project and validate/confirm that the documentation and actual implementation (main branch) are aligned
- In case of finding a bug: Check if it is not reported already if not then please report it :) with the label "Area: BuildCheck"
- In case something is not clear in Documentation that is also an issue, please report it.
Categories/Scope/How to s
-
Inbox (built-in) analyzers that run during the build execution.
-
Custom Analyzers
- Person to contact: YuliiaKovalova
- How to:
- Scope: Prepare simple build check and integrate it into the solution.
-
Configuration
- Person to contact: f-alizada
- How to:
- Scope:
- Enablment of the rules is configurble and its severity
- Specification of .editorconfig will be observed
-
Tracing
- Person to contact: maridematte
- How to:
-v:dand times should be at the end of logs - Scope:
- Opt-in reporting of time spent via specific analyzers and infra overall.
-
Replay mode
- Person to contact: surayya-MS
- How to: https://aka.ms/BuildCheck#binlog-replay-mode
- Scope: https://aka.ms/BuildCheck#binlog-replay-mode
Part 2
This part contains only of running the MSBuild on existing project with BuildCheck enabled.
Steps:
- Choose repository in dotnet
- Run the MSBuild with BuildCheck enabled on selected repository