VSTS to on-premise build agent then to Octopus Deploy

Legacy Execution
1

I would like to deploy from VSTS to on-premise build agent then to Octopus Deploy.

I have the VSTS to on-premise build agent working and a NuPKG package as a result.

I am not sure how i get Octopus to take the package into it’s repository ready for deployment.

Do i need to configure an Octopus Deploy plugin inside VSTS ?

I know there is a lot of documentation on here, i have read a lot of web pages on the subject too but i would really like to know the official way to accomplish this.

Thanks

2

Hi Alan,

Thanks for reaching out!

If you already know the location in disk of the Nuget package, then I’d recommend you to use the Push step of the Octopus Deploy plugin for VSTS to push the package to the Octopus built-in repository: https://octopus.com/docs/guides/use-the-team-foundation-build-custom-task#UsetheTeamFoundationBuildCustomTask-push-packages-stepAddaPushPackage(s)toOctopusStep

Hope that helps!
Dalmito

3

Hi Dalmiro, Thank you for the suggestion. Am i right in thinking that i would need to make the Octopus URL public so it could talk to the VSTS Octopus plugin ?

The NuPKG package is built on-premise, so is there a way Octopus could listen for it or could MSbuild possibly could push it to the Octopus repository ?

4

Hi Alan,

Am i right in thinking that i would need to make the Octopus URL public so it could talk to the VSTS Octopus plugin ?

The VSTS build agent will need to be able to communicate with the Octopus server through the network, yes.

The NuPKG package is built on-premise, so is there a way Octopus could listen for it or could MSbuild possibly could push it to the Octopus repository ?

Octopus can consume packages from many sources as explained in the documentation. Instead of pushing the package to the built-in repository, you could tell Octopus to pick the package from a folder like c:\packages or \\server\packages by creating an External Feed Source with those paths.

As for MSBuild pushing the package, it is totally possible if you are using Octopack: https://octopus.com/docs/packaging-applications/nuget-packages/using-octopack

Regards,
Dalmiro

5

Thanks Dalmiro. I was confused by the VSTS Endpoint. It is merely a connection parameter rather than a publicly exposed connection point.

I referenced the VSTS Endpoint in the Octopus VSTS plugin and voila, i have built and pushed a NuGet package to the Octopus server’s repository.

6

Cheers!