Skip to content

Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1452 results found

  1. I suggest you add functionality to display a badge showing the currently deployed version of a specific project.

    In a similar way to http://shields.io/

    In the UI you would show the link to use that would be an endpoint that displays a PNG or similar containing the project name, environment and currently deployed version.

    76 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  ·  Integration  ·  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)
  2. When a new environment is added to a project, it becomes a pain to add all the variable overloads for that environment.

    It would be nice to have a way to select all the variables you wish to clone along with the scope you wish to apply to them all. After they are cloned, you could easily update their values and then save.

    At the moment, it is a rather cumbersome task of finding a variable, copying its name, pasting it down the bottom, entering the new value, selecting the scope, and repeating one by one for each variable. Since…

    76 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

    14 comments  ·  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)
    Paul Stovell responded

    Hi Richard,

    There is a shortcut that can help – if you right click on a variable, there’s a Duplicate option. It doesn’t work with multiple selections however, but it should get you part of the way.

    Paul

  3. We need an ability to allow specific users access to the script console based on their environment permissions. So if we could have the ability to assign users/teams access to the script console, and then only allow them to use it based on their environment permissions that would solve some problems.

    Source: http://help.octopusdeploy.com/discussions/questions/2242

    72 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  ·  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)
  4. External feeds currently only support NuGet package feeds. It would be good to support ZIP feeds, to support integration with products like Artifactory.

    70 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  ·  Integration  ·  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)
  5. Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.

    I would like to be able to version octopus variables, this would include:
    - Who
    - When
    - When deployed
    - The ability to roll back/forward.

    At the moment we have to source control much of this type…

    67 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

    Planned  ·  7 comments  ·  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)
  6. We just found an issue where our CI deployments via Octopus had been backed up for more than a day because one of them was hung on an FTP to Azure issue. We found out because a tester tried to run a promotion to Test which didn't complete in a timely manner.

    This highlighted that there is no step timeout available so that we could for example have the step fail if it doesn't complete within X minutes. Similarly, we should be able to fail the overall deployment if the collective steps take longer than Y minutes.

    67 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

    11 comments  ·  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)

    Until we implement this feature, the work around would be to monitor the deployment using the API and cancel it if a timeout has been reached.

    I have written up a script (https://octopus.com/blog/automating-octopus-with-azure-functions) that retrieves all running deployments for a project and cancels it if:
    - it has been running for more that 30 minutes
    - the first step has been running fro more than 20 minutes
    - the first step has not output any logs in 5 minutes

    This can run as a scheduled task. Alternatively you can use the subscriptions feature to kick off a piece of code (eg Azure function) that does this polling, as described in this blog post: https://octopus.com/blog/automating-octopus-with-azure-functions

    — Robert W

  7. Whilst it is possible to integrate Slack in to Octopus using script steps at the moment, there are now some great possibilities with Slack Apps: https://slackhq.com/get-more-done-with-message-buttons-5fa5b283a59#.uw51h0tvy Steps like manual authorisation steps could be actioned through Slack, each step in a deployment could have an "output result to Slack" option etc.

    65 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

    4 comments  ·  Integration  ·  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)
  8. https://github.com/OctopusDeploy/Issues/issues/590

    Would you consider supporting net.tcp binding as an IIS Binding type so that we can configure WCF services via the "IIS web site and application pool" feature. Currently only HTTP and HTTPS are supported.

    64 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

    9 comments  ·  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)
  9. In Octopus 3.2 the Channel Version Rules only apply to explicitly selected Package Steps.

    When adding a new Package Step, you need to remember to add that Step to all of the Channels that apply, otherwise when creating a Release, none of the Version Rules will apply to that new Package Step.

    What if you could create a Version Rule that applied to ALL Package Steps as an alternative to being explicit?

    This could be more convenient, and safer-by-default, when people follow a consistent convention for versioning the packages in their Projects.

    62 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

    8 comments  ·  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)
  10. It would be great if you could save multiple dashboard configurations (as opposed to just the single one) and then switch between them.

    The reason behind this suggestion is that we have so many different projects and customers (each customer with their own set of environments) that when you want a view thats in the context of a particular customer, you have to constantly re-configure your existing dashboard to filter out all of the noise. It would be easier to define the dashboard configuration once for a particular customer, and then simply switch to it.

    If you really wanted to…

    61 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

    12 comments  ·  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)

    I’ve reset the status of this suggestion, as the requirement described is for multiple dashboard configurations per-user, which Octopus does not currently support. Apologies for the misunderstanding.

  11. Letsncrypt could get more popular with the pass of time. Would it be useful to provide support for automatically renewed thumbprints created by it?

    Source: http://help.octopusdeploy.com/discussions/questions/8393

    60 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

    11 comments  ·  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)
  12. Currently (2.6.x) its not possible to use Octopus variables from the Script Console. It makes sense that Project variables cannot be used from the SC, but variables from Library Sets might be a good idea.

    60 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

    14 comments  ·  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)
  13. When Tentacle cleans up an installed package folder as part of retention policies, it would be great to be able to have a custom script - like "Undeploy.ps1" - which Tentacle invokes if it finds.

    This would make it possible to delete old custom installation folders during deployment.

    60 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

    8 comments  ·  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)
  14. When updating Variables, it would be great to see what Octopus will change the web.config to when deployed to an environment without actually deploying it.

    57 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  ·  Installation  ·  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)
  15. For steps like 'post to a slack room' or 'update the build server with a token', I think it is reasonable to provide some sort of toggle to allow the step to fail without failing the entire deploy.

    56 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  ·  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)
  16. Currently with Guided failure mode you need to watch the deployment and continue if a machine fails. Sometimes a deployment might be going out to 50 machines, and one might fail but the rest of the deployments should continue, and that deployment was scheduled for 1am.

    Having a setting to allow you to set 'continue on failure' deployments so they would run without a user but would continue to the other machines even if X failed would take the place of the user always hitting continue.

    Source: http://help.octopusdeploy.com/discussions/questions/4472

    56 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

    13 comments  ·  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)
  17. Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
    In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
    This is not possible now, the only solution now is to cancel all the existing tasks.

    54 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

    4 comments  ·  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)
  18. Make it possible to allow users to enter their own HTML/CSS which can appear:

    1. At the bottom of the <head>
    2. At the bottom of the <body>

    This would let users:

    1. Change the colours in Octopus to highlight differences between "production" Octopus vs. a pre-production Octopus
    2. Make their own CSS overrides for things like the dashboard

    If we're worried about HTML, maybe just allowing a custom CSS file would be enough.

    54 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

    8 comments  ·  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)
  19. We are using guided failure mode by default. Most problems that pop up for our website deployments can be fixed with a one line command and then continue on.

    Recently, we've started using TeamCity to create and deploy releases to our Staging environment as soon as TC finishes it's build. Since this action is automatic, if the build is waiting for manual intervention (guided failure mode), it would be nice to receive a notification when it enters that state.

    The typical notify when failed steps do not work since the build never "fails"

    Source: http://help.octopusdeploy.com/discussions/questions/2950

    54 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

    8 comments  ·  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)
  20. Currently, retention policies are applied at the end of a deployment only. It might be good to have a way to force retention policies on tentacles outside of the context of a deployment. Maybe a button on Configuration -> Retention -> Top right corner, specific for tentacles.

    53 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  ·  Installation  ·  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)
  • Don't see your idea?