Repository navigation
Scans are marked as Failed after the First Jobs has failed #238
Description
Current Status
The secureCodeBox Operator marks Scans as "Failed" if the job fails, even when the job gets restarted by Kubernetes and succeeds later.
Expected Behavior
The scan is only marked as "Failed" if the retry limit for the job has been exceeded.
Activity
Weltraumschaf commentedon Jul 26, 2023
This has a merged PR. Is it still valid?
J12934 commentedon Jul 26, 2023
@Weltraumschaf yes still valid.
I think the linked Pr was linked primary linked as they are somewhat related but merging it does not affect this issue.
#238 Changed the condition for failed job to requiring exceding the …
7 remaining items
#238 set backoffLimit to 1 in makefile testing
#238 remove parameter used for testing the backOfflimit parameter fun…
#238 set scanner backoff limit to 1 in deploy-without-scanner makefil…
#238 Changed the condition for failed job to require exceding Backof…
#238 Changed Job failure requirement to equal or more the backofflimit
#238 set backoffLimit to 1 in makefile testing
#238 remove parameter used for testing the backOfflimit parameter fun…
#238 set scanner backoff limit to 1 in deploy-without-scanner makefil…
#238 Changed the condition for failed job to require exceding Backof…
#238 Changed Job failure requirement to equal or more the backofflimit
#238 set backoffLimit to 1 in makefile testing
#238 remove parameter used for testing the backOfflimit parameter fun…
#238 set scanner backoff limit to 1 in deploy-without-scanner makefil…