Skip to content

Product Feedback

Categories

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

315 results found

  1. As I've gotten more and more step templates, I've realized that there are some of the step templates that I'd like to rename to make it easier to "group" like ideas. The problem here is that as I refine these, each renaming creates a new version. The same would be true of the description. This doesn't seem like something I should be running out to each process to update especially since the name wouldn't update anyways.

    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  ·  Installation  ·  Admin →
  2. 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

  3. Something I would like to see is user description. We have a few service users and since there is no description we are using a mix of display name and a page in confluence to describe their roles and scope.

    And what about having a place to store API keys? Only available to certain roles, let's say system administrators.

    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  ·  Installation  ·  Admin →
  4. When using branching (and semver on each branch) to maintain feature and release branches, I have found that I do not want to auto deploy every build, rather, I want to only auto deploy specific types of branches automatically,

    For instance, any build that comes from our master branch, should get auto deployed as far up the chain as possible, including production for continuous deployment. Or a hotfix branch should get auto deployed to a QA environment, while a feature branch should only be created and deployed manually.

    If you exposed some powershell or other script with access to the…

    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

    1 comment  ·  Installation  ·  Admin →
  5. Often times various components that make up a 'whole' project can exist at different version numbers. A WebApi project perhaps, a UI project, a SQL Database project. The three of these things together comprise a single solution. It would be nice to have component based projects (as currently implemented) and then to have a sort of parent/solution container.. so that for the container, I can click a button and bam, all sub-projects get deployed.. or, if I want, I just click a button and release individual pieces of that whole project.

    3 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

  6. I'm working in an environment where web servers are sitting in a DMZ that only allows incoming HTTP traffic - no outgoing traffic at all is permitted without going through numerous administrative channels to get ports opened. I do however have full administrative access to the server only.

    I could deploy a tentacle in this scenario if I had some kind of web resource that acted as a proxy for a listening tentacle. Octopus would manage the tentacle via <site>/octopus-deploy.axd instead of through the usual listen port.

    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  ·  Installation  ·  Admin →
  7. Disabling a feature from a step should either remove the configuration (clear out the fields) or provide a visual queue that there is configuration that that will affect the step that is not visible.

    I had a step performing an xml transformation. I removed the transformation feature, created a release and deployed but the transformation still occurred. I had to re-add the feature and clear the transformation fields to stop the step from performing it.

    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  ·  Installation  ·  Admin →
  8. What would be ideal is for Octopus Deploy to attain a "PCI-certified" status.

    I don't know whether this would require 2 linked Octopus servers (as suggested elsewhere), or whether it could be accomplished with a single Octopus server. Here's one idea for the latter (it might display my ignorance)...

    1. Switch Octopus into a new "PCI-compliant" mode.

    2. Use a clever permissions strategy to segregate users into either:

      • a ProductionDeployments role, or
      • something else.
    3. Certain target environments would be designated as Production.

    4. Only those in the ProductionDeployments role would be allowed to promote a product version to a production environment. Everyone who…

    3 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. 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  ·  Admin →
  10. We are using multiple servers and want to export/import project steps between them. Right now the environments, machines, roles ..etc must match and the variables gets overwritten to import.

    An option to export/import project steps ONLY (and via GUI) will be greatly appreciated.

    For example, if we have a server for QA, then prosecution, which clearly have different environments ..etc, we want to be able to import/export between these.

    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

    1 comment  ·  Installation  ·  Admin →
  11. Hi

    I'm using Octopus but the one thing i find a potential problem with is the ability to arbitrarily assign a machine to any role i type in.

    I would like to see the ability to have a 'machine' roles 'table' that needs to be setup before any machines can be added to a role.

    That way, machine roles can be managed (CRUD functionality).

    Thanks!

    4 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. On the tentacle manager screen, we currently see the 'Home directory' and 'Logs directory'. How about also showing the default 'Application directory' to which the tentacle deploys?

    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  ·  Installation  ·  Admin →
  13. Unfortunately, I am forced to work with a very slow NuGet feed and the more packages I upload the slower Octopus is at retrieving them when creating a deploy. Fixing the speed of this is out of my control.

    It would be great if you could do some very simple caching to speed this up. Or can you simply limit the number of versions you get from the feed?

    Anything to speed up this up would be fantastic.

    2 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. on the dashboard, if you hover a deploy, you will get more information on that deploy in a little info-box. We would like to see the same behaviour but for the environments. If you hover "dev" it will list you what servers it contains, and a little icon for if it's up and running or disabled/not healthy)

    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  ·  Installation  ·  Admin →
  15. We have a host that controls UAT and production. They manually promote sites by hand currently but are open to something automated that they control.

    Internally we have a CI environment and test server but don't want to give access to the host to our intranet or active directory or expose our octopus deploy to the host.

    We would like to see the state of releases in UAT and production on the same board as our CI release.

    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

    1 comment  ·  Installation  ·  Admin →
  16. It will be really helpful to be able to enable/disable PC/Tentacle environment wide.

    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  ·  Installation  ·  Admin →
  17. We have lots of machines/tentacles with lots of different roles. It would be helpful if we could search all projects that use a given role. This would show us all Octopus projects that are assigned to a given role.

    3 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

  18. I am an administrator and I manage 3 environments DEV/QA/PROD. After I install Tentacle in a prod server, I should be able to add that machine only under production environment.

    One way to do is by having a different thumbprint for each of the environments.

    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

  19. We are working with projects as templates and thus almost always start from a template which we clone.

    To reduce the manual steps involved in the process it would be nice to be able to clone a project using octo.exe

    11 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  ·  Admin →
  20. We've had a couple issues where something in the Queue froze and stopped all future deployments. When it's a project that seizes up, we can cancel it, however when it is an internal task (e.g. Tentacle Health Check), the only way to fix the issue is go into Raven Studio. I know I can see the completed tasks, but I would like to be able to view the queue, and perhaps cancel jobs from there as well.

    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  ·  Installation  ·  Admin →