Kevin Kelchen

My feedback

  1. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    Kevin Kelchen supported this idea  · 
    Kevin Kelchen commented  · 

    I was directed to this suggestion by Octopus Support from an issue I came across:
    https://help.octopusdeploy.com/discussions/problems/70187-extracted-packages-linger-when-using-custom-install-directory

    When using a Custom Installation Directory, the copy of the package at the extraction location is left around after it has been copied to the Custom Installation Directory. The version in the Custom Installation Directory is the one that matters and is where the application runs out of; the version it was copied from in the extraction location is no longer useful. I would like a solution to automatically delete the copy of the package at the extraction location when using a Custom Installation Directory.

    I think it's an important point to make because you could imagine that Octopus could get this feature where only the current release is retained and yet the copy of the current release's package at the extraction location could still be left to linger around when using a Custom Installation Directory.

  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Kevin Kelchen shared this idea  · 
  3. 145 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    Kevin Kelchen supported this idea  · 

Feedback and Knowledge Base