GeezerVison

My current suspicion is that the Ubuntu 18.04 problems are caused by the LANG=C.UTF-8 locale change on that platform. I'll have a look into how dictionaries are built to make sure they're not taking the culture into account in any way.

Hmmmm just confirmed it wasn't that and haven't been able to reproduce yet on my ubuntu 18.04 VM

Also: I was not sure if we still need the calls to ./PSCompatibilityCollector/build.ps1 in the build yaml script?

We should certainly be building the module to make sure it builds in CI, but not sure if you mean that there's another call to that build script elsewhere that outmodes it?

Close and re-open to see if things have changed and if the new Ubuntu failures on AppVeyor, happen here as well.

Hmmm, so it is reproducing in AzDO CI as well. After spending a day trying to reproduce this, I stopped trying when James Truher (@JamesWTruher) and I didn't see it in AzDO (only AppVeyor).

Since this seems to be causing an issue in AzDO now, I'll go back to trying to reproduce it. I didn't have much luck replicating the AzDO environment locally...

Maybe just ignoring the failures similar to the AppVeyor ones would be the best? Interestingly there were new AppVeyor AppVeyor failures just before xmas in AppVeyor but they have disappeared now

Frustrating. But yes, I don't think these failures should block anything, so we should ignore them for now.

I'll open a PR to ignore them in AzDO

I suggest to just add them in this PR here and use an environment variable that is only set in Az-Do

I suggest to just add them in this PR here and use an environment variable that is only set in Az-Do

Ok with you if I commit to this branch?

Yes, please

Getting this:

To https://github.com/bergmeister/PSScriptAnalyzer
 ! [remote rejected] AzurePipelinesIntegration -> AzurePipelinesIntegration (permission denied)
error: failed to push some refs to 'https://github.com/bergmeister/PSScriptAnalyzer'

Going to open a PR instead

See bergmeister#11

Don't know why the push did not work, especially since I had the 'Allow edits from maintainers' checkbox ticked. Thanks for the PR of the PR.

Great, the Ubuntu build fails now because somehow after bootstrap the .net core sdk, it seems to lose it on the PATH env variable. Will merge bootstrap and build tasks into one then

Yippee, it's finally green. Now, I have to do a self-review as well as some things might've changed since then.
For example I created a build definition for each type of hosted agent image as there was a dropdown (this allowed to report them indiviudally in GitHub). Now there is only the previously chosen option left in the dropdown, which means that we could not add a new build definition with a new image. Therefore I think it might be better to put the image into YAML as well now and use only 1 build definition. What do you think?