Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion .github/workflows/qodana_code_quality.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,31 @@ jobs:
with:
ref: ${{ github.event.pull_request.head.sha }} # to check out the actual pull request commit, not the merge commit
fetch-depth: 0 # a full history is required for pull request analysis
- name: Set up JDK 25
uses: actions/setup-java@v5
with:
java-version: "25"
distribution: "temurin"
- name: Cache Qodana Maven repository
uses: actions/cache@v5
with:
path: ${{ runner.temp }}/qodana/caches/.m2
key: ${{ runner.os }}-qodana-m2-${{ hashFiles('**/pom.xml') }}
restore-keys: |
${{ runner.os }}-qodana-m2-
Comment on lines +33 to +39

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in eae6368 — disabled the action's built-in caching (use-caches: false, which also makes cache-default-branch-only moot). Its per-SHA keys never restored in the runs we inspected, so the only effect would have been re-uploading the seeded .m2 every run. The explicit pom-keyed actions/cache step is now the sole cache manager.

# Qodana's own Maven import intermittently skips downloading dependencies,
# leaving unresolved library roots that break the sanity check and produce
# bogus findings. Seed the repo it uses (/data/cache/.m2) ourselves.
- name: Warm Maven repository for Qodana
run: mvn -B -P ci -DskipTests dependency:go-offline -Dmaven.repo.local=${{ runner.temp }}/qodana/caches/.m2
- name: "Qodana Scan"
uses: JetBrains/qodana-action@v2026.1
with:
pr-mode: true
cache-default-branch-only: true
# built-in caching never restored (per-SHA keys) and would now
# re-upload the pre-seeded .m2 every run; the explicit
# actions/cache step above manages the Maven repo instead
use-caches: false
args: --fail-threshold,0
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_2097965348 }}
Expand Down
Loading