General

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

    156 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 →
  2. 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 →
  3. 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

    28 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 →
  4. 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 →
  5. 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 →
  6. 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.

    87 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. 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.

    11 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 →
  8. Add email attachment support

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

    218 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 →
  9. 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.

    240 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 →
  10. 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…
    53 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 →
  11. 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.

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

    4 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. Add the Octopus CLI to HomeBrew

    We're working on a few Mac minis to be our iOS build servers. We use (among other things) Homebrew as our package manager. For a variety of reasons, we need the Octopus CLI tool installed on these Mac Minis. You guys support MacOs, but it doesn't look like you've added the CLI to Homebrew.

    While I was tempted to add it myself, I figured I'd start with suggesting it here.

    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 →
  14. Add an octopack option for dynamically creating dockerfiles

    It would be super helpful if I could add a dockerfile to my project and place a #ADDFILES variable in and have octopack dynamically regenerate the dockerfile for me as part of the build step so my output could be a zip file that was 'docker build' ready.

    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 →
  15. Add option to collect artifacts in TFS/VSTS extension deployment task

    When triggering a deployment from a build system (TFS, VSTS, or other), it may desirable to collect artifacts produced by the deployment (via New-OctopusArtifact) back to the triggering build. For example, when executing integration tests during a deployment triggered from a TFS build, I would like to copy the test results back to the triggering build for publishing within TFS.

    The above can currently be done after the deployment has completed. However, it is challenging to ensure that the correct artifacts are collected since the deployment ID needs to be inferred rather than being well-known as it is within the…

    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 →
  16. stop embedding html in the api

    We want to scrape and store events from the API so that we can aggregate events to help us understand our usage.

    Unfortunately this is made difficult by the embedding of HTML in fields that are inside the json that is returned by the octopus api.

    It is rather frustrating because there is a lot of useful information in the details field of an event but they are formatted with html.

    see https://github.com/OctopusDeploy/OctopusDeploy-Api/wiki/Events

    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 →
  17. Azure Government with MFA

    Support for Azure Government account or environment selector.
    Also support for MFA.

    Thanks.

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

Feedback and Knowledge Base