-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warn on failed verification #339
Labels
Comments
mgroth0
added
Feature
Feature request issue type
S: untriaged
Status: issue reported but unprocessed
labels
Apr 15, 2023
shanshin
added
S: postponed
Status: work on the issue is not in the short term plans
and removed
S: untriaged
Status: issue reported but unprocessed
labels
Apr 17, 2023
Closed
shanshin
added a commit
that referenced
this issue
Mar 21, 2024
Added property to suppress task execution failure if there has been a violation of the verification rules Resolves #339
shanshin
added a commit
that referenced
this issue
Mar 21, 2024
Added property to suppress task execution failure if there has been a violation of the verification rules Resolves #339
shanshin
added a commit
that referenced
this issue
Mar 21, 2024
Added property to suppress task execution failure if there has been a violation of the verification rules Resolves #339
shanshin
added a commit
that referenced
this issue
Mar 27, 2024
Added property to suppress task execution failure if there has been a violation of the verification rules Resolves #339
shanshin
added
S: ready for release
Status: merged in the main branch
and removed
S: postponed
Status: work on the issue is not in the short term plans
labels
Mar 28, 2024
Implemented in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Sometimes I may want the vertification task to simply produce a warning rather than a failure.
I suggest adding a configuration property to the buildscript dsl to allow users to control whether a failed verification produces a warning or an exception.
The text was updated successfully, but these errors were encountered: