CI Treat Errors As Warnings - ref #2295

[erikgraa]

PR Summary

Added parameter 'CITreatErrorsAsWarnings' to output configuration. When true, errors will be logged in CI as warnings.

Fix #2295

PR Checklist

• PR has meaningful title
• Summary describes changes
• PR is ready to be merged
  • If not, use the arrow next to Create Pull Request to mark it as a draft. PR can be marked Ready for review when it's ready.
• Tests are added/update (if required)
• Documentation is updated/added (if required)

[fflaten]

Thanks for looking into this! Will give it a review the next days hopefully.

Should the option maybe be a StringOption? Ex. CILogLevel with a default of Error? Just to avoid a breaking change if we'd want to support ex. informational/notice at one point.

Thoughts on this feature @nohwnd and @ArmaanMcleod? See discussion in related issue

[erikgraa]

Thanks for looking into this! Will give it a review the next days hopefully.

Should the option maybe be a StringOption? Ex. CILogLevel with a default of Error? Just to avoid a breaking change if we'd want to support ex. informational/notice at one point.

Thoughts on this feature @nohwnd and @ArmaanMcleod? See discussion in related issue

CILogLevel is a great idea! I pushed an update that reflects this.

[fflaten]

Looks great! :) Just need to include configuration validation and expand tests.

We should throw a more friendly error when a invalid value is used. Add a check like this just below it. 🙂

Pester/src/functions/Output.ps1

Lines 774 to 776 in d81fdbc

	if ($PesterPreference.Output.CIFormat.Value -notin 'None', 'Auto', 'AzureDevops', 'GithubActions') {
	throw "Unsupported CI format '$($PesterPreference.Output.CIFormat.Value)'"
	}

[fflaten]

LGTM! 🎉

[erikgraa]

Seems this PR didn't make it to the 5.4.1 release; any chance you will get a chance to look at it in the not-so-distant future @nohwnd / @ArmaanMcleod? 🙂

[nohwnd]

Merged, thank you all. Will start preparing next minor release.