General

  1. Add email attachment support

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

    192 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. Allow multiple and/or wildcard domains for Google OIDC authentication

    The GoogleApps authenticator in Octopus is excellent. However it limits you to specifying a single 'Hosted Domain' and rejects otherwise successful authentication if the user's email address domain does not match that one domain.

    We have a couple of use cases where we would like to allow multiple domains (with just one instance of the the GoogleApps auth):

    1) We operate two brands and so have Google Apps addresses for two domains. We can only enable one on of them for Octopus.

    2) We would like tenant users to be able to have limited access. It would be ideal if…

    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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. Make it possible to append a build number when using OctoPack

    Octopack can parse AssemblyVesion attributes to extract version information, which is great. This enabled me to control the version of the generated NuGetPackage at the time when I check in my project. I like that. My build server generates new packages for every commit to out repository (even though the version might now have changed). Therefore I would like to be able to append the build number to the package Id. This could be done using an OctoPack parameter "OctoPackBuildNumber"

    Example: AssemblyInfo.cs: [assembly: AssemblyVersion("3.5.0.1")]
    then the buildserver passes in: /OctoPackBuildNumber -build%build.number%

    Result:

    MyProject.3.5.0-build5551.nupkg

    7 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