2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
Hello, there are a few things I would ask you to check:
- Check the ESLint configuration file (typically
.eslintrc
file) and make sure the rules and severity levels are set up correctly. The rule corresponding to the finding may have been set to warn instead of error. - Check if there are any suppression comments added next to the lines triggering the finding. Suppression comments like
/* eslint-disable */
can ignore rule violations on certain lines. - Check if there are any global suppression rules defined that may be overriding the severity of the finding. The AWS documentation mentions you can define suppression rules to ignore certain findings.
- Ensure the ESLint plugin or library being used supports failing on certain severity levels. Some may not fail the build or analysis even if high severity issues are found.
- Check the CLI command or configuration used to run ESLint. Options like
--max-warnings
could be preventing it from failing on warnings.
-1
You will need to configure the success criteria from the workflow YAML to fail the report. Please follow this link.
respondido hace 2 meses
It is already configured, that's why the text circled in red shows 0 findings as maximun
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
- OFICIAL DE AWSActualizada hace 2 años
As you can see in the screen shot. There is one finding in that report. The finding severity is HIGH The success criteria is set to 0 findings with Low and above.
The report should FAIL, but is not