Skip to content

Add --fail-on-violation flag to exit non-zero when violations are detected#392

Open
mbarbero wants to merge 1 commit intoboostsecurityio:mainfrom
mbarbero:add-fail-on-violation
Open

Add --fail-on-violation flag to exit non-zero when violations are detected#392
mbarbero wants to merge 1 commit intoboostsecurityio:mainfrom
mbarbero:add-fail-on-violation

Conversation

@mbarbero
Copy link

@mbarbero mbarbero commented Mar 3, 2026

poutine always exited with code 0 after analysis, even when violations were found, making it unsuitable for use as a blocking CI gate. This adds an opt-in --fail-on-violation flag that exits with code 10 when violations are detected.

Fixes #391

@mbarbero mbarbero requested a review from a team as a code owner March 3, 2026 20:30
@fproulx-boostsecurity
Copy link
Contributor

Thanks for your contribution @mbarbero ! Could you fix the lint please?

…ected

poutine always exited with code 0 after analysis, even when violations were found, making it unsuitable for use as a blocking CI gate. This adds an opt-in --fail-on-violation flag that exits with code 10 when violations are detected.

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Signed-off-by: Mikaël Barbero <mikael.barbero@eclipse-foundation.org>
@mbarbero mbarbero force-pushed the add-fail-on-violation branch from 3de2f42 to d0e5208 Compare March 5, 2026 12:00
@mbarbero
Copy link
Author

mbarbero commented Mar 5, 2026

linter issues are fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add --fail-on-violation flag to exit non-zero when violations are detected

2 participants