Skip to content

Bug 2247748: A storage-client CronJob create too many jobs and pods causing maxPod limit to be reached #193

Bug 2247748: A storage-client CronJob create too many jobs and pods causing maxPod limit to be reached

Bug 2247748: A storage-client CronJob create too many jobs and pods causing maxPod limit to be reached #193

Triggered via pull request November 20, 2023 08:41
Status Failure
Total duration 23s
Artifacts

commitlint.yaml

on: pull_request
commitlint
12s
commitlint
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
commitlint
You have commit messages with errors ⧗ input: controllers: added keep failed iterations ⚠ body's lines must not be longer than 72 characters [body-max-line-length] ⚠ found 0 problems, 1 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: insert ConcurrencyPolicy field to CronJob ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ message must be signed off [signed-off-by] ⚠ body may not be empty [body-empty] ✖ found 3 problems, 1 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
commitlint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
commitlint
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/