-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Violations support for JAS scanners #241
Draft
eranturgeman
wants to merge
99
commits into
jfrog:dev
Choose a base branch
from
eranturgeman:jas-violations-support
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+4,918
−3,773
Conversation
This file contains 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
…dded the new parsed violations results to ApplicabilityScanManager.
…ew parsed violations results to IacScanManager.
…new parsed violations results to SastScanManager.
…e new parsed violations results to SecretScanManager.
…ded relevant logs
…methods for hte new struct
eranturgeman
requested a deployment
to
frogbot
November 19, 2024 10:47 — with
GitHub Actions
Waiting
…o jas-violations-support
eranturgeman
requested a deployment
to
frogbot
November 19, 2024 10:48 — with
GitHub Actions
Waiting
…canner cannot incur violations
…y commented at this point)
…o delete comments in results.go)
…rseCommandResults related to jas violations
…esults) + changed the names for Sca parsing methods
…all relevant references
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 3, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 3, 2024
eranturgeman
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 4, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 4, 2024
…o catch this kind of error sooned in the stack
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 11, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
dev
branch.go vet ./...
.go fmt ./...
.Depends on: