https://pulumi.com
Join Slack
This message was deleted.
# azure
s
This message was deleted.
c
do you have a snippet of your pipeline's yaml?
Specific reason to run this on Windows? (not that it shouldn't work, but just curious)
c
Hi @rhythmic-vegetable-87369 can you please provide re-run the job with System Diagnostics enabled and share the logs with me directly? Also, I see that you have double-posted the same question in another channel. (https://pulumi-community.slack.com/archives/CQ2QFLNFL/p1578759832003200?thread_ts=1578759832.003200&cid=CQ2QFLNFL). In the future, can you please post in one channel? It would be helpful to people trying to help solve the problem to see previous responses in a single thread.
r
Thanks for the help. Here is the log.
tasklog_7.log
@colossal-room-15708 No specific reason for using windows. Please find attached the YAML.
c
Thanks for the log. It looks like the problem is with the stack you are trying to use. It is possible that there is a typo or the stack does not exist anymore. As re you sure the fully-qualified stack name is correct? Does this work locally for you? 
2020-01-11T01:41:06.5354596Z [command]d:\a\_temp\0c2c6f5c-12cc-466a-9fc3-34b632f33ffd\pulumi\bin\pulumi.exe stack select miflamashood/matchnetv2deploy/matchy
2020-01-11T01:41:06.5442747Z ##[error]Error: There was an error when attempting to execute the process 'd:\a\_temp\0c2c6f5c-12cc-466a-9fc3-34b632f33ffd\pulumi\bin\pulumi.exe'. This may indicate the process failed to start. Error: spawn d:\a\_temp\0c2c6f5c-12cc-466a-9fc3-34b632f33ffd\pulumi\bin\pulumi.exe ENOENT
You also may want to check to make sure that the folder in which you are executing (seems to be 
matchnetv2deploy
according to your configuration file above) actually contains the Pulumi app that you are trying to execute.
r
Yes, it works locally, I'm able to create my resources
Yes, that folder contains the pulumi stuff
c
I'll reach out to you via DM.
Just to close out the loop here. Turns out that the directory structure in the release definition @rhythmic-vegetable-87369 was using was nested under another parent. So the Pulumi Task couldn't find the directory provided as input to the "Working directory" input. (It is likely due to using an artifact in the release stage built from a Pipeline build that the parent directory is different.)
✔️ 1
2 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by