General

  1. Machine api permissions

    It would be great if you could give your machines default permissions to call the octopus API. That way I would not need to expose API keys in source control.

    This would be similar to the way AWS supports machine Instance Roles.

    This could be something admins within octopus could setup. Ideally you could specify a set of permissions and apply that to the server. The level of permission you grant the server can be set on a machine by machine basis. This would make interacting with the API far easier.

    2 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. 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/

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. 165 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Quick Navigation shortcut key

    Recently discovered the quick navigation shortcut in TeamCity and use it constantly! Would love to see this feature implemented in Octopus Deploy as well, including the type ahead functionality and arrow keys support, for quick navigation.

    1 vote
    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 →
  6. 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

    7 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 →
  7. Integration with Microsoft Teams

    Microsoft Teams already has a pretty great list of connectors, but one big one is missing... Octopus Deploy!

    I would like to be able to receive messages in a channel when a deployment is complete, or certain events happen.

    222 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    171 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Windows Server 2016 Nano Support

    Support Windows Server 2016 Nano.

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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…

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Channel display improvements

    1) Highlight channel name (make it bold and/or different color) on the project's overview page.

    2) Add channel name to deployment status on Dashboard (next to release number and date).

    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 →
  13. 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…

    6 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 →
  14. USA Support Hours

    I know you are based in Australia, but if there is any way to have some limited support hours in the USA time zones, that would be extremely helpful. It's kind of rough only being able to get maybe one interaction per day with the time zones what they are.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    31 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 →
  16. Version control configuration

    This was originally raised at https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6186352-version-control-of-deployment-scripts and closed as completed with a solution of scripting the import/export tool.

    Raising as a new suggestion as this has come up as few times in support calls and some people have suggested on the original thread that the import/export tool doesn't meet their needs. (Didn't want to reopen the original thread as some people are happy with the provided solution in that thread.)

    "In the Continuous Delivery book, Jez wrote that your deployment scripts should be in source control. After creating some pretty elaborate powershell scripts for Octopus, I have to agree. Losing…

    571 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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…

    83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Cloud Foundry Support (Pivotal)

    We've started looking into handling container deployments with Pivotal Web Services, it'd be great to add Cloud Foundry support as a deployment option, similar to AWS or Azure.

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Certificate pinning of external feeds

    When setting up an external Package Feed we'd like to be able to pin the SSL certificate thumbprint of the external feed to make it even more unlikely we'd accidentally fetch packages from a source through DNS poisoning, redirect or or man-in-the-middle attack.

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

Feedback and Knowledge Base