Closed kasperdj closed 4 years ago
Here is an example of a previous run of the same pipeline, that failed as expected. Note: This was before the BC Artifact update of ALOps
Hang on: maybe it's because this is an information and not a warning....
Issure fixed, it was only an information and not a warning.
Thanks :-).
Can I ask - did someone create a ruleset for this rule so that it's info in stead of a warning/error?
@waldo1001 there was a slight difference in the code for the 2 two examples even though the compiler output (also in VS Code) raised almost identical "Information", one as warning and the other as Information. So no bugs in AlOps
Describe the bug When I compile my app with: failed_on_warnings: true then the pipeline should fail if I have any warnings. This used to work without problems before the "BC Artifact" update of ALOps
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 It should failed when failed_on_warnings is set to true in the Compile step - like it used to do.
Screenshots