Conversation
Adds a step to the polaris-scan job that runs pixee/blackduck-polaris-scripts after each Polaris scan, converting SAST findings to SARIF and uploading them to edge.getpixee.com for remediation analysis. Secrets/variables (PIXEE_API_KEY, POLARIS_PROJECT_ID, POLARIS_PORTFOLIO_ID, PIXEE_REPOSITORY_ID) are pre-populated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Auto-generated PR comment (Polaris)❌ Found dependencies violating policy!
|
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
pixee/blackduck-polaris-scripts is internal-visibility. Pass a PAT (PIXEE_SCRIPTS_PAT) embedded in the git URL so the runner can clone it. Accepts the divergence from the customer flow for this sandbox PR. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replaces the cross-repo `uvx --from git+...` clone of pixee/blackduck-polaris-scripts with a checked-in copy under .pixee/polaris-to-sarif/. Mirrors how customers consume the script (emailed bundle, committed to their repo) and removes the PAT requirement. pyproject.toml carries a one-line local fix to the console-script entry point (`polaris_to_sarif:main` -> `polaris_to_sarif:app`), matching pixee/blackduck-polaris-scripts#4. Once that PR merges, the vendored copy can be re-synced to match upstream pristine. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
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
1 participant
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.
Summary
Adds a step to the
polaris-scanjob in.github/workflows/polaris.yamlthat runspixee/blackduck-polaris-scriptsafter each Polaris scan. The script queries the Polaris REST API for SAST findings, converts them to SARIF, and uploads them to Pixee Cloud (https://edge.getpixee.com), triggering remediation analysis.The secrets/variables the new step references (
PIXEE_API_KEY,POLARIS_ACCESS_TOKEN,POLARIS_PROJECT_ID,POLARIS_PORTFOLIO_ID,PIXEE_REPOSITORY_ID) are already populated in this repo's Actions settings.Shape
BRANCHresolves togithub.head_refon PRs andgithub.ref_nameon pushes.uvx --from git+…@main polaris-to-sarifinvokes the script's console-script entry point directly from the upstream repo — no checkout needed. Once stable,@maincan be swapped for a pinned commit SHA or release tag.--polaris-branch-nameand--pixee-branch-nameare the same value: WebGoat branches match 1:1 between Polaris and SCM.--trigger-analysiskicks off Pixee remediation analysis immediately.if: success()prevents the upload from running if the Polaris scan step failed.Test plan
CI-Polarisand the new "Upload Polaris results to Pixee" step prints✓ Successfully uploaded to Pixee!with a Scan ID and Analysis URL.edge.getpixee.comshows SAST findings and remediation analysis starting.🤖 Generated with Claude Code