General

  1. Kubernetes Ingress doesn't allow to configure TLS

    Allow kubernetes ingress to specify TLS configuration.

    15 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 →
  2. Allow defining an explicit order for prompted variables

    At the moment (at least to my knowledge) the order in which prompted variables are shown is dependent on the variable name (ordered alphabetically).

    It would be really cool if there was a possibility to give prompted variables an explicit order so that we can control in which order they appear in a simpler manner. For example it would be cool if one could just set a "priority" value for a prompted variable. This "priority" could be an integer and the prompts could then be ordered by this priority in descending order.

    Unfortunately giving them names to achieve the correct…

    13 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 →
  3. Allow kubernetes & helm steps to override the target provided namespace

    Although the kubernetes target type defines its namespace, there may be some situations where a different namespace should be used for a given step

    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. Support Powershell scripts on Linux

    Now that Powershell is cross-platform, please support running Powershell scripts on Linux

    33 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 →
  5. Show variable snapshot differences in release screen

    Sometimes when deploying, the user receives this message:

    "For consistency, this deployment will use a snapshot of the variables and deployment process that was taken when the release was created, which does not include the latest changes that have been made to the project. A changed process can only be incorporated by creating a new release (this one may be renamed if desired). Variables can be updated via the release page, clicking Show to show the variables from the snapshot, and clicking the Update variables button."

    It would be great to be able to tell the user exactly what changed,…

    217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow cloning of tenants

    It should be possible to clone a tenant including it's current configuration in a similar way to that you can clone whole projects.
    Tenants tend to be similarly configured with only minor changes to each one so it would save time rather than having to configure each one from scratch.

    144 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 →
  7. Add Let's Encrypt automation to OD server

    Ensuring certificates for the OD server are up to date are a little annoying. It would be awesome if the OD server could support renewing it's own hosting certificate with Let's Encrypt.

    I've had a stab at creating custom steps to do this. The main issue is domain validation (DV). DNS validation often requires manual intervention and OD server controls http (see discussion at https://community.letsencrypt.org/t/domain-validation/26512 ).

    The only way I see this really progressing forward is if OD server supports Let's Encrypt in the server as a maintanence task as it would be able to respond to http DV requests.…

    16 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. Allow project dependencies - so deploying one project would automatically deploy all dependent projects

    We have many dependencies between our projects. So for example we have cross database dependencies which mean that a particular version of the database must be installed prior to another version. Similarly we have base services that are required by all others that must be installed first. There is currently no way of telling Octopus that one project depends upon another.

    We could create one great big Octopus deployment with all the steps in it to deploy the TFS projects/libraries in the correct order. But this would be very complicated because of the large number of dependencies.

    It would be…

    317 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Improve variables UI

    The variables view is very basic and it generally needs improving since it quickly gets hard to use when you begin adding lots of variables.


    1. You have to add the same variable name for multiple environments and the ordering of environments is not the same. This is error prone and makes the list hard to parse.

    2. There is no description for variables so you need to add very long names sometimes. This has already been covered, but I added it for completeness. See https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6079578-enhance-the-variable-maintenance-screen-with-varia

    3. There can be different types of variables which are changed for different reasons. It would be…
    991 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    47 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks everyone for your suggestions. We are happy to announce that a new version of the Variable Editor has shipped in Octopus 4.0! See https://octopus.com/blog/octopus-release-4-0 for more details.

    In this first release, we have focused on providing a great variable editing experience, which we hope you will love! Although we haven’t yet been able to implement all of your great suggestions, we have been able to build an extensible variable editor that we will continue to improve in future.

  10. C# Script in script modules

    We need to use C# code as script in the script modules

    229 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. Improve Add Step functionality

    We are working on making the Add Step functionality much better. The idea is to show built-in steps, community step templates (from http://library.octopus.com/) and custom step templates in one central location. Please let us know what you think by leaving your comment below.

    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 →
  12. Support v3 NuGet Feeds

    Currently there are a few feeds that support v3 NuGet feeds. Octopus currently does not support linking directly to the JSON file. Please add votes and feedback on why you would like this supported by the few feeds that currently do.

    Please note that this is not about Octopus updating its NuGet library to support things like SemVer 2.0 which is planned. This is strictly when you add an external feed to retrieve external packages.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Find variable usage across all projects and variable sets

    When working with library variable sets used in many projects with many steps it is cumbersome to figure out where a given variable is used.

    When updating a deployment process, certain tasks become very difficult, such as:
    -Renaming or deleting a variable
    -Checking validity of a newly-updated variable value across all usages

    With a "find all" feature these tasks would be much simpler (plus I'm sure there would be wider-reaching benefits).

    343 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    Happy to announce we’ve added a usage tab to the variable set page in 2019.5.4, where you can view which projects and releases are using a variable set. While this does not cover all suggestions below, we are confident that this goes a long way to solving the problem.

    Finding the usages of individual variables is something that is a lot more complex than it sounds, and we are unlikely to implement. Many variables usages are embedded in strings, or even in files sourced from packages, meaning any results we displayed would be incomplete.

    If you think we’ve misinterpreted this suggestion, please raise a new suggestion with a bit more detail about the use case, and let us know in the comments below.

  14. Automatic release creation to allow packages with variables in IDs

    Currently the automatic release creation feature does not resolve variables when looking if a package is used in a project set for automatic release creation. You can only use package IDs with static names.

    It would be great if you could use variables in the package ID and have them resolved when the package is pushed.

    Source: http://help.octopusdeploy.com/discussions/problems/28069

    217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Viewing variables for a release should evaluate nested variables

    I regularly use nested variables to minimise the number of variable changes I must make between environments. Consider something like this:

    data source=#{Database.Server};initial catalog=#{Database.Name};#{Database.Auth};

    This allows me to just specify simple variables for the DB server, the DB name and the type of auth being used, without having to construct a connectionstring every time (and probably making the odd mistake).

    It would be great if I could see the fully-evaluated variables when i click "Show variables" on a release - or at least have a switch between the raw variables and evaluated variables.

    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 →
  16. Add an option to only create a binding in IIS if it does not already exist

    We would really like to have an option to leave bindings alone in IIS if they already exist.

    I configure a single binding as a templated deployment step. I would like octopus to automatically create the IIS app and bindings in the event the app pool and website doesn't exist - but if it does already exist I'd prefer it not to reconfigure the bindings.

    This is useful when we create website aliases for production environments which don't fit the normal QA and UAT environment setup (but they happen to use the same steps).

    Best would be a checkbox:

    "Overwrite…

    148 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 →
  17. Add support for Python scripting.

    It would be great to see Python listed as a script step. Python is heavily utilized in the infrastructure space, AWS, F5, Citrix, VMware and will help to drive full automation further up the stack.

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Skippable Steps by default

    Is there a way to make a step skippable by default?

    I know the request might sound strange, but we're run into a scenario where a step may need to be run in certain scenarios. Obviously the user could skip the step by hand each time, but considering the default is to run each step, we're trying to avoid a scenario where someone doesn't look and just runs the default. This would make it very apparent that the step isn't run (as it will be marked as skipped) and force the user to look into it with more detail.

    Odd…

    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for voting on this. I think that the “channels” feature we added in 3.3 is a solution to this scenario – you could set up channels like “major release (all steps)” and “tiny bugfix (run 1 step)”.

  19. Virtual Dashboard

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

    It'd be awesome if clicking on a Project Group in the Projects drop down took you to a dashboard that ONLY listed the projects under that group.

    Better if an admin user can still hide/show projects in those virtual dashboard for everyone

    Even better if each user could configure a custom version of that dashboard for themselves

    132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Compliance with latest SemVer

    Would like that OD is in compliance with the latest version of SemVer, so that the Pre-Release flag, and Build Metadata can be utilized in the release number.

    8 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 →
← Previous 1 3 4 5 14 15
  • Don't see your idea?

Feedback and Knowledge Base