azuredevopslabs | plan smartly , collaborate | DevOps library

I think you are missing a task to publish the test results to Azure DevOps. You are executing dotnet test and get a trx- file (the result file), but you are not doing anything with it.

You need to use the Publish Test Result task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-test-results?view=azure-devops&tabs=yaml) afterward to upload the trx- file to Azure DevOps.

Or you change the dotnet test command to use the Visual Studio Test task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/vstest?view=azure-devops). This tasks makes the upload of the trx- file automatically.

Read a similar question from VSTS (Visual Studio Team Services) and was able to solve it.

Created a Pipeline variable called ConnectionStrings.DefaultConnection that had a reference value to my linked variable group.

If my secret was named ConnectionStringsDefaultConnection I would hook this up as a linked variable and then add $(ConnectionStringsDefaultConnection) as a value.

Source:

https://stackoverflow.com/a/47787972/3850405

have seen in the documentation that it cannot be used in the same way as a normal (non-secret) variable. It says "Instead, we suggest that you map your secrets into environment variables." and "You need to explicitly map secret variables."

The doc is misunderstood, it's not saying the secret variables cannot be used in the same way as a normal variable, instead, it says it's not suggested to pass secrets on the command line directly since some operating systems log command line arguments which could cause information leakage as mentioned, and it's suggested to map your secrets into environment variables.

This blog says you can use it directly in the script, which seems to contradict the MS document.

As mentioned above, the secrets can be used directly in the script although it's not suggested, so they are not contradictory.

You can also check the example in the MSDN doc:

well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one

After I started looking into why the remote certificate (SQL) was invalid, I changed my connection string to include TrustServerCertificate=True. Since this is a demo environment and I kept Encrypt=True, then it looks like this fixed everything! If anyone thinks bypassing walking the server certs is a bad idea, let me know too.

I've checked the full deployment process from the beginning to end. I also got the same error. It seems that this tutorial creates a new resource group, but did not create a new web-app inside that resource group to deploy. To successfully deploy, create a webapp inside your resource group with the name "githubci-web-" and run the deployment again. It will be successful.

After several attempts, changes and other setting tweaks i'd managed to get this operational. I think the problem was solved by creating a new personal access token with only the code read/write option selected. Now the sonarcloud decoration works (providing comments for codesmells) and the status policy is selectable in the branch security policy settings.