Product Feedback

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Composite Step Templates

    There are sets of common steps that we very often want to "bookend" all of our deployments with. One concrete example would be: sending out a Manual Intervention to confirm when all servers are confirmed live before stamping a new deployment in NewRelic.

    Right now, everyone has to bake these steps into their own projects by adding the Manual Intervention step followed by the NewRelic Deployment Stamp step. If it were possible to create what I would call "Composite Step Templates" then I could define a reusable step template that was made up of other step templates. That way, instead…

    358 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

    Under Consideration  ·  39 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Automatically retry steps if they are failed

    Now when a step failed you have to set guided failure on in order to retry the step, it would be handy to have a setting where you say always retry failed steps.

    For example if you are doing continues deployment where a build server triggers a deployment from a build, you have to:
    - login into octopus
    - select the correct project
    - manually intervene and assign it to you
    - retry it

    It would be much better if the retry can be done automatically

    197 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

    21 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Permission attributes for variable sets, library variable sets, or even variable

    Add RO attribute/flag to variable set to prevent accidentally changes of it. Or even develop extended permissions linked to username, groups etc. For example in our Octopus environment we have default variable set in library for special package and I'm afraid if somebody will change it accidentally and it will affect to whole related projects where it will be used

    187 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

    21 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  4. Environment groups

    Make it possible to put environments into groups (or rather, to put Tentacles within an environment into groups)

    https://github.com/OctopusDeploy/Issues/issues/497

    178 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

    21 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Renaming roles

    I think it would be a nice feature to be able to rename roles, there are situation where you might choose the wrong name and at that point if you have many project connected to it it will be annoying to have to update all the projects.

    177 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

    28 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow approval step for scheduled deployment happen before actual deployment

    It would be great to have the ability to be able to add an approval step for a scheduled deployment, but be able to approve it before the deployment starts.

    So for example, if I wanted to schedule a deployment to run at 2am, I have the ability to schedule the deployment, but the approval can happen between now and then, but the rest of the steps only run at 2am.

    Source: http://help.octopusdeploy.com/discussions/questions/3081

    165 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

    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Upgrade of OctopusServer through Octopus

    It would be really nice if Octopus Server (and portal) had the ability to be updated the same way as a release can be pushed meaning through and Octopus nuget package. this would make the maintenance easy instead of having to download and rerun installer each time a new Octopus release is created

    150 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

    12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Run steps as a different user

    Some of our projects live on shared servers, and run under different users for isolation. It would be good to be able to choose which user a nuget deployment/powershell script runs under so we can protect against mistakes/malicious code in our powershell deployment scripts.

    118 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

    11 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Integrate smoke tests for post deployment

    While we can run smoke tests by using the PostDeploy.ps1, such as running nunit.exe or something similar (frisby.js, etc), it would be great to have a way to integrate back into the dashboard (through the rest api?).

    Related links:
    http://help.octopusdeploy.com/discussions/questions/214-running-smoke-tests-after-deploy
    http://help.octopusdeploy.com/discussions/problems/53646

    http://jimblogdog.blogspot.co.uk/2012/08/walk-thru-using-wolfpack-to.html

    117 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

    18 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the suggestion and for voting everyone. I’d like to get feedback on where we should go with this.

    There are a few things in Octopus that already help with this – first, it’s possible to package your NUnit tests and run them as part of a package test (we do this ourselves), or to write a PowerShell step that pings your website to see if it is online. So the actual process of performing the tests is pretty easy. Do we need to write more blog posts/documentation to show how it can be done?

    The next part is viewing the test results – in Octopus 2.0 you can “attach” files to a deployment via PowerShell which are then uploaded and available on the deployment page.

    Viewing NUnit results XML isn’t that nice though, so I guess it would be nice to be able to render those NUnit test…

  10. Allow new IIS step to just create IIS resources without necessarily deploying a package

    Currently the new IIS step (introduced in 3.4.7) allows you to create Sites, Apps and Virtual directories, but you always have to deploy a package.

    It might be useful for some users to be able to take advantage of the IIS functionalities, without having a deploy a package.

    Source: http://help.octopusdeploy.com/discussions/questions/9702

    115 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

    11 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Automatic release creation to multiple channels

    It would be helpful to be able to specify multiple channels for automatic release creation. The way we are using channels, no package is eligible for more than 1 channel. Without this, the development team now needs to remember that for some channels they don't need to go to octopus to create the release and for others they do.

    109 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

    13 comments  ·  Releases  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add email attachment support

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

    105 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 →
  13. Add support for setting Windows Service Recovery options

    Add the ability to set the actions to be taken on service failure. This is accomplished via sc as follows:
    http://technet.microsoft.com/en-us/library/cc742019.aspx or using Powershell set-service.

    At present, we are managing with a custom PowerShell script.

    98 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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Inheritable Templates

    There should be the possibility to create project templates which can be chossen when creating a new project. This should then not only copy everything, but keep the reference to the template. So when something is changed in the template, all projects based on this template should be updated as well.

    Steps coming from a template should not be editable in a subproject, but there should be the possibility to disable a specific step in a specific project.
    Also there should be the possibility to add other steps between "template steps" to customize the process.

    Teamcity has a simillar model.

    97 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

    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    96 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

    10 comments  ·  Releases  ·  Flag idea as inappropriate…  ·  Admin →
  16. Make the Blue/Green Model the Gold Standard of Deployment with Zero Downtime

    In my mind zero-downtime deployment is the gold standard of deployment. Octopus should support this model to the fullest. Given proper tooling (in Octopus) this is very easy to accomplish for customers.

    I think most ASP.NET apps should be deployed in the following way:

    1. Put the app behind a load balancer such as ARR (built-in and free)
    2. For each new deployment create a fresh IIS site
    3. Configure the site
    4. Request a configurable set of important URLs to start the site and warmup caches
    5. Validate, that those URLs return 200 and contain a given check string (a smoke test)
    6. If all…
    81 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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Use 24 hours format in UI instead of AM/PM (Option in user or site settings)

    We are more familiar with 24HH format. Thit feature would help europe customers.

    Also it would be great to have ability to select timezone in UI.

    81 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

    16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Two Factor Authentication

    I need to implement some form of two factor authentication for Octopus due to regulatory requirements.

    A very simple approach might be this: http://www.codeproject.com/Articles/403355/Implementing-Two-Factor-...

    Used by Google, Twitter, GitHub etc.

    Source: http://help.octopusdeploy.com/discussions/questions/1605

    81 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

    16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support deployment of Azure Function projects

    Support deployment of Azure Function projects

    79 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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Associate variables with a Release when creating one

    When creating a release, allow variable values to be set that will then flow through to all deployments of the release. See: https://github.com/OctopusDeploy/Issues/issues/1149#issuecomment-52598811

    79 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

    9 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 70 71
  • Don't see your idea?

Feedback and Knowledge Base