Octopus deploy export – import

Imagine you don’t have acces to a customer’s serverpark but still want to use a central octopus deploy server. Now you can export that release from your octopus deploy server and import it into the (local) installation on the customer’s serverpark.

Commandline export – import

What I hoped octo commandline would do: export all variables and nuget packages to disk. Then I could import everything to the customer installation. But what it did was export the definition of the project / release in JSON. Not sure when they think this is used.

Nuget to the rescue

My solution is to get the nuget packages that octo.exe creates and upload them with nuget.exe to the octopus deploy server.

NuGet.exe push <YourApp.nupkg> -ApiKey <Your API Key> -Source http://customer.octopus/nuget/packages

Then create the same process steps (tailored to the customer) and begin releasing. Next release upload the nupkg files again and create a release from the latest versions.

About erictummers

Working in a DevOps team is the best thing that happened to me. I like challenges and sharing the solutions with others. On my blog I’ll mostly post about my work, but expect an occasional home project, productivity tip and tooling review.
This entry was posted in Tooling and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.