General

  1. octo.exe pack should support a --exclude= flag (at least when --format=zip)

    The nuspec approach may indeed support excluding files. However the zip approach (--format=zip) doesn't. Per octopus documentation the .zip approach is the recommended way forward. In this light a --exclude option is in order to compensate feature-wise vS the nupkg approach.

    4 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 →
  2. Make target roles variable

    Let target roles be bindable like most other fields.

    22 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 →
  3. Allow variables to be used for Channel Version Rules

    It would be nice if the Channel Version Rules had support for Octopus variables. From a management standpoint, when you have dozens and dozens of deployment steps bound to specific Version Rules, it would make sense to be able to make centralized updates rather than going through all of the various projects, channels, and associated rules in order to make the same update.

    1 vote
    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 →
  4. Allow adding tags for AWS CloudFormation Stacks

    Currently if I were to deploy a CloudFormation template using the AWS CLI I would have the option to specify tags for the stack.

    The tags defined at the stack level propagate to all AWS resources in the stack that support tagging.

    Since our stacks generally correlate to an environment such as 'staging' or 'production' it would be useful to supply an Environment tag to the stack and have this applied to all resources.

    Octopus currently does not allow us to specify the tags for the stack in the 'Deploy an AWS CloudFormation template' step.

    9 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 →
  5. Display operating system version information on the Deployment Targets page

    It would be useful to see what operating system and potentially which .net framework versions are installed on a deployment target. I've got a variety of different server versions and in order to pick a baseline .net framework version I need to work out the oldest OS.

    20 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 →
  6. Compress the Offline Package Drop folder

    I would like it if there would be an option to compress the Package Drop folder on a target location.

    I see it is now possible to deploy it as an artifact in .Zip format.
    But i would like it if we could deploy it to a file share in .Zip format without requiring somebody to manually copy it there.
    Each Offline Package Drop folder contains a Calamari folder that is 45MB unzipped and only 10MB zipped.

    1 vote
    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 →
  7. Exclude process steps when you are creating release

    Exclude process steps when you are creating release not before deploying release. Why?

    We have multiple projects and when we are deploying to higher environments we are actually deploying "wrapper project" which contains releases of projects.

    In each release, we don't always deploy all the projects so we want to exclude them from deploying.

    We know that we can set up "deploy only if the version is greater". But If we exclude some of deploy release steps then we have a better overview of what actually has been deployed.

    We just want to skip boring manually clicking each time before…

    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 →
  8. Show task estimate progress bar/percent on dashboard

    Similar to TeamCity, use historical runtimes of previous deployment steps, to know how to estimate a progress percentage (or ETA left) for the deployment tasks.

    Right now the Dashboard just shows a blue spinner with no progress bar or percentage of completion, so some 10-20 minute tasks I need to click on the activity to see how much its done to see how much is (roughly) left to go.

    3 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 →
  9. Define Manual intervention on an Environment

    I'd like to assign a manual intervention, or "Approval gate", at the environment level, independent of project.

    We have many projects that can be deployed to our environments. The lifecycles these projects can deploy to have a mix of Dev, CI, Test and Production environments. Some important environments require approval before anything can be deployed to them (e.g. QA, PreProd, Production).

    At the moment I have to add manual intervention steps to every project that could be deployed to those environments. I also have to make the intervention steps are conditional based on the environments they're going to (i.e. I…

    9 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. Add "Request Deploy" button

    It would be nice if a deploy could be requested when you don't have permissions. For example our Acceptance and Production environments can only be deployed to by the Release Management team, so it would be nice to be able to Request a deploy from within Octopus for a certain release version.

    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 →
  11. Allow multiple version of 'kubectl'

    Currently Ocotpus only allows for one version of 'kubectl' to be added to the Octopus server. This means that all clusters targeted by Octopus must be running the same version of Kubernetes.

    It would add greater flexibility if we could add multiple versions of 'kubectl' and then choose which version to use within the Kubernetes deployment target.

    3 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 →
  12. New Release Available could take admin to release compare

    As an Octopus Deploy administrator,

    I want to see the changes that would be in my specific upgrade in a single action,

    So that I can be more quickly informed of what changes will occur on upgrade.

    Basically looking for a quick link to this: https://octopus.com/downloads/compare?from=2019.2.4&to=2019.2.7

    As is stands, both of the values in the URL above are visible in the Octopus Deploy UI (relatively close to each other)

    Under

    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 →
  13. 13 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 →
  14. Tenant (Project) variables UI improvement - toggle linked environments

    We have around 50 Tenant project variables that differ per each linked environment (Dev, Test, Uat, Stage, Prod)
    So imagine the current UI, we have to scroll down the list endlessly until we find the variable.
    Tenant variables UI improvement suggestion:
    1. Toggle linked environments project variables- meaning use accordion or panel widget for each linked environment, so when I click on one linked environment I would expect to see the Tenant Variables only for that linked environment. Currently all linked environments variables are displayed.
    app#/tenants/Tenants-61/variables?activeTab=projectVariables

    2. Add filtering / searching for project variables on the same page
    app#/tenants/Tenants-61/variables?activeTab=projectVariables

    4 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 →
  15. Add 'latest' option on Octo.exe -package overrides

    When using Octo.exe's --packageversion to specify a version for all packages, and then --package to override one package, it would be helpful if --package would let you specify 'latest'.

    Example:
    --packageversion 6 --package SomeSinglePackage:latest

    Currently if a script is sending --package SomeSinglePackage:2 and there is a new version, you have to remember to change the script to version 3.

    This scenario occurs when you are trying to release a specific version of your application, but one package is shared across many projects and won't have the same version number as the project being deployed.

    4 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 →
  16. Add Auto-Logout Timeout for Users

    As an administrator of our Octopus server I'd like to assign auto-logout interval for our users after a period of inactivity.

    0 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 →
  17. Specify Service Name in Ingress Host Rule

    Currently, when creating an Ingress Host Rule, you can only specify the "Path" and the "Service port". The Service Name appears to be calculated for you. Why not let the user specify the name?

    One use case where providing the Service Name is critical is when using Ingress Annotations for the AWS ALB Ingress. An action annotation can be provided on the Ingress to tell the ALB Ingress Controller to create a specific action on the ALB. For example, an SSL redirect action. The annotation must be named "alb.ingress.kubernetes.io/actions.my-custom-action-name". Then in the host rule you specify the desired path (for…

    3 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 →
  18. Deployment Pipeline as Code

    I would like to see the "pipeline as code approach" applied to projects. The main idea is to be possible to define the process of a project using a yml file in a source code repository or package.

    139 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Supply a list of project variables for powershell

    Currently in powershell scripts, the only list of variables is $OctopusParameters, but this list includes all the built-in Octopus parameters as well.

    It would be really nice to be able to reference only the variables defined in the current project during a deployment.

    Something like $OctopusProjectVariables

    1 vote
    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. Verify a user's database permissions prior to attempting the database upgrade

    If a user runs an Octopus Deploy installer and has some of the permissions necessary to upgrade the database, but not all, the database can be left in a broken state. Verifying all the permissions are correct before making any changes would prevent this broken state, which is most likely to occur by accident.

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

Feedback and Knowledge Base