ci(spotbugs): publish one SARIF run per code-scanning category - #681
Merged
Conversation
The weekly SpotBugs job gathered every module's spotbugsSarif.json into one directory and uploaded it under the single category `spotbugs`. Each run names the same SpotBugs tool driver and carried no automation id, so code scanning saw seven runs it could not tell apart in one delivery and refused the upload: "The CodeQL Action does not support uploading multiple SARIF runs with the same category." Stamp each file's runs with the module's own automationDetails.id (`spotbugs/<module>/`) while collecting them, which is what the category input sets and what code scanning keys an analysis on. upload-sarif fills that id in only where none is set, so the per-module ids survive and the category input is no longer needed. The module reports stay in one upload and one job; the findings keep their repository-relative paths, so attribution is unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L3wQdJ9u1p1KkcHM7wfc1n
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The weekly SpotBugs job gathered every module's spotbugsSarif.json into
one directory and uploaded it under the single category
spotbugs. Eachrun names the same SpotBugs tool driver and carried no automation id, so
code scanning saw seven runs it could not tell apart in one delivery and
refused the upload: "The CodeQL Action does not support uploading
multiple SARIF runs with the same category."
Stamp each file's runs with the module's own automationDetails.id
(
spotbugs/<module>/) while collecting them, which is what the categoryinput sets and what code scanning keys an analysis on. upload-sarif fills
that id in only where none is set, so the per-module ids survive and the
category input is no longer needed.
The module reports stay in one upload and one job; the findings keep
their repository-relative paths, so attribution is unchanged.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01L3wQdJ9u1p1KkcHM7wfc1n