Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. An easy way to attach deployment artifacts would complement this feature very well.

    106 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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.

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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…

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Support for Azure Government account or environment selector.
    Also support for MFA.

    Thanks.

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Support Windows Server 2016 Nano.

    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

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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.

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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.

    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

    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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).

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    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

    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Octopus was born out of a desire to help .NET developers, why not have someone try this...

    Create a custom project type for Visual Studio for Octopus Projects that incorporate these json files.

    That would allow a GUI that can easily and ready be documented, it would allow us to integrate them with our source control tools, and more closely align our Octopus projects with our work.

    I wish I had those skills, I'm more of a DBA/BI Developer, but I think this idea could work, thoughts?

    Keith

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. There does not seem to be a direct way of requesting more than one DeploymentProcess from the API. I am working on a tool that needs to determine all projects that have deployment processes that have steps with a specific TargetRole. As it is, I have to iterate over every project (hundreds of them in our case) and request each process individually to interrogate the step information. I would be better if I could paginate over the processes directly and only request the projects I care about.

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. It would be useful to be able to set up notifications after each step. In our case, specifically, we would like to notify Slack after each completed step.
    I've seen the library script that you can use to add a step to a deployment process to notify Slack, but that would mean notifying Slack only after a deployment is complete. Some of our deployments take a long time and we would like to be able to follow their progress in Slack, i.e. get OctopusDeploy to notify Slack after each individual step.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 4 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. I'd like to see a plugin for Octopus deployments to integrate into the continuous delivery process displayed in Hygieia. This would make octopus deploy part of a comprehensive view of work. Hygieia is a DevOps Dashboard to track development. More info and a link to a video explaining the benefits are here: https://github.com/capitalone/Hygieia

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?