General

  1. Deployment Email Preferences by User

    Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Built-in Azure App Service/Function Restart

    I find that deployments to Azure Functions and standard app services will occasionally fail due to files being locked. This usually requires stopping the app service, re-running the deployment, and then restarting the function or app.

    This can be scripted with Powershell, but since this is such a common scenario, I’d love a checkbox built into the Azure App Service step that provides this ability. Something like “Stop App Service prior to deployment and restart after deployment”.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add Migrate options to API Import

    First I want to say that the new API functionality added in latest versions is very appreciated especially the possibility to export/import project out of spaces. However we really miss the merge functionality when importing project from Non-prod octopus to Prod Octopus

    Our current automated procedure includes : Delete project-> Re-import Project-> Update prod variables

    Problems: It removes history and require a new release number in prod due to updated of variables.

    Addition to this feature requests includes: Exclusion of environment variables in export

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Grouping variables in Octopus UI

    As a project leader I should be able to group variables on Octopus UI. This can be just logical separation.

    This solve the problem with linked variables and help mange them.

    For example It could collapse elements that are in structure - for example: db.username and db.password can be collapse as elements of root db or by labeling variables and then can be filtered by using specific label, for example - db.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Custom advanced variable substitution filters

    Add ability to define custom substitution filters that can run scripts defined by the end user.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support sharing of variable sets and script modules across spaces

    https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4

    We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.

    We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Please support deployment to Azure Cloud Sevice (Extended Support) targets

    Microsoft opened up a preview for ARM base Azure Cloud Service, which is probably hinting on them moving away from a Classic cloud service deployment model:
    https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/overview
    Please add support for this type of targets.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Dashboard should be better at visualizing multiple tenants

    Currently the home dashboard displays tenants as a small grey-on-grey count of up-to-date tenants vs total tenants. It would be nice to see a coloured pie chart or similar visualization instead, to make it more obvious when one tenant in an environment is still running an old version or has had a failed deployment.
    It can be easy to miss failed deployments from the dashboard screen.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add tenant tag support to runbook scheduling

    Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Control when Tentacle retention policy step will be executed during deployment

    Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
    This behavior is by design and can't be configured.

    This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.

    As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.

    I would like to have an option to control when the retention…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Dashboard icon page target

    I manage a multi tenant system and the dashboard is always a pain to use.

    First the icon cant be trusted as it dose not accurately show things like a single tenant deploying (The animated icon).

    But the real pain is that if I click that icon it takes me to the deployment page of one of the tenants. What I want it to do is take me to a screen for all of the tenants. Something like the tasks screen filtered by environment would be very nice.

    Then I would be able to see the true state of all…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add timeout to guided failures

    Add an option to have guided failures timeout out and fail after a specified period of time. I.E it no manual intervention is taking in 1 hour have the deploy fail completely.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Marking a process step as non critical

    Some steps in the deployment process could merely be just to trigger some notifications or sending metrics to other products. These steps are not critical to the deployments.
    A flag in the step could be helpful which can mark it as a critical/non-critical step

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add Support for More Runbook Triggers

    The only Runbook trigger right now is a scheduled trigger.

    I would like to suggest two more trigger types:


    Helm Chart Package Trigger:

    When a new Helm Chart version of a package is published, then the trigger would fire. (Allowing the calling of a Runbook.)


    Version Control Trigger:

    If Octopus Deploy added a VCS trigger, then it would allow us to use GitOps.

    Both of these allow Operations to enable control from check in / merge point in source control.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. OctopusBypassDeploymentMutex for Script console

    Parallel execution should be enabled or can be switch on the fly in script console. Via a variable, similar to OctopusBypassDeploymentMutex

    With the scenario that there is a process running (read: stuck/looping) in the target and executing a kill command via the script console will get you “waiting for script to finish in task…” so it is currently not the workaround.

    Ref case:
    https://help.octopus.com/t/force-stop-a-step-execution/26682/3

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support for .env files with Structured Variables

    We are currently using React, Gatsby and Parcel which all use .env files for their environment variables

    https://www.npmjs.com/package/dotenv

    Currently .env files are not being recognized, they are assuming they are yaml files, which they are not, they are read similar to java properties as key values

    Right now we have to use variable substitution, but would like to use structured so we don't need to add #{} tags in our code

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Download package option to only keep latest in cache

    There are currently 2 package download options when deploying a release: using the package from the cache and always re-downloading. Both of these are useful, but each has one big downside that I think this feature would correct.

    When using the package cache, Octopus will never pick up changes that were made to the same version of the package. If forcing a re-download, the package cache can quickly fill up, especially with multiple development teams (and yes, we have retention policies configured -- our packages are unfortunately quite large).

    A new option that will just always re-download and keep a…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Execute F# script steps using dotnet fsi

    Several packages are now incompatible with FSI as it uses the old execution engine, one example is FSharp.Data and latest Newtonsoft.Json. System.Text.Json is also out of the question, basically anything targeting Netstandard 2.0.

    Switching to dotnet fsi will allow usage of said packages. It will also ensure cross platform compatibility for scripts and allows referencing packages in the script. https://devblogs.microsoft.com/dotnet/f-5-and-f-tools-update-for-june/

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add First Class Support for Blue Green Deployments

    For a product that is all about deployments, not having first class support for Blue Green deployments is.... odd.

    Not a lot is needed. In fact you can't put in too much or it will be too opinionated.

    Basically, all that is needed is something similar to your "tenant" system with a blue and a green line. But also show on the line which one is currently in use.

    The "in use" flag will need a bit of effort as it can be a percentage or a list of users or both. But that is not too difficult to show.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 25 26
  • Don't see your idea?

Feedback and Knowledge Base