Closed rasmusskov closed 2 months ago
Hi,
there are no warning, but "info".
Can you please check your ruleset to see if you demoted the rules?
My ruleset only have AL0432 in it, and im seing the warnings in vscode.
But i understand from the setting name of course that we are using FailOnWarnings.. But what if we want to have FailOnInfo... I seem to remember that pipelines has failed on "info" previously
{
"name": "BC",
"description": "Rules",
"generalAction": "Hidden",
"rules": [
{
"id": "AL0432",
"action": "Hidden",
"justification": "Marked for removal"
}
]
}
May be you can bump from Info to Warning, as that is what you want?
info is Info - we never should have failed on that .. .
{
"name": "BC",
"description": "Rules",
"generalAction": "Hidden",
"rules": [
{
"id": "AA0072",
"action": "Warning",
"justification": "Force a warning to fail pipeline"
}
]
}
We are trying to enforce a problem free project, and that includes everything.. Ie.. keep the "info" as info in vscode, but have the pipeline fail if there is any Maybe a feature request to have a new setting in the pipeline to fail on infos also?
We'll add a "FailOnAny" setting in a future release.
Should have been fixed in 1.462.
Describe the bug We have a project, where failonwarnings = true in the yml file, but when alops pipeline is run, it still completes as succeeded the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Pipeline should fail since there is warnings in the compiler