Repository navigation
Conversation
POD-10503: adding security scans
…sult POD-10502: Respect TruffleHog scan results in build
POD-11318/jenkins
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
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.
WHAT
Removes the blank line before
#!/usr/bin/env groovyin the Jenkinsfile.WHY
Jenkins only accepts a shebang on line 1. With the leading blank line the pipeline
failed to compile (
unexpected char: '#'at line 2), so no CI ran for this repo,including the TruffleHog secret scan required by POD-11741.
RISK
Low. One-line whitespace change; no build logic changes. The repo keeps
securityScanOnly = trueand theaws-linuxdocker-testnode.TESTING
aws-linuxdocker-test.--results=verified,unknown,unverified --fail, scanned 330 chunks, 0 verified / 0 unverified findings.No
.trufflehog-known-findingsneeded.