Closed brostk closed 1 week ago
116 tests ±0 116 :white_check_mark: ±0 35s :stopwatch: -2s 34 suites ±0 0 :zzz: ±0 34 files ±0 0 :x: ±0
Results for commit a01140d5. ± Comparison against base commit 3db173de.
Overall Project | 67.7% | :x: |
---|
There is no coverage information present for the Files changed
What was the problem?
Scheduled SecRel runs are failing due to missing the container image names set to be signed and published.
Associated tickets or Slack threads:
3031
How does this fix it?[^1]
PUBLISH_IMAGES and RUN_SECREL flags are now being set from the gate check due to having added a condition to an if/else block which previously did not support "schedule" event types.
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.