Artifact “Windows Machine File Copy” task configure properly

0
votes

I just tried to automate my build process. So tried to add Windows Machine File Copy task for artifact (Release Definition)

This DevOpsBuild artifact has 3 environment as seen on the picture.

enter image description here

So I added Windows Machine File Copy task to copy the files from my published folder

\localhost\NewBuildDropLocation\$(Build.DefinitionName)\$(Build.BuildNumber)/drop/MVCWebApplication/MVCWebApplication

So as example

\localhost\NewBuildDropLocation\DevOpsBuild\20180427.3\drop\MVCWebApplication\MVCWebApplication

here the image of above settings

enter image description here

then after I create release for this artifact, it's stuck "In Progress" phase not going for other phases.

enter image description here

I'm using localhost environment for all these task. I'm newbie to DevOps, followed this tutorial

1
tfsazure-devopsbuild-automationdevopsrelease-management

1 Answers

2
votes

localhost is the machine the agent is running on.

The source parameter should be the location of the build artifacts, which is usually $(System.DefaultWorkingDirectory), or some subfolder of that. See the documentation for more details.

The Machines parameter should be an actual hostname for a server on your network.

Also note that if you're using the Hosted agent, none of this is going to work -- if you're deploying to on-prem servers, the servers have to be network-accessible by the agent. The hosted agent is run by Microsoft and lives in the cloud and definitely doesn't have access to your servers. You'll need to configure a private agent.