Qodana Incremental Cache Behavior During Parallel CI Job Execution

Determine whether Qodana’s incremental analysis cache remains consistent when two or more scans run concurrently on the same repository, a scenario common in CI pipelines that trigger parallel jobs.

The documentation describes the cache as a performance optimization but does not specify locking or isolation mechanisms for simultaneous access. Observed latency may vary, and without explicit synchronization, cache files could be overwritten or read while being written, potentially leading to stale issue reports or unnecessary cache misses.

• Does Qodana create lock files or use file‑system locking to protect the incremental cache during concurrent access?
• If no locking is employed, can overlapping writes corrupt cache entries and cause scans to miss newly introduced issues?
• What observable signs (e.g., increased cache‑miss rate, divergent issue sets between parallel jobs) indicate that the cache has been affected by concurrent scans?