General

  1. Allow the use of F# script (.fsx) in place of Powershell/ScriptCS

    Please enable the option to use .fsx files (F# script) in places where Powershell is currently used.

    It's concise syntax make it perfect for scripting, it's a darn sight easier to pick up than Powershell, comes with a fantastic REPL and as a bonus the popular F# library "FAKE" provides functions for all manner of deployment tasks and operations.

    275 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add a way to pass parameters when using scripts in packages

    In Octopus 3.3 the option to execute a script inside of a package was added, along with a field to declare the name/path of the script.

    It might be good to add an extra field (or another way) to pass parameters to these scripts, just like other tools like TeamCity, AppVeyor or TFS have.

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Different icons/images for the new TFS build steps

    Currently the new build steps in TFS 2015 for octopus, have the same image/icon and it's not easy to identify which type of step it is.

    I suggest create different icons for each type:

    - Package Application
    - Push Packages to Octopus
    - Create Octopus Release
    - Deploy Octopus Release

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Azure Resource Manager Key Vault support

    This feature allows users store credentials in a Key Vault (like a password manager) in azure, and the reference those keys from their ARM templates.

    This was introduced in the Azure SDK 2.9 in 3/31/1026: https://azure.microsoft.com/en-gb/blog/keyvault-support-for-arm-templates/

    At the current Octopus version (3.3.6), this doesn't work. It'll definitely be handy to support this feature.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Use samAccountName and not userPrincipalName for user creation

    Currently it looks like Octopus uses the userPrincipalName when syncing/authenticating users from AD. Since the UPN may change (for instance when migrating users to Office365....), users will suddenly end up with a new account in Octopus when loggin in using Windows Auth.

    Using the samAccountName (as is more common) should allow users to keep their Octopus account/profile in situations like this.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Automatic Kerberos/NTLM Login on page visit

    I see this question - http://help.octopusdeploy.com/discussions/questions/8083-automatic-user-login but this indicates it would go through something like OAuth. The already built in Kerberos/NTLM integration is really nice and I'm not sure why there isn't already an option to have the octopus deploy site initiate an auth challenge on page load rather then when you click the button. This is how Klondike works out of the box and TeamCity calls this "Forced Protocols." Forced protocols is a bad name though as it gives you the option to log out and login as another user - which is useful for keeping separate accounts one…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Audit Viewer Role

    As an IT compliance officer I need to be able to view the Audit page in Octopus Deploy but I don’t want to be able to make changes to the Octopus System. Please create an “Audit Viewer” role that has appropriate access to the Audit page separate from AdministerSystem

    1 vote
    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 →
  8. Comments on each Variable

    Please add a a comments field beside each variable. There are times when an explanation would be extremely valuable.

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. more granular team/project roles

    It would be nice if there was a way to expand the roles for a team on a per environment basis. For example I'd like I'd like for the developer team to be able to create and edit variables in the production scope, but not be able to deploy there.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Ability to set Application Pool CLR to No Managed Code

    As of Octopus 3.3, the 2 options are:

    - 2.0 (for .Net 2.0 and 3.5)
    - 4.0 (for .Net 4.0 and 4.5)

    It might be useful to also add the option "No Managed Code"

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add Channel to Dashboard

    I know there a lots of requests to make the dashboard more compact and that you're also working on significant changes to it for the upcoming multi-tenancy release. One thing I don't think I've heard mentioned in either conversation is displaying channel information in the dashboard.

    It's great that when you drill into a project overview you can pretty easily see what feature is in what environment because the channel is listed on the left. It would even better to get this information on the dashboard so you can see at a high level what components are affected by a…

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Dashboard and project pages should show if a project is disabled

    In the project settings there is a "Disable this project" checkbox, when it is checked there should be visual indication in both the Dashboard and in the project header notifying the user of the state.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Output variables for offline drops

    Offline drops don't currently support passing output variables from a deployment package step to another step as part of the same deployment script. Would it be nice to add them?

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

    324 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Remove Mono/Calamari dependency for SSH connections and deployments

    For every process run on SSH, Mono is required on the end target machine as we rely on Calamari for each process. With our recent extensions into other package types, and script types, removing this dependency would give a much larger range of targets and uses. It would allow for greater scripting.

    Adding this suggestion to find from the community how useful this would be - please add comments below about your potential use / server config or really anything relevant to why this is important for you.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Let octo.exe auto-select the right Channel when creating a Release based on Version Rules

    It would be really nice if octo.exe could make an intelligent decision and automatically select the correct Channel for a Release based on the Version Rules.

    As of Octopus Deploy 3.2 you need to explicitly choose a Channel for a Release, unless you intend to use the Default Channel. This doesn't help when you are supporting multiple active versions.

    Whilst this wouldn't work for every situation, it would be brilliant if I'm following a strict versioning convention for my packages and Releases, and configured explicit and independent Version Rules, that octo.exe could pick the right Channel.

    I would imagine octo.exe…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Icon vs Detail list view

    We have a lot of projects 50+ and a lot of hosts 200+ so it's a problem with the big icons (they got even bigger in 3.0)
    hard to get an overview.
    so make a drop-down where we can select Icon or Detail view (like in the explorer)
    Atm there is a lot of mouse wheel scrolling happening to get to the host in the end of the list.

    22 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 →
  17. Mix Domain / Local Accounts

    We have an environment where there are a mixture of employees / vendors who need different levels of access to different resources in Octopus. No problem. However, I've got a mixture, some who have just local accounts in our Gitlab & Octopus environment, and those who have AD accounts because they use Gitlab, Octopus & other resources in our environment. If it were possible select whether an Octopus user authenticates off of AD or local, that would be MOST EXCELLENT!

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Preserve file timestamp when extracting packages

    Many parts of the internet infrastructure use timestamps, but when Octopus extract files from NuGet packages the original timestamps are overwritten with the time of extraction. This causes pain with load-balancers, edge caching, file sync...

    It would be very (very very) nice if Octopus would maintain the original timestamp from the original file upon extraction.

    Source: http://octopus-deploy.tenderapp.com/discussions/problems/17537-timestamp-not-preserved-when-tentacle-unpacks-packages

    Source: https://github.com/OctopusDeploy/Issues/issues/829

    Source: http://help.octopusdeploy.com/discussions/questions/6829-is-it-possible-for-octoexe-or-octopack-to-maintain-last-changed-dates

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support for Azure Service Fabric

    Please support deployments of the new Azure Service Fabric "microservice" architecture platform.

    See http://azure.microsoft.com/en-us/documentation/articles/service-fabric-overview/ for the initial documentation and Channel9 build videos.

    557 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow deployments to target roles that don't exist (yet)

    Presently Octopus assumes the deployment environment must exist before the project is setup - because you can't create a deployment that targets a role that doesn't exist.

    This means that you can get into creating your new deployment, then realize you are blocked from saving, then lose your changes as you a) go and create a role or b) go and talk to the admin (the drop-down won't refresh, so creating the role in a different browser tab doesn't work).

    I think it'd be better if you were just warned if targeting a role that didn't exist, but allowed to…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base