Skip to content

Settings and activity

7 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Piers Williams shared this idea  · 
  2. 23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Piers Williams commented  · 

    The reverse applies: it would be good to be able to see which roles *on tentacles* are currently not used on any deployment steps (and clean them up)

  3. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Piers Williams shared this idea  · 
  4. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Piers Williams commented  · 

    Looking in the Calamari source it'd be really easy to splice this into the existing Bootstrap.ps1 script, just not sure I've got the time to setup an environment to test it in.

    https://github.com/OctopusDeploy/Calamari/blob/master/source/Calamari/Integration/Scripting/WindowsPowerShell/Bootstrap.ps1

    Piers Williams shared this idea  · 
    An error occurred while saving the comment
    Piers Williams commented  · 

    Sorry I forgot the link to my shim script: https://gist.github.com/piers7/f637240ec8408ae6176c
    This binds as many Octopus variables to explicit script parameters as it can, and passes the rest as a hashtable to a parameter called 'properties'

  5. 21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Piers Williams commented  · 

    This came up *again* yesterday, in a conversation with a client that's evaluating Octopus, and doesn't want to lose the ability to rollback (that they have in their current, largely manual, process).

    Piers Williams supported this idea  · 
    An error occurred while saving the comment
    Piers Williams commented  · 

    @Jack - one workaround is to put an additional deployment step prior to the service deployment that does the uninstall, based on finding the currently registered service and using the normal TopShelf uninstall conventions. It's a wee bit messy to do this because you have to grep the service path from the output from SC.EXE since get-service doesn't give it to you, but it can be done.

    An error occurred while saving the comment
    Piers Williams commented  · 

    This also helps in rollback situations (just intentionally saying rollback so it comes up in search). Rollback.

    An error occurred while saving the comment
    Piers Williams commented  · 

    +1. A simple convention where an 'undeploy.ps1' script gets executed in the currently deployed package prior to the next version being deployed is all that's required. If the version number of the *new* deployment was passed to that script it'd be all the better.
    Otherwise definitely risk of leaving debris behind (and I have seen this in the wild, with deployments that deployed varying numbers of TopShelf services too)

  6. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Piers Williams commented  · 

    One way to make dealing with clusters easier would be to allow deployment steps to be limited in the number of times they run (ie scope the step to run across both nodes in the cluster, but limit it to only running at least once). This is useful when deploying to cluster services, like SQL Server, which can be deployed to remotely.

    I've raised this suggestion to cater for that:
    http://octopusdeploy.uservoice.com/forums/170787-general/suggestions/9569970-ability-to-globally-limit-number-of-times-a-step-w

  7. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Piers Williams commented  · 

    If failed packages weren't considered 'installed', this would be really easy - you'd just kick off a new release (without 'force redeployment') and all would be good.

    Apparently this is in progress: see http://octopusdeploy.uservoice.com/forums/170787-general/suggestions/5070326-reinstall-packages-that-failed-in-previous-release