General

  1. 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…

    555 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Default release notes for release created from package push

    When a release is automatically created from a package push to the private NuGet feed, it would be handy if the release notes from the release was generated from the combination of release notes in each of the packages in the release.

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

    199 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 →
  4. Add email attachment support

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

    184 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  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.

    153 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 →
  6. 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.

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

    134 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. 120 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Integrate Octopus deploy project variables with Azure Key Vault

    So sensitive project variables will be referenced from Azure Key Vault instead of being stored in octopus.

    https://azure.microsoft.com/en-us/services/key-vault

    3357461 - 'Azure Resource Manager Key Vault support' was only about ARM template Key Vault support.
    17973586 - 'Integrate Octopus deploy with secrets managment system Vault' is similar to this issue only for https://www.vaultproject.io

    This idea is similar to
    https://docs.microsoft.com/en-us/vsts/build-release/concepts/library/variable-groups?view=vsts#link-secrets-from-an-azure-key-vault-as-variables

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

    86 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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…

    50 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 →
  15. 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.

    48 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 →
  16. 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/

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

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

    33 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. Create an Azure Web Sites extension that acts as a tentacle to allow tentacle-like deployments OOTB

    Azure Web Sites extensions: http://azure.microsoft.com/blog/2014/06/20/azure-web-sites-extensions/

    How amazing would it be if you could add in an extension to your Azure Web Site that can connect to a OctopusDeploy server and register that website in a particular envionment with a particular role and have NuGet packages deployed to it?

    It would be a much nicer ootb experience then the current Azure Web Sites Web Deploy library item (which is definitely awesome, but it's not very seamless).

    31 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 →
  20. 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"

    30 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 →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base