-
Notifications
You must be signed in to change notification settings - Fork 590
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
detectExecuteScan always scans in RAPID mode on PR builds #4719
Comments
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
@SAP/jenkins-library-team |
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
still open |
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
@SAP/jenkins-library-team |
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
@SAP/jenkins-library-team |
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
Due to #4211 which contains the addition of
jenkins-library/cmd/detectExecuteScan.go
Lines 459 to 468 in a342f49
a detect scan is always executed in RAPID mode in case of a PR build. There is no way to run a scan in FULL mode through this step anymore since this change.
Setting the mode parameter to
FULL
results in error:Unable to parse raw value 'FULL,RAPID'
, becauseRAPID
is always appendedThis behavior needs to be switchable.
The text was updated successfully, but these errors were encountered: