Damian Brady

← Feedback & Support for Octopus Deploy

My feedback

  1. Support Net.TCP bindings for IIS configuration

    150 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…)
    9 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Damian Brady commented  · 

    For those stumbling across this request, there's a PowerShell script here: https://www.codingcurve.com/snippet/481/creating-iis-net-tcp-binding-using-powershell/

  2. Better guidance for TFS users

    112 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…)
    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Damian Brady commented  · 

    We have a new video on our videos page that talks about Continuous Integration with TFS. That's a great place to start!: http://octopusdeploy.com/learn/videos

  3. Child Step on Manual Intervention

    4 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…)
    2 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    Damian Brady commented  · 

    An easy way to do this would be to put an email step immediately before the manual intervention step. You can even include details about the deployment using the built-in Octopus Variables (http://docs.octopusdeploy.com/display/OD/System+variables).

    If you want an email with specific information sent out if the step is rejected, you could add an email step after the manual intervention step that only runs on failure.

Feedback and Knowledge Base

(thinking…)