This means that it is theoretically possible for our CI to let through build errors, test failures, or worse. Any help fixing this would be appreciated. This is a terrible default, but we'll just need to work around it however we can.
Note that it isn't enough to just add set -e at the top of the script since that won't work on Windows.
We have a few multiline scripts in our Azure DevOps Pipeline. For example:
https://github.com/sunjay/turtle/blob/dc80b658717134366b7fc387ce251f327580d1bb/azure-pipelines.yml#L61-L66
Originally when I set this up, I expected that if any of those lines failed, the whole step would fail, but apparently that is not the case.
Related GitHub issue: https://github.com/microsoft/azure-pipelines-yaml/issues/135
This means that it is theoretically possible for our CI to let through build errors, test failures, or worse. Any help fixing this would be appreciated. This is a terrible default, but we'll just need to work around it however we can.
Note that it isn't enough to just add
set -e
at the top of the script since that won't work on Windows.