How tencent/codeanalysis works
Project type and purpose
• This is a full-stack, microservice-based code analysis and issue-tracking platform (“Tencent Cloud Code Analysis” a.k.a. CodeDog).
• It comprises three logical slices:
• Client (CLI and IDE/Jenkins plugins)
• Server (a collection of Django microservices + Celery workers)
• Web (micro-frontend React apps managed by Lerna)
• Purpose: orchestrate code-analysis tasks (linting, metrics, security) via REST APIs, asynchronous workers, and present results in web UIs or IDE/CI integrations.
File structure
Top level:
• client/ – Python CLI and local-node runner modules
• plugins/ – Jenkins and JetBrains IDE plugins for CI/editor integration
• server/projects/ – multiple Django services:
• analysis/ – code analysis API + Celery tasks
• main/ – core APIs (projects, repos, jobs, users, scan_conf, nodemgr)
• login/ – authentication service
• file/ – file-management service (uploads/downloads)
• scmproxy/ – proxy to external Git/GitHub/GitLab
• web/ – Lerna monorepo of React micro-frontends:
• login, tca-layout, tca-manage (admin), tca-analysis (results), shared, framework, etc.
• helm-charts/ + docker-compose.yml – Kubernetes and Docker deployment descriptors
• Scripts and Dockerfiles for local/docker deployment
Supplementary insights from README
• Emphasis on integration points (APIs, DevOps, external SCM, dynamic tool loading)