General

I suggest you...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

    12 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. Performing dry run with octo.exe push (--whatif)

    Looking at the documentation for “octo.exe push” (https://octopus.com/docs/api-and-integration/octo.exe-command-line/push), but I cannot see any option to perform a dry run. The ‘create-release’ command has a ‘whatif’ param, and it would be really handy to have this on the ‘push’ command as well.

    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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. When deploying project containing Deploy Release step, allow previewing steps and excluding machines from child deployments

    Currently when deploying a project containing one or more Deploy Release steps (https://octopus.com/docs/deployment-process/coordinating-multiple-projects/deploy-release-step), there is no ability to preview the deployment steps that will be executed in the child deployment, nor the ability to exclude machines from the child deployment.

    It would be nice to surface this information on the create-deployment page of the parent project.

    34 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 →
  17. 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.

    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. Support multi-package deploy steps

    Allow package deploy steps to select multiple packages that are deployed in the selected order (with the ability to change the order). We have a website where we deploy a clean copy of a vendors files (makes upgrades easier), then we overlay different 3rd party modules and our solution into the same folder. These packages together create a whole website.

    35 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 →
  19. Deploy to Service Fabric

    The 'Deploy to Service Fabric' process does not provide all the available security mode options available in Service Fabric, we are doing a POC around an on-premise SF cluster using a gMSA which the Fabric will run under the context of and Windows Identities to allow client-to-node communication. the option for using Windows Credentials (in this case it would be the Windows Service Account which Octopus is running under the context of) to connect to the cluster is not available! i.e.

    Connect-ServiceFabricCluster -ConnectionEndpoint <cluster-domain-name | server hostname>:19000 -WindowsCredential

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Mapping environments on library variable sets

    The issue I run into is the following:

    Product A: offers an API on several environments DEV/TST/ACC/PRD

    Product B: wants to use ProductA-TST on DEV/TST/QA
    wants to use ProductA-PRD on ACC/PRD

    I want the ability to make a library set of varables from product A so any other product I have can easily link to the API, without having to keep track of a url in the other projects variables. So if Product A changes the URL, everyone is automatically updated.

    But I might have more environments in other projects or want to map multiple environments to 1 environment of…

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

Feedback and Knowledge Base