Home / Help centre / Troubleshooting
Troubleshooting
Why did my CI job pass even though Cyberlop found critical issues?
The ready-made snippets are non-blocking by design. They print findings to the build log and never fail the job, so a green build says nothing about severity. The log holds the finding list. Or add your own step that fails on the counts.
Why this happens
Each snippet says so in its first line: non-blocking, reports findings, never fails the build. One file sets continue-on-error: true and the other sets allow_failure: true. Cyberlop chose that so a new scan step cannot break a busy pipeline on day one.
How to fix it
- Open the job log and find the Report findings step. It prints the number of findings, then one line each with the severity, the title and the location.
- Look at the build notice that ends the run. It tells you how many issues Cyberlop found.
- Confirm that the wait step finished. It polls every 30 seconds, up to 120 times, so a scan still running at the end can leave the list short or empty. See why a CI job stopped waiting.
- For a quick review outside CI, open Issues in the app and filter by severity.
- To fail the build on severity, add a step to your own copy of the file. Read the result call's severity counts and exit with an error when they pass your limit. The snippet does not do this for you, and the rule is yours to set.
Flipping the failure setting will not help, because it only matters when the job itself exits with an error, and the snippet never takes that step on its own. Nothing in the snippet exits with an error when it finds something, however serious the finding is, so the pipeline stays green on purpose. That is a choice, and you can change it.
Still not working?
Make sure you used the profile you meant, and that the scan appears under Recent Scans. For the polling details, see polling a scan result. Learn about gating a build before you turn on a hard stop. Stuck? Send the job log to us through the contact page.
Related questions
- How do I check a CI-triggered scan's result through the API?
- My CI job stopped waiting before the scan finished. Why?
- My CI job can't trigger a scan. What should I check?
- Can I use Cyberlop with a CI system that has no ready-made snippet?
- What's the difference between scheduled scans and CI-triggered scans?
How to add security scanning to your CI/CD pipeline
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Error still showing?
Send us the exact message and the page you were on. We will reply with the fix.