You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Single build has multiple evaluation phases and extra execution phase to facilitate Restore. Running analyzers during those would be superflous - unnecessary perf burden, plus producing duplicite reports.
There might be cases where analysis during Restore is acutaly wanted - but let's skip such cases for now.
Let's somehow detect that current evaluation/execution is for Restore and defunct analyzers infra during that (or alternatively - let's detect it's for Build and enable only during that).
The detection will probably be needed in 2 places - first in the connector logger (for the analyzers getting data from BuildEventArgs) and in RequestBuilder - for analyzers getting data directly in the evaluating/executing node (this second place is not yet mounted in current analyzers prototype code - so can be skipped now).
JanKrivanek
changed the title
Detect restore (evaluation and execution) and skip it (but probably not if it's the only target and analysis explicitly requested?)
Detect and skip restore (evaluation and execution)
Feb 15, 2024
JanKrivanek
changed the title
Detect and skip restore (evaluation and execution)
Analyzers prototyping - Detect and skip restore (evaluation and execution)
Feb 15, 2024
Context
#9627
Single build has multiple evaluation phases and extra execution phase to facilitate Restore. Running analyzers during those would be superflous - unnecessary perf burden, plus producing duplicite reports.
There might be cases where analysis during Restore is acutaly wanted - but let's skip such cases for now.
Let's somehow detect that current evaluation/execution is for Restore and defunct analyzers infra during that (or alternatively - let's detect it's for Build and enable only during that).
The detection will probably be needed in 2 places - first in the connector logger (for the analyzers getting data from BuildEventArgs) and in RequestBuilder - for analyzers getting data directly in the evaluating/executing node (this second place is not yet mounted in current analyzers prototype code - so can be skipped now).
Work in this context:
The text was updated successfully, but these errors were encountered: