fix: run sonar:sonar in same reactor as verify
Running mvn sonar:sonar as a separate invocation skips child modules. Combining verify and sonar:sonar in a single mvn command ensures the reactor processes all modules. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -42,9 +42,6 @@ jobs:
|
||||
key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
|
||||
restore-keys: ${{ runner.os }}-maven-
|
||||
|
||||
- name: Build and Test Java
|
||||
run: mvn clean verify -DskipITs -U --batch-mode
|
||||
|
||||
- name: Install UI dependencies
|
||||
working-directory: ui
|
||||
run: |
|
||||
@@ -57,9 +54,9 @@ jobs:
|
||||
working-directory: ui
|
||||
run: npm run lint -- --format json --output-file eslint-report.json || true
|
||||
|
||||
- name: SonarQube Analysis
|
||||
- name: Build, Test and Analyze
|
||||
run: |
|
||||
mvn sonar:sonar --batch-mode \
|
||||
mvn clean verify sonar:sonar -DskipITs -U --batch-mode \
|
||||
-Dsonar.host.url=${{ secrets.SONAR_HOST_URL }} \
|
||||
-Dsonar.token=${{ secrets.SONAR_TOKEN }} \
|
||||
-Dsonar.projectKey=cameleer3-server \
|
||||
|
||||
Reference in New Issue
Block a user