Bart Koelman

Also, note the failures haven't occurred in the Sonar build pipeline so far, so we'd need verbose logging in all pipelines.

It happened again today, this time on Ubuntu. Logs at https://dev.azure.com/SteeltoeOSS/Steeltoe/_build/results?buildId=30623&view=logs&j=d3006ae9-e0d8-51ca-f80d-b22532b69219&t=95ab65d7-e607-5531-bf1f-611160e7c133.

Sorry, yes, Windows.

Suggestion: - Add a temporary undocumented MSBuild property or environment variable that we can set from our Azure DevOps pipeline. - When set, double-check the failure using conventional logic, ie,...

Occasionally hitting the 100ms timeout on shared build agents is a reasonable assumption. I'm happy with this solution, thanks.

It's not possible to PR directly against a wiki, see https://stackoverflow.com/questions/10642928/how-can-i-make-a-pull-request-for-a-wiki-page-on-github for how to control changes.

As part of this, the dependency on `Microsoft.Extensions.FileProviders.Physical` can be removed from the project.

I don't know, haven't tried since. However, it should be easy to determine by checking out a commit from around that time. For example https://github.com/SteeltoeOSS/Steeltoe/commit/326c0fd55eeda2d79fe55443d9d713b4831737e3.

For the moment, we've decided to stick with FluentAssertions v7.x, which is feature-complete and still receives critical fixes. We'll keep an eye on AwesomeAssertions, but it hasn't yet gained the...

/azp run Steeltoe.All