General

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. Filter Environments shown in each Project Group on the Dashboard

    Filter the environments show in each project group on the dashboard. Only environments included in the lifecycles/channels for each project in the project group should be shown.

    We have many environments but most are only used by a few project groups. Some project groups only deploy to a single environment. This requires us to horizontally scroll far to the right past environments which aren't capable of being deployed to in order to see what is 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 →
  7. 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 →
  8. Allow segregated package repositories

    In a lot of companies there is a clear separation between development packages and packages approved for production. Systems like Sonatype Nexus and Artifactory provide hugely powerful examples of these catering for a wide variety of requirements, but in most cases you need a simple set of requirements:
    * The ability to push packages to one (dev) repo
    * The ability to promote packages to another (prod) repo
    * The ability to force certain environments to pick from a certain repo

    This should be a relatively simple improvement to Octopus' very awesome but very simple package management capabilities.

    3 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. Set Rolling Deployment Window Size with a variable

    Should we implement the ability to configure a Rolling Deployment's Window Size via variable? Adding this feature would allow the window size to be controlled dynamically after release creation.

    Feel free to add any comments or thoughts below.

    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 →
  10. Cleanup Application folder for versions that have no corresponding release any more

    We noticed that the automatic cleanup of C:\Octopus\Applications apparently does not cleanup versions where no corresponding release exists any more (e.g. because we only played around and afterwards deleted the release without manually cleanup up the C:\Octopus\Applications folder).

    It would be really cool if the cleanup would also cleanup versions for which there is no corresponding release.

    3 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 →
  11. Allow machine policies to be set for Azure WebApps

    I would like to be able to customize the Health Check of Azure WebApps deployment targets. For example I would expose an endpoint `/health` that must be queried on an ~hourly basis. In the case of a Tentacle this is possible using Machine Policies, but I can't assign one to a Azure WebApp deployment target.

    3 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. Re-label or remove the "Automatically run configuration transformation files" checkbox

    The label of this checkbox is slightly confusing - it led me to believe there was a manual process for applying transforms too. Given that when this box is ticked, a default set of transforms are applied, and when it is not ticked, those default transforms don't run (but transforms listed in the additional box DO run) and the process is always automatic, a label like "Apply the default set of transforms built into octopus" might be better. Alternatively, consider removing the checkbox entirely and just putting the pre-programmed defaults (Web.Release.config => Web.Config, Web.#{Octopus.Environment.Name}.config =>Web.Config) into the box as a…

    3 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 →
  16. Octopus Server API versions & related components - Compatibility Table

    Firstly, thanks for working on and improving upon an already great product. Now to the feedback at hand, I am currently investigating making use of the .NET Octopus.Client within a project to manage the octopus deploy server. As part of that investigation I was trying to gain a better grasp of the compatibility of the various Octopus Deploy (OD) server versions and the related components. That led me to the current page, https://octopus.com/docs/api-and-integration/compatibility which though useful at first glance, it was not clearly defined upon further investigation. Since I'm looking to use the Octopus.Client component let's example some questions for…

    3 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. Deploying files

    The only thing Octopus should do is deploy files, correct?
    Can we just deploy files with a polling tentacle without an issue?
    Fair enough I am deploying to sites with low connection speeds, but even windows remote desktop connect can copy the files without an issue but Octopus can't!!!!!?
    Can we just do that?

    But thank you, even dow it sucks at polling it still remains the BEST, great program awesome way for deployments.

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