Static Code Analysis
Static code analysis involves examining program source code through techniques such as lexical analysis, syntactic analysis, control flow, and data flow analysis without actually running the program. It verifies whether the code meets standards for compliance, security, reliability, and maintainability.
Analysis Scheme
An analysis scheme, also referred to as an analysis policy or analysis configuration scheme, distributes corresponding configuration information to execute code analysis when an analysis project initiates.
Analysis Project
An analysis project is the smallest unit for performing analysis. Currently, there are three types of analysis projects: code repository analysis projects, source code package analysis projects, and artifact repository analysis projects.
A code repository analysis project = code repository branch + analysis path + analysis scheme
A source code package analysis project = source code package version + analysis scheme
An artifact repository analysis project = artifact name + analysis scheme
Analysis Node
Analysis nodes are used to execute specific analysis tasks. When a user initiates an analysis task, it is allocated to the corresponding node for execution based on the analysis configuration. TCA adopts a distributed client architecture, allowing clients to be flexibly deployed to any region (provided they can access the TCA platform), such as being used as one-time temporary nodes or resident nodes.
Issue Owner
git blame: responsible party, typically the committer of the corresponding problematic line.