General

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. Scoped Tenant Variable

    Here's the scenario:

    I have a web application that is being used across 12 countries.

    Every country has its own environment, databases.

    While the current Octopus allow us to create tenant variable like Alias, it is useful but when it comes to scope variable this feature is not there.

    Example: Tenant A has a different Database credential for UAT and PROD. Currently the workaround is to create 2 tenant variable, like UAT Database, PROD Database.

    It would be useful to have this scoped as well.

    14 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. new user role\s

    Would it be possible to introduce a new user role\s for adding\editing\removing steps from a process?

    We would like developers to be able to add a new step but not delete or edit existing steps.

    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 →
  11. Expand All button in Task Log

    In Task Log screen, we need to click on "+" button to expand the sections for each section. A "Expand All" button would be useful when you want to expand all sections at once but do not want the verbosity in Raw tab.

    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 →
  12. Highlight the variable Snapshot difference while updating the release snapshot

    Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done…

    78 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 →
  13. Obfuscate sensitive variables in deployment log in variable substitution

    We're using various steps for deployment ('Deploy a package', 'Deploy to IIS') which both have variable substitution options to substitute variables in Web.config/App.config.

    During deployment, i've noticed that these substitutions are logged. However, sometimes i see that our sensitive variables are being logged here at 'verbose' level. Other sensitive (and also non-sensitive) variables are obfuscated.

    It seems that the deployment process decides by itself based on the name of the variable. In my opinion, the sensitive option of the variabel should be considered here as well.

    An example of what we've got currently:
    We've got an appsetting in our app.config,…

    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. Terraform support for SSH Workers

    Currently the built in terraform steps only support Windows workers. It would be good if the steps were platform agnostic and able to run on any worker.

    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 →
  15. Production Deployment Notification

    I would like to receive an email notification when a PRODUCTION deployment is taking place.

    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 →
  16. Tag AWS ECR (Elastic Container Registry) images from a feed with a deployment tag

    Amazon's ECR (Elastic Container Registry) is a docker-compatible registry that you can configure as a first-class package feed in Octopus. Part of the ECR product (in AWS) is to set up lifecycle policies so it can automatically delete old images (since it takes up space for each image). This is a similar feature that Octopus offers on its own built-in package registry, but the ECR is obviously an external registry so the purging has to managed by AWS (and no Octopus). But ECR has no way of knowing which images are used (so they won't get deleted), except if you…

    2 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. Approval Role

    I'm not seeing things specifically, but it would be nice if there was a role which was Release Approval Only Role. To allow a certain set of users to just approval releases to go to the next environment in the life cycle.

    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 →
  18. terraform

    Terraform step templates for Azure deploys. Currently only AWS is supported in Octopus included step templates. It seems like an easy addition to the existing functionality

    12 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 →
  19. Rolling deployment parallelism per role

    We have an service environment right now that consists of two data centers that each contains 3 servers that host the services. These services hosts host 100+ services each and each server is hosting exactly one instance of each service; so they are in effect mirrored.

    When we deploy to these servers, we do it one data center at a time. Since there are so many services per server, we can’t just remove the server from the load balancer. Also since we do round robin load balancing and want to have zero downtime and keep consistency in our responses during…

    3 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 →
  20. Display channel description when creating a new release

    The selected channel's description should be displayed when creating a new release, otherwise a user may miss important information that is not fully conveyed by the channel's name. Currently a user would have to navigate to the separate channels tab to see this, which breaks the UI flow and which they may not necessarily do.

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

Feedback and Knowledge Base