VLourenco705176 (Community Member) asked a question.
how to use policy scan in a squash environment (multiple commits on main/master branch)
hi community,
I have a git environment, where we make multiple commits on the main/master branch.
This causes a problem that I cannot run multiple policy scans or queue policy scans.
What strategies do you use in this squash environment on main/master branches?
for the other branches I use the pipeline scan without problems.
however I need the policy scan in a branch that reflects the current state of production, however as mentioned above, I have multiple commits in the main/master branch and with that I have the problem of concurrency of policy scans.
thanks
.png){kind=logo}
Pipeline scan is probably your best bet in this use case with a nightly build pushing to policy. Additionally, developers should be scanning locally before pushing any code to the repo. Anything flagged in a local scan should be addressed and any false positives should have code comments detailing why it is a false positive. This comes in handy later in the mitigation process, since the notes are readily available.
You might try using getbuildinfo.do to check the status of the latest scan, then sleep for 2 minutes before resuming, if you are queueing builds in gitlab.