[BUG]: Scanning solution seems to not work in pipeline about liz HOT 9 CLOSED

Sure! I was able to reproduce this exact bug when creating a new project so here we go:

Screenshot to your first question:

But the same can be seen here: https://dev.azure.com/PhilippHonsel/liz.bugreport/_build/results?buildId=2&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=35f53584-79fc-539f-463c-6471d0663a3a

This is a "broken" pipeline run. You can feely navigate this project to find the root cause if you want. With this code it works on my windows 10 machine, but not on the pipeline. If I remember corretly, the public azure devops pipelines are running on ubuntu as well.

from liz.

Ahh very nice, this will help a lot, thank you! :)

I'll have a look at that as soon as I can. This will be some time next week though (real-life y'know), I hope that does not hinder you too much.

Looking at the output of the Trace-Log seems like liz doesn't find anything to process. As if there aren't any package- nor project-references. Seems odd.

from liz.

Yes, using a csproj works. (See the screenshot in the bug report)

from liz.

This did fix it indeed. Thanks!
See new run: https://dev.azure.com/PhilippHonsel/liz.bugreport/_build/results?buildId=3&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=35f53584-79fc-539f-463c-6471d0663a3a

from liz.

Hi @starteNCS,

thanks for providing a detailed bug-report!
Is there any chance you could provide me with the following information?

1. A diagnostic log (using -l Trace) make sure to censor any confidential information
2. A solution containing the projects and package-references that you're currently using - again, making sure to censor any confidential information (i.e. I don't need any source-code, as liz only uses the project- and package-reference information)

Both of these things might be helpful to track down the issue that might occur in your Azure-Pipeline.

from liz.

Unfortunately I won't be able to work on this today.

But: Can you try to run the analysis targetting a csproj instead of a sln? This might help to narrow down the cause of the issue.

from liz.

I unfortunately have no solution yet, but I managed to track down that the issue probably comes from my SlnParser library which I use to parse the solution when one is given.

from liz.

I just released a new version 2.0.3 which should fix the issue that you described. Can you verify that? Worked in my Azure DevOps pipeline.

from liz.

great news, thanks!

from liz.