Deployment strategies for Asp.Net MVC app on a server behind a wall of fire

Question

One of our clients absolutely insist on using their own server, but refuse to open up IP ports for automatic WebDeploy (don't ask why and how - large enterprise). Usually we have TeamCity installing WebDeploy packages as and when. But not this time -(

We have looked on Octopus Deploy, hoping to install a tentacle on their server and make it poll our server, but Octopus does not seem to work that way.

We are thinking we'll have to write some sort of service that will be polling for new versions of software and if are available, do deployment. But that seems to be a lot of work. I wonder if that exists already and we can just buy this system.

What are the ways to do automatic deployment for a server that can only initiate the connection, but can't accept connection?

Answer 1

Octopus Deploy should work. it supports a polling mode.

Read more about it here: http://docs.octopusdeploy.com/display/OD/Polling+Tentacles