1

In Visual Studio Online (aka Team Services, aka Team Foundation Services) I had some XAML definitions which build and deploy in the TFS repository by setting the Staging location with:

Copy build output to the following drop folder:
    $/{reposotiory}/Drops

Now, after creating the new vNext build definitions, I'm unable to reproduce this behavior.

I've created an artifact (server type) as suggested here: https://www.visualstudio.com/en-us/docs/build/steps/utility/publish-build-artifacts but it's only accessible through website (in the Artifact tab): Artifact tab in visualstudio.com

Others Stackoverflow questions refer to deploy in a external server by using a UNC path like:

Is it possible to drop binaries in the repository? Am I doing anything wrong?

Alex
  • 797
  • 10
  • 30

1 Answers1

0

You can drop the file in local repository first (UNC path, create a share folder) then check in the drop to remote repository. If you want to do that within the build process, just create a cmd/batch file with the tf checkin command.

We don't recommend to do that, as TFS repo is for source control, the binaries files don't need to add in source control. So, with the UNC path or FTP to store the drop file would be a better practice.

enter image description here

Andy Li-MSFT
  • 28,712
  • 2
  • 33
  • 55
  • I don't have my own TFS server, I'm using Visual Studio Online (https://{mycompany}.visualstudio.com/) as repository and build server. As I read in the documentation the Artifact Type file share is not possible to be use in Visual Studio Online. Am I wrong? – Alex Aug 01 '17 at 09:08
  • @Alex The file share is also available for VSTS, you can deploy [private Windows agent](https://www.visualstudio.com/en-us/docs/build/actions/agents/v2-windows) for building and make sure the agent services account has the permission to access the UNC path. – Andy Li-MSFT Aug 01 '17 at 10:04
  • Please also answer my question problem in below post https://stackoverflow.com/q/63059180/10846390 – Saad Awan Aug 19 '20 at 12:18