Product Feedback

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Step for creating or updating a service in a Docker Swarm

    As a DevOps Engineer, I would like to be able to create a new service, or update an existing service in a Docker Swarm using an Octopus Step.
    For this to work for us, we would need to assign or alter Networks, Secrets, Environment Variables, and HRM Labels.
    The commands involved would be "docker service create" and "docker service update"

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Project Variable Filter for Tenants

    I was wondering if there has been any thought into making a project variable filter/tag system by tenant. It seems like over time the project variable list could get quite long for large implementations. It would be nice if when setting up a project variable you could tag a tenant or tenants that it applies to. That way it would only show for those tenants. Otherwise it would take the default value for the other tenants. Or something to that effect.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Octopus Deploy Status Icon/Widget

    The ability to hot-link to publicly accessible widgets/icons that show the last Octopus deploy status for a particular project and it's environment. Very similar to how build tools do it (like TC Server, Jenkins, VSTS and Travis CI). See an example here: https://docs.travis-ci.com/user/status-images/

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support ZIP file for external feeds

    External feeds currently only support NuGet package feeds. It would be good to support ZIP feeds, to support integration with products like Artifactory.

    69 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Create an official Slack app

    Whilst it is possible to integrate Slack in to Octopus using script steps at the moment, there are now some great possibilities with Slack Apps: https://slackhq.com/get-more-done-with-message-buttons-5fa5b283a59#.uw51h0tvy Steps like manual authorisation steps could be actioned through Slack, each step in a deployment could have an "output result to Slack" option etc.

    64 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. AWS Elastic Beanstalk support

    Fully support of Elastic Beanstalk for deploying HA web applications that make use of the built in feature set plus the rich features provided. H octopus.

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. NPM and Bower package support

    It would be great if Octopus would also support external NPM and Bower feeds instead of NuGet or the internal Octopus feed.

    Background:
    Octopus does a great job when deploying Windows software based on NuGet packages. As described in #2183 the NuGet package format isn't always suitable. Octopus now supports to store arbitrary archives in the internal Octopus feed. Although this might be useful in some cases, you don't want Octopus to become a package repository. Octopus can also fetch from TeamCity, but TeamCity is also limited to a NuGet only feed and should be responsible to build software, not…

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Display currently deployed versions in badges

    I suggest you add functionality to display a badge showing the currently deployed version of a specific project.

    In a similar way to http://shields.io/

    In the UI you would show the link to use that would be an endpoint that displays a PNG or similar containing the project name, environment and currently deployed version.

    75 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Accumulate TFS Work Items for release notes in the TFS extension

    With the new way of pushing packages and releases to Octopus in VSTS vNext, using the new Octopus task, it looks like each release can only go back in time to the previous build. So, if there are many releases for a "2.0" release, it seems all those work items would be sprinkled among all the dev/test builds and releases that had to happen to get to the "2.0" state. What i really want is the ability to accumulate work items since "1.0" so that all the new features and bug fixes that have happened for "2.0" show up on…

    33 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add AWS CodeDeploy as a Deployment Target

    Add AWS CodeDeploy as a Octopus Deploy Target (similar to the Offline Package Drop)

    We;re currently using a combination of Tentacles and CodeDeploy. Tentacles are great for debugging deployment issues, but CodeDeploy is simpler to integrate with AWS AutoScaling etc. It also allows cross-region deployments without the need for VPNs or having to keep multiple Octopus server configs in sync.

    We're currently doing this using the following steps:

    • Offline Package drop
    • Some script file renaming and adding an AppSpec.yml file
    • Uploading to S3
    • Calling the CodeDeploy APIs to trigger and monitor the deployment
    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Ability to update releases from Octo.exe

    Just like in the UI, it might be useful for some users to update releases from Octo.exe for things like:

    • Package(s) Version(s)
    • Release Notes
    • Release Version

    Worth considering if it should also update the Release's variables (in the UI that functionality is set in a dedicated button)

    Possible commands could be:

    Octo.exe Update-release
    Octo.exe Create-Release --updateExisting

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  13. Merging/managing Library Variable Sets

    atm we are working with multipule people on multipule projects without any common agreement about naming convention and categorys. the problem is wild growth of varibales. The more we use octopus the more we see overlap of commonly used values. if u want to merge is is dumb work copy pasting form one side to the other side.

    the feature i realy like to see is variable manager:
    - var set names are labels/category
    - filter option on labels/category
    - filter not used
    - overview where the variable is used in projects

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Sales Force Integration with Octopus Deploy

    1. Enable File System deployments - Deployments to be carried from a file share 2.Possibility to automate the sales force Continuous Delivery feature using Octopus Deploy.
    34 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  15. Make the API or an API abstraction that sucks less

    After using Octopus Deploy for the last 4 years. I love the product, but I hate using the API, The current octo.client pretty much mirrors the rest api and using it is cumbersome and clunky. We have gone down the path of 100% automation and because of it, we have run into edges of the api where we end up hard coding guids for variable identification into our code base. Our current path has lead us down trying to automate the setup of tenants and setting their variables. Its painful and we have spent a lot of hours trying to…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  16. Define dependencies on PS modules/scripts hosted on PowershellGallery.com (or similar source) in script modules and templates.

    Allow defined dependencies on powershell modules or scripts (and versions) from a nuget compatible source such as PowershellGallery.com. Allow these dependency definitions anywhere powershell is used in Octopus. Tentacle should install the scripts/modules into the Powershell Session prior to performing any release steps.

    This would allow for more complex powershell modules to be made available for Octopus to use, as well as a means for keeping the PS code up to date outside of Octopus.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add email attachment support

    An easy way to attach deployment artifacts would complement this feature very well.

    105 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Custom Release Properties Like Team City Build Id

    I'd like to capture some additional fields along side every release.

    For example, every release of my project, should have a corresponding:

    • Team City Build Number
    • Team City Build Type Id
    • Team City Build Id

    At the time of creating a release in Octopus, if done through the octopus UI - these values would be prompted for.

    If done through Octo.exe then the create release command should have the ability to set these release specific property values.

    The reason this is useful is because:

    1. The Octopus Release number no longer has to match the Team City build number in order…
    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support for app settings from Application Pool in IIS

    We currently want to set features like the number of worker processes. It would be good to be able to set these up from Octopus instead of powershell.

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Provide a hash of sensitive variables so we can determine if they have changed

    I'm working on code for a Terraform module for modifying Octopus Deploy configuration, and when we have variables with the type set to Sensitive (or IsSensitive=true), Octopus understandably does not return the value of the variable.

    However, this means it is impossible to determine if the value is set correctly.

    One workaround would be to provide a hash (even a salted hash) of the value when it is set. Then we could compare our hash against the hash in the API, and if they don't match then update the sensitive variable.

    E.g. A new field called ValueHash which is sha1(Name

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base