Closed carmeleve closed 6 years ago
@carmeleve Thanks for the feedback. We are actively investigating and will get back to you soon.
The screen images for this tutorial need to be updated, as this tutorial is very hard to follow.
@carmeleve I have assigned the issue to the content author to evaluate and update as appropriate.
@carmeleve Let's start with a simple question and I'll have some follow-up. What Agent Pool are you using in your Build Definition? Is it a hosted or self-managed pool?
+@milismsft
@David-Noble-at-work Hi, sorry have been out of office since Thursday, we are using the Hosted VS2017 build agent.
@carmeleve I had a chat with David about this issue today, we don't have any known issues with hosted VS2017 build agent. Because it's a connectivity issue and not a doc issue, we need to debug it further and take a look at your environment. Can you please send an email to askcosmosdb@microsoft.com alias, it creates a support request and someone from our team will get on a call with you. We will close this issue here and track it in the support request.
Hi, We are trying to use the CosmosDB emulator for our automated testing. I've followed the steps outlined here, placing the emulator build task at the start of the Azure DevOps build definition. However it can't get past starting the emulator as the emulator build task is failing with the error: "Start-CosmosDbEmulatorContainer : Connectivity test failed:{"PingSucceeded":true,"TcpTestSucceeded":false}" I've tried setting the port mapping to "PublishAll" and that made no difference.
Any help would be appreciated!
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.