📄️ Running Semgrep using templates in Azure Pipelines
Running Semgrep commands in Azure Pipelines templates.
📄️ Triggering events from Bitbucket to Jenkins
How to trigger events from the Bitbucket server to a Jenkins instance
📄️ Set up Jenkins pipeline projects for Bitbucket repositories
Set up Jenkins pipeline projects for Bitbucket repositories.
📄️ Semgrep in CI vs CLI: align your SAST scan results and understand differences
How to align your scan results between CI and CLI and understand differences in behavior.
📄️ Collecting Semgrep GitHub Actions logs from GitHub
Collect logs from GitHub Actions to troubleshoot Semgrep CI scans.
📄️ GitLab "Job's log exceeded limit" error
Collect verbose logs from GitLab to troubleshoot Semgrep CI scans.
📄️ Failed to run a git command during a pull or merge request scan
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:
📄️ Use GitHub repository rulesets to implement Semgrep
Set up GitHub required workflows to efficiently implement Semgrep scans across many repositories.
📄️ Set up reusable GitHub workflows for Semgrep scans
Learn how to set up reusable GitHub workflows for Semgrep scans.
📄️ Why aren't findings populating in the GitHub Advanced Security Dashboard after running Semgrep in CI?
To prevent "resource not accessible by integration" error when running job to upload findings to GitHub's Advanced Security Dashboard
📄️ Jenkins shared library with Semgrep scans
Setting up Jenkins shared library with Semgrep scans
📄️ Receive Semgrep MR comments through a GitLab runner
Set additional environment variables to receive Semgrep MR comments through a GitLab runner.
📄️ Scanning a monorepo in parts
How to scan a monorepo in parts for better CI performance and clearer findings organization
📄️ Why are duplicate findings appearing after running Semgrep in CI?
To prevent duplicated findings, perform full scans only on the main branch of your repository.