General

  1. Make "Run on Octopus Server" a separate permission

    As it is now if you can change the deployment process, you can also set scripts to run on the Octopus Server. We want people to be able to change the deployment process, but not to run scripts on the Octopus Server. A permission or feature-toggle to restrict that option would be great.

    24 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. Step for docker package selection

    As of version 3.7.12 it is possible to use the "Transfer package" step and use the selected package on custom steps (e.g. push it to an s3 bucket).

    However, when it comes to docker "packages" the only way to select a docker feed is by using one of the 3 default docker steps.

    It would be nice to have a basic step which would allow us to select only the docker feed and have that step export the image+version (tag) to other steps.

    In my case, this would allow me control the deployment of a specific image using custom templates…

    19 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 →
  3. UI new version - release list without comment

    we do not see anymore the comment on the release list.
    it was helpful to have a small remiinder of difference between versions

    1 vote
    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 →
  4. Add option to mask sensitive variable while typing it in

    While typing in the value of a sensitive variable, the complete value is always visible while typing it in.

    It would be more secure if there is an option to obfuscate the value while typing it in.

    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 →
  5. Allow octo.exe to generate results in machine-readable formats (i.e. JSON/XML)

    octo.exe is a great tool that wraps much of the Octopus Deploy API. It would be great if we could specify a parameter --output-format=json or --output-format=xml to have octo.exe generate its results in a machine-readable format for further scripting (e.g. in an environment where I have an older version of Powershell without access to modules such as Octoposh).

    3 votes
    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. Allow deployment of a project to an environment without any machines in that role

    We have a pretty ephemeral environment in AWS and setup new environments several times a week. Our ELB healthchecks are tied to the web apps we're deploying. This can kind of create a timing or chicken-and-egg problem when we need to deploy a project to a new environment. We have to deploy the app for that box before the ELB kills the instance as unhealthy.

    What I'd like to be able to do is deploy a project to an environment then as new EC2 instances are registered with Octopus we lean on deployment triggers to deploy the software as soon…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Target machines by Tenant in Script Console

    It would be really helpful if I could target a set of tenant machines in the script console.

    Sometimes I want to run a script on the machines allocated to a specific tenant, but right now I need to pick those machines manually. That's OK if all my tenanted machines are named using a convention including the tenant name, but with the public cloud that often isn't the case.

    What would be lovely is if I could choose one or more tenants and have the script console run the script across all the machines those tenants are allocated to.

    Likewise…

    9 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 →
  8. Tenant Comment / Alert

    It would be nice to be able to add notes or an alert to tenants so that we have some warning about release windows or contact people against a tenant.

    2 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 →
  9. Allow scripts to reference NuGet packages

    Allow C# and F# scripts to include references to NuGet packages that are downloaded and referenced before the script is run (see http://scriptcs.net/).

    Preferably the feed could be any defined feed and not just NuGet.org.

    4 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 →
  10. Allow non-tenant and multi-tenant deployments to the same environment

    The new 3.4 Multi-tenancy feature is great. But there is a limitation preventing it for some to use it effectively.

    We have several projects, some have multi-tenant deployments (per client) some others not (tool project, shared services projects etc).

    We deploy all these projects to the same test and staging servers and some as well to production environment. Meaning, the same machine might be used for multi-tenant and non-tenant deployments.

    The current 3.4 release does not allow us to use the same environment/target for both type of projects.

    Workaround as published (setup dummy tenant instance) is a less desirable, as…

    91 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. provide a way to send notifications from failed tasks

    as an admin, i'd like to receive email notification of failed tasks such as health checks or other automated tasks.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Deployment Steps Logic

    It would be nice to have the option to run different steps based on the status of the previous step (failed or completed successfully). Sort of like an If/Else statement. This way, you can roll back changes if a certain step fails within the deployment process.

    4 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. Enable PowerShell Debugging only for particular steps/scripts

    PowerShell debugging feature uses special variable Octopus.Action.PowerShell.DebugMode which only allows to turn script debugging on and off. Any real deployment contains many steps and many scripts, out of which only one particular script is under debugging, not all of them.
    I propose to make DebugMode selective.
    One way to achieve it would be to use special variable to configure step name (or a list of step names) where scripts run in debug mode.
    Another way (may be combined with the first) is to let PowerShell scripts to invoke debug break explicitly, exactly where and when it is needed.

    3 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. Expand the size of defect description box and allow for hyperlinks

    As part of my TeamCity builds I like to check if a build that ran a deployment has passed/failed (because sometimes a deployment has suceeded but tests run afterwards in TeamCity have failed), and if it has failed then raise a defect via the Octopus API. I like to add the name and link to the build in the defect description.

    However, the the max length of the defect description box shortens the message posted. It would be great to see this increased.

    Furthermore, if links could be supported somehow then users could click on the link to take them…

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  15. 57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback. Sorry this took so long to action.

    For the v4 release, we added the time to the title/hover text of this label (which you can use now), but you’ve all raised good reasons about why the time should be shown directly in these deployment/task cells.

    Time will be included in the next 2018.5.2 patch release for the dashboard / task cells, shipping early next week.

  16. Please have a copy of your W9 on your website.

    And please leave a support or contact form so that we can reach out to you with non-technical questions also.

    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 →
  17. Put the SAVE button in the same location on every page instead of upper right of bottom left.

    The SAVE button is in the bottom left on the deploy process config page and upper right for the variables page.

    8 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 →
  18. Enable triggering deploy for entire group

    When you got a lot of microservices inside a group, one click to start deployment for all of them in their defaults lifecycle

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. License Screen - Add Summary

    Add a simple summary to the license screen showing how many projects / users / deployment targets are "used" to make it easier to see how much capacity is left in the license and where the capacity is used.

    94 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 →
  20. Certificate Management

    We are working on a feature to allow storage and management of X509 Certificates within Octopus.

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

    If you have any comments or suggestions, please post them to the GitHub issue.

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

Feedback and Knowledge Base