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 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.

    145 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. 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 →
  4. 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 →
  5. 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…)
    8 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.

  6. 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 →
  7. Allow me to choose which environments a project uses / per project environments

    We have multiple projects being deployed to different servers in heterogeneous environments. Some are just test-production, others are dev-test-staging-production. The projects often have completely separate environments.

    It would be beneficial to be able to either choose which environments a project can deploy to, or to be able to set up per-project environments to be able to keep the same names for config transforms. (ex. "Web.Test.cfg" instead of "Web.Test-Product1.cfg")

    Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects.

    8 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 →
  8. promote a whole environment

    We have "major deployments". At this time we have to deploy all our applications (~ 70) at once. So it would be nice to have a possibility to deploy all projects from environment-1 to environment-2

    30 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 →
  9. Set-OctopusVariable to support -IsSensitive flag

    The Set-OctopusVariable (and its counterparts for other scripting languages) should support an -IsSensitive flag such that if a variable is marked as sensitive it will not leak into a log.

    40 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 →
  10. BUG: Allow library variable names to be viewed on one screen

    Ideally variables can be read without expanding the browser to both windows - probably a bug

    Screens:
    https://ufile.io/nf3ps

    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 →
  11. Support for Kubernetes

    The new Docker features debuting in recent versions of Octopus are really promising, and I'm excited by the Docker Compose RFC published late last year.

    Kubernetes is becoming increasingly popular as the production deployment environment of choice for containerised applications. It offers functionality very similar to Azure Service Fabric, in terms of auto-scaling and self-healing of services and applications, but is based around container images rather than zip files.

    442 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Skip deployment steps

    I just updated to the new 4.0.3 version of Octopus. I do NOT like the process to skip deployment steps. It is hard to follow and see what is going on and takes way longer than the older versions. Please change this to something more like the older version where I can see all the steps and easily click on the ones I want to skip.

    One of the people on my team couldn't even figure out how to skip the steps it was such a pain to find.

    6 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. Allow to mark a deployment step as mandatory (un-skippable)

    Right now only manual intervention steps cannot be skipped during a custom deployment. It maybe good to be able to mark any step as unskippable.

    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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base