Fix sonarqube analysis #95
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| BUILD_WRAPPER_OUTPUT="${{ env.BUILD_WRAPPER_OUT_DIR }}bw-output" | ||
| if [ -d "$BUILD_WRAPPER_OUTPUT" ] && [ -f "$BUILD_WRAPPER_OUTPUT/build-wrapper-output.json" ]; then | ||
| echo "Build-wrapper output found at: $BUILD_WRAPPER_OUTPUT" | ||
| ls -la "$BUILD_WRAPPER_OUTPUT" | head -5 |
There was a problem hiding this comment.
The new SonarCloud logic sets BUILD_WRAPPER_OUTPUT="${{ env.BUILD_WRAPPER_OUT_DIR }}bw-output" and looks for build-wrapper-output.json, but the earlier build-wrapper invocation uses --out-dir ${{ env.BUILD_WRAPPER_OUT_DIR }} (which is ./) and produces build-wrapper-dump.json directly in the repository root. Because no bw-output directory or build-wrapper-output.json file is created, this condition always fails and sonar.cfamily.build-wrapper-output is never passed to sonar-scanner, even though C/C++ analysis has been re-enabled. The scan will still error out or skip C++ files. Point the check (and subsequent parameter) at the actual output directory/file or adjust the build-wrapper invocation to write to the expected location.
Useful? React with 👍 / 👎.
Summary
Technical Details
✨ Features
🐛 Bugfixes