Repository navigation
Re-enable ZAP-advanced CI tests #963
Description
We currently have the ZAP Advanced scans disabled in CI because they run too long. We would like to get them working again. One proposal is:
- Run them in the CI if files related to ZAP-Advanced have changed (but not otherwise), and
- run them in a nightly build to test them against (merged) changes to operator, SDK, etc.
Other options can also be viable and are left at the discretion of the person implementing this.
Reacted by Sven Strittmatter
Activity
RamiSouai commentedon Feb 21, 2022
Running the tests only in a nightly build is pretty straightforward (See #986). However, having the test conditionally trigger based on changed files isn't as simple.
The on:push:path directive can only apply to entire workflows, not individual jobs. The only mechanism to conditionally trigger jobs is jobs.<job_id>.if and AFAIK, there is no way to access the modified files in a commit throught Contexts
We could created another zap-advanced-tests.yml workflow that triggers just for changes in zap-adavanced files. But this would over-complicate the pipeline