Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Ability to specify version of PowerShell during script execution.

    Currently tentacles use the default path, which is great most of the time! You could currently call PowerShell with a command line parameter but any scripts have to completely re-written to work this way, which defeats the simplicity of Ocotopus!

    http://technet.microsoft.com/en-us/library/hh847899.aspx

    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  ·  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. Via: https://github.com/OctopusDeploy/Issues/issues/1041

    It would be fantastic if there was a static URL to that last successful deployment. E.g. a (web) url like app#/projects/project-name/environment/previousversion

    This would make it trivial to point our deployment team to the correct page for a rollback.

    I realize that there are currently no static links to the current release by environment so this may be a separate enhancement.

    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

    0 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)
  3. OctoPack is a build time tool not a project dependency.
    Adding the developmentDependency attribute will allow other tooling understand this.

    see http://nuget.codeplex.com/workitem/1956 for more info on developmentDependency attribute.

    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

    0 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)
    1. After deployment, create and store a small hash of all files extracted from the package. It should run at the end so that it includes any changes made to configuration files, and should only include files that existed in the original package.
    2. During a health check, report whether any files on disk have changed when compared to the original hashes

    The second part should be optional (or perhaps a different task that runs just daily and that can be disabled) since it can consume extra resources.

    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  ·  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. we are estimating that in few months we will have 200 projects in octopus. This would be a nightmare to keep track both in dashboard and in all projects view.
    I would suggest to be able to filter projects be name, or seach for projects.
    Moreover it would be nice to have an option for a more compact project view (like a simple grid with thin rows)

    It seems that current ui design for projects is only working for a relatively small amount of projects.

    thanks

    7 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  ·  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. "Deploy to a specific subset of machines" field should be an dialog with a list of servers and checkboxes. You should be able to "Select All/None".

    It will cover the cases when you have environment with many machines where you need to install all except one/two.

    Now, you need to select it one by one, which may be pretty annoying when dealing with environment of dozens servers.

    It does exists in some competitors products.

    thanks.

    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  ·  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. When I have many Queued tasks and then go to the Tasks page, I have to scroll down to see the Active task. I suggest the Tasks page be grouped by Active task, then Queued tasks, then Recent tasks.

    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  ·  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)
  7. If I have a WCF endpoint in my .config file, and an Octopus variable with a name that matches the name of my contract, auto-replace it (just like appSettings/connectionStrings replacement).

    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

    2 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)
  8. Currently when we need some tools (sqlpackage.exe, sqlcmd.exe, some DLL...) to be present on the tentacle for our deployment script we create a NuGet package with the tool and have to manually add a Deploy Package step for each tool to deploy it in a standard path so we can then use them from PowerShell scripts/

    It would be great to have a tool library:
    - we create a tool by specifying a NuGet package, a name and a description
    - in each steps (template steps or process steps) we can specify which tools is needed
    - when deploying the…

    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

    0 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)
  9. I have a project in Octopus that can only be deployed to 2 of my 5 environments. But since the environments are for all projects and I made a mistake once to deploy it to one of the un-deployable environments now my dashboard show that version XXX is in that environment (but it's dark yellow since there were no processes for it). It would be a nice feature to configure allowed environments per project.

    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

    0 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)
  10. We intend using OD for multiple clients which have multiple environments each. It would be nice to be able to scope environments, roles etc to one or more specific projects or to have some kind of client scope.

    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

    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)
  11. When creating a release the user is given three options to configure a package version for each step, Latest, Last, Specifc. The default is Lastest.

    Allow the user to specify the package version default behaviour in each step.

    The user could then ensure a package stays at a particular version without having to set the version each time they create a 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

    0 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)
  12. https://github.com/OctopusDeploy/Issues/issues/662

    When setting up a user in a team you can currently set Projects and Environments on the team, but if I setup a team as "Project Deployer" they do also get view access for all environments and machines, though they cannot do anything more then viewing.

    I would very much appreciate if you could add in a "Roles" field as well in the team setup, so that the users in the team only can see the Environments (Machines) with the same Role.
    As default (If no Roles are specified) all Environments (Machines) should be visible.

    12 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  ·  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. We need the ability to view all the variables in a release snapshot including those coming from step templates

    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  ·  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. The .net SessionState provider uses the IIS site ID as part of the key used to access a session when working in out of process mode. If you are running a site in a webfarm these ID's need to be kept in sync with each other otherwise as requests bounce around the servers a different session will be accessed.

    It's probably not a big issue as more complex set up's will probably be using custom set up scripts but I think it'd be a very easy feature to add.

    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

    0 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)
  15. In places where we show NuGet packages (release page, library), show extra metadata like the project URL and icon.

    http://help.octopusdeploy.com/discussions/questions/2383

    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

    1 comment  ·  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. As we continue to find more ways to use Octopus, we've increased our usage of the roles feature. This serves the dual purpose of filtering variables/steps as well as being visual indicators on machine configurations when viewing the Environments page. It would be really helpful if we could assign a custom color to each role to make items stand out and faster to identity beyond using a naming convention. Even better would be the option to also assign an icon, which I think Font Awesome would be a great option. http://fortawesome.github.io/Font-Awesome/icons/

    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

    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)
  17. https://github.com/OctopusDeploy/Issues/issues/863

    Octopus Manager and Tentacle Manager should make it easy to configure the Windows Service to run under a custom user account.

    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  ·  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. Have an entry field that accepts the same sort of content as is seen in the transform window here: https://webconfigtransformationtester.apphb.com
    as well as maybe a file pattern/name to match the transformation to.

    This way one can avoid building multiple instances of an application, one for each build configuration (environment), transforms don't happen at build time and can take place as part of a deployment.

    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

    0 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)
  19. I would be really cool if there was a deployment step for AppHarbor.

    AppHarbor has a build API that will let you pass the SHA you want built.

    Not sure how to best implement it, but having Octo control my AppHarbor
    deploys would def be nice.

    Source: UserVoice Support Ticket 281

    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

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