Closed brostk closed 1 month ago
116 tests ±0 116 :white_check_mark: ±0 36s :stopwatch: -1s 34 suites ±0 0 :zzz: ±0 34 files ±0 0 :x: ±0
Results for commit a0a53a18. ± Comparison against base commit 4f396adc.
:recycle: This comment has been updated with latest results.
Overall Project | 67.56% | :x: |
---|
There is no coverage information present for the Files changed
What was the problem?
Scheduled SecRel runs did are not performing scans because images have already been built during the previous PR merge.
Associated tickets or Slack threads:
3224
How does this fix it?[^1]
In the action script, when we find an image which has already been updated, for scheduled runs we will still add the image name and tag to the output list of images used further down the SecRel pipeline.
How to test this PR
[^1]: Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. [^secrel]: To check if a PR will succeed in the SecRel workflow, test PRs in the SecRel pipeline.