0
votes

I am using Visual Studio Team Services for Continous Integration, Continous Deployment for a ASP .NET Core project. In VSTS when we create a build definition, we are required to provide a repository link from where VSTS will get the code and then build it and we can use the build artifacts in VSTS release definition.

I do not want to link my repository with VSTS build definition. Instead I want the ability to produce a Web Deployment Package or a NuGet package for my project (I wont mind even if I have to do it out of VSTS) and then use that package as build artifact in my release definition.

Is that possible? if yes then how can I acheive this?

Thanks

2

2 Answers

0
votes

You can add a package management feed as a release artifact. When choosing an artifact source, change the dropdown from Build to Package Management.

However, you still need to publish your NuGet packages to the feed first.

0
votes

First, there are many source types of artifact in Release, as Daniel said that you can choose Package Management as release artifact, but you need to push the package to the feed first.

With Build artifact, it needs to be generated through Build and you need to specify the sources (Get sources).

Secondly, you can don’t link any artifacts in release definition, and download/copy the Web Deployment Package or NuGet package from a shared folder, other machine or other ways (e.g. FTP server) through related tasks, such as Copy Files, Windows Machine File Copy, PowerShell (download files programming) etc…