I suggest you...

← General

Manage VPN connections

Make it possible to put machines into a VPN connection, and have Octopus manage the closing/opening of the connection so that concurrent deployments don't result in closed or hanging connections.

64 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
AdminPaul Stovell (Founder, Octopus Deploy) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

7 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    A VPN-feature would be really great!
    In the meantime; How did you solve this with scripts Sebastian? I'm planning to do the same thing (Juniper Network connect)

  • Sebastian Nemeth commented  ·   ·  Flag as inappropriate

    I've just applied upgraded my Octopus Deploy to 2.5.4 and the last update that runs Retention policies after the last 'package deployment' step, rather than the final release step has solved my problem!

  • Sebastian Nemeth commented  ·   ·  Flag as inappropriate

    I'm come back to this problem again, having issues with Applying retention policies.

    I am already connecting to VPNs in my scripts as the first step that runs before NuGet packages are uploaded. However, having the last step as 'disconnect' is a problem, because the connection closes before Retention Policies are run.

    So far, I can't find any way to force the script to run after the retention policy runs.

    Could we either have a 'Wait until retention policy finishes' option for the last step similar to 'Wait until NuGet packages downloaded' found on the first step?

    Alternatively, a manual step to trigger Retention policies would work too.

    Another option to provide (as dave.griffiths mentioned) hooks for pre and post release scripts.

    Seems to me this kind of set up could solve a *lot* of connectivity issues that are causing problems at the moment by letting folks script solutions for themselves.

  • Sebastian Nemeth commented  ·   ·  Flag as inappropriate

    I was just looking at the discussion here: http://help.octopusdeploy.com/discussions/questions/374-deploying-to-servers-in-a-vpn

    I manage solutions for several corporate clients that are deployed to their own servers behind VPNs, and while I will be manually starting and stopping these VPNs via scripts, it would be a massive relief to have Octopus Deploy able to manage the more common VPN solutions for us. For us specifically, we use Cisco VPN Client, Dell SonicWall NetExtender etc.

  • scott mcfadden commented  ·   ·  Flag as inappropriate

    One our customers requires a VPN connection (Cisco AnyConnect Client) before we can deploy. Would be nice if Tentacle could optionally start up VPN connection, deploy, then close VPN connection.

General

Feedback and Knowledge Base

(thinking…)