CI environment variables
Configure Semgrep in CI by setting various environment variables. Enable diff-aware scanning, connect to Semgrep Cloud Platform, and more.
Configure Semgrep in CI by setting various environment variables. Enable diff-aware scanning, connect to Semgrep Cloud Platform, and more.
Collect logs from GitHub Actions to troubleshoot Semgrep CI scans.
Configure how Semgrep in CI pipelines handles errors and blocks findings.
When running Semgrep in CI with a pull or merge request as the triggering event, Semgrep runs some additional git commands to determine the behavior for the scan. The scan exits with an error if these commands fail. A message like the following shows in the output:
Collect verbose logs from GitLab to troubleshoot Semgrep CI scans.
How to test scans with different versions of Semgrep.
Packages included in the latest Semgrep docker image.
Set additional environment variables to receive Semgrep MR comments through a GitLab runner.
View sample configuration files to run Semgrep with various CI/CD providers such as GitHub, GitLab, Jenkins, Buildkite, CircleCI, and more.
How to scan a monorepo in parts for better CI performance and clearer findings organization
Learn how to set up the Semgrep Network Broker, which facilitates secure access between Semgrep and your private network.
Get more information when Semgrep in CI hangs, crashes, times out, or runs too slow. Fix issues with GitLab SAST's Semgrep analyzer, such as jobs running slowly, not showing results, or returning errors.