pulumi / pulumi-az-pipelines-task

Azure Pipelines task extension for running Pulumi apps.
https://marketplace.visualstudio.com/publishers/pulumi
Apache License 2.0
27 stars 19 forks source link

Azure DevOps pulumi preview command failing (C# stack) due to nuget null HOME ENV variable #20

Closed rajeshmuraleedharan closed 5 years ago

rajeshmuraleedharan commented 5 years ago

i know C# language support still in preview.

I have observed c# stack project failing on DevOps error : Value cannot be null. (Parameter 'path1')

image

image

But i am able to do dotnet build on the project, but pulumi preview command failing image

Also dotnet restore command also working fine. is there any switch i can pass to pulumi CLI not to restore nugets because nugets already restored (like dotnet build --no-restore

praneetloke commented 5 years ago

@rajeshmuraleedharan it is not clear to me if you are using this Pulumi task extension to run your Pulumi app in Azure DevOps? Are you manually installing the Pulumi CLI yourself and then running into an issue with running pulumi preview?

rajeshmuraleedharan commented 5 years ago

Yes i am using Pulumi task extension to run c# pulumi app. I have installed pulumi sdk on my deployment agent (windows server 2016). Which has .net core 3 sdk pre-installed. if i run dotnet restore/ build as a deployment step then project getting build successfully. pulumi preview/ up getting above error

praneetloke commented 5 years ago

@rajeshmuraleedharan thanks for clarifying. Can you please post your Azure Pipelines config in a GitHub Gist? (Be sure to remove any confidential information from it.)

praneetloke commented 5 years ago

A new version of the task extension was released which potentially fixes this issue. Would you mind giving it a try? The extension version is 1.0.1. Your build agent should automatically pick-up the new version so as long as you are using the major version 1.x of the task extension.

praneetloke commented 5 years ago

@rajeshmuraleedharan I am going to close this issue as I think the issue is fixed by #25. Please feel free to reopen this if you are still having issues.