Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    17 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

    4 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. 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)
  3. 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…

    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

    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)
  4. 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
    11 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)
  5. 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…

    33 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)
  6. 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.

    65 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

    4 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'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)
  8. 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)
  9. 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.

    76 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)
  10. 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)
  11. 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)
  12. 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)
    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.
    34 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)
  13. 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.

    5 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)
  14. 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)
  15. Add support for Octopack Nuget so that MonoAndroid and Portable Libraries can be packed with Octopack.

    Currently unable to install Octopack to portable library:
    Could not install package 'OctoPack 3.0.44'. You are trying to install this package into a project that targets 'portable-net45 ....... (and so forth) ..

    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. 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)
  17. 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)
  18. I would like to register a webhook after a new environment is created or when a new release is created. I am currently auto creating environments when a new feature branch is created, but we do not have a great way to auto deploy new releases to the appropriate environment yet. We currently have to poll all the releases and inspect the release notes to determine if we should deploy the release to a specific environment. Having a webhook for a release creation will allow us to support our GitFlow workflow.

    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)
  19. We use Octo.exe in TFS CI Builds that starts the deployment of the project in Octopus Deploy (OD) to our development environment, using a specific OD user (called TFS Service User). This has been working flawlessly, however it restricts the audit history and (email) notifications away from who "really" started the deployment (the user that check-in). As it always ends up saying/using "TFS Service User (tfs@domain.com)".

    It would be nice to be able to create and start the deployment (via Octo.exe) with a provided username to "impersonate".

    8 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?