General

  1. Deployment step success and error colors Red/Green color

    On the deployment steps, when a step fails the step entry color flips to red. For a success it is Green

    For a person that is Red/Green color blind telling the difference can be almost impossible to detect

    changing the step icon from the Plus to a X or Check will make it easier to distinguish

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Deploy in "Debug Mode", pause after each step

    It would be useful to be able to run a deployment in "Debug Mode", where it would execute one step at a time, pausing after each step, so a developer can verify that it is operating correctly.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. If a step failed on a specific Target / Tentacle remove it from the list of targets for future steps

    It would be configurable and we could leverage the existing functionality of how the Health Check steps take targets out of the list for future steps.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Tentacle service recovery

    When a tentacle is installed on a machine, the recovery on the windows service should be set to restart the service on failure.

    I had several tentacle services fail, which caused deployments to fail on those nodes

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow use of user display name in audit

    It wouldbe nice to display the "Display Name" for an account instead of the username in the audit (I know this can be changed, but if name changes are also audited, it should plug the hole), or maybe both, for PIV logins where the username cannot be changed, or maybe better yet, allow us to tie accounts together or associate them as one.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Audit access to Audit screen

    Proposed by a user here: https://secure.helpscout.net/conversation/246264030/9467 (private link)

    As an auditor, it would be nice to see who is logged in and who has logged in from the audit screen.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Exit codes for Octo.exe

    Octo.exe returns:

    - 0 When the deployment succeeded
    - 0 When the deployment suceeded with warnings (SWW)
    - 1 when the deployment fails

    Would it be useful to add a specific error code for SWW? Build servers also have a "SWW" status and Octo.exe could pass this specific error code to let the user know that there was a warning during the deployment.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Ability to enforce steps in group of projects

    There are time where Octopus admins want to make sure that all the projects on their instance run a specific step at the beginning/end of all of their deployments. This has been asked a few times already, most of the times by big companies with lots of projects.

    Users: Would this feature be useful to you? Please tell us a bit more about your scenario and how would this solve your needs.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support the new In-VM metadata service for load balanced nodes

    Microsoft has just released the Azure in-VM metadata service that will let you know when a machine is going to be rebooted.

    it would be great to tie this into the node maintenance functionality so that the node is automatically drained.

    It might be useful to do this for AWS as well (similar to https://github.com/scopely/shudder), but that looks a lot harder.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide access to account credentials during deployments

    When a deployment is being executed, there may be some value in providing access to account credentials that have already been stored and managed in Octopus Deploy.

    While the primary motivating factor for creating the accounts section has been to provide access to deployment targets, some users may get value from using them to access or control other parts of their deployment process that sit behind some authentication mechanism. This would allow OD to better manage all the resources needed to fully complete a deployment with authentication details being securely managed in one place.

    The biggest concern with this approach…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Multi-select tentacles for changing environment/roles

    Enable a way to make a changes (add/remove environment, add/remove role) to multiple tentacles at once.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Hide Release

    Over time, older releases that are no longer in use just crowd up the release screen. I want to retain their history, so do not want to delete them.

    It would be nice to be able to hide releases.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add an ability to define your own package install directory

    having a variable to be able to define your own package installation directory is needed. We have a situation where we rely on roles to define variables for customers, but the package on the same environment will not install if it already has been, even though it needs to be re-extracted for the role variables to be applied. Having to force the package redeployment on all projects then takes a lot longer than it should. Having the ability to add role to the path of the package directory would stop this from being an issue for us. Something similar to…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add option to Rention Policy to 'Keep last package' always

    We need an option in the retention policy to allow for keeping the last updated package in the repository 'always'.
    There are cases where the latest release does not included the latest package, but that package may still be needed later on.

    Source: UV 941

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Show differences in scope values

    https://github.com/OctopusDeploy/Issues/issues/264

    When displaying snapshots, show any variables whose scope values don't appear in the current set available to the project (owner)

    At the start of deployment, warn if scope values have changed (e.g. if Production is deleted and recreated, there will be a variable scoped to the old Production environment ID, apparently useful but not applied)

    Where the name associated with a scope value has changed, show the old and new names

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 2 60 61 62 64 Next →
  • Don't see your idea?

Feedback and Knowledge Base