General

  1. Allow the Apply Retention Policy step to timeout gracefully on a locally locked file condition. Exit timeout with Warn or Error.

    We have hit the condition where the oldest package that is being deleted by the Tentacle cannot be deleted due to a locked file.

    This locks the progress of the overall deployment.

    This proposal will time-bound the Apply Retention Policy step to a configurable timeout value.

    After the timeout is reached and there should also be the option to either fail the overall deployment with an Error exit condition -or- pass the overall deployment with a Warning

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Integration with Microsoft Teams

    Microsoft Teams already has a pretty great list of connectors, but one big one is missing... Octopus Deploy!

    I would like to be able to receive messages in a channel when a deployment is complete, or certain events happen.

    208 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Project Variable Filter for Tenants

    I was wondering if there has been any thought into making a project variable filter/tag system by tenant. It seems like over time the project variable list could get quite long for large implementations. It would be nice if when setting up a project variable you could tag a tenant or tenants that it applies to. That way it would only show for those tenants. Otherwise it would take the default value for the other tenants. Or something to that effect.

    15 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 →
  4. Add pattern matching to JSON transforms for arrays

    This matched:
    Currently JSON transforms support arrays by providing the index
    Serilog:WriteTo:2:Args:serverUrl

    This is fragile, if an item is added then it will attempt to add the value to the incorrect item.

    But maybe something like
    Serilog:WriteTo:[Name="Seq"]:Args:serverUrl

    This means the Args value will be set on any WriteTo child item that also has a field matching the supplied pattern.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Selective health checks and tentacle upgrades targeted via filter

    See https://help.octopusdeploy.com/discussions/problems/65644-selective-tentacle-upgrades-and-health-checks

    In v4 it should be possible to select the targets to health check or upgrade via the filters. For example, I may only want to run it against a certain environment or tenant or against a certain role.

    I feel there has been some regression from v4 here because you used to be able to control this by environment. Now it's all or a single machine and for large environments makes staged roll-outs of upgrades and updates extremely time consuming.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Apply rention policy to custom install directories

    When deleting a release from a target machine according to retention policy, option to also delete the custom directory (and its contents) that release was installed to. This is for custom install directories that are named with {Octopus.Release.Number} as part of the name.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Dashboard filter to show specific tenant

    Be able to display tenant specific release/project information on Dashboard

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow the use of C# script (.csx) using .NET Core

    ScriptCS will no longer be supported under .NET Core.

    Please enable support for dotnet-script (https://github.com/filipw/dotnet-script) so that C# scripts can be executed under .NET Core

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Step for creating or updating a service in a Docker Swarm

    As a DevOps Engineer, I would like to be able to create a new service, or update an existing service in a Docker Swarm using an Octopus Step.
    For this to work for us, we would need to assign or alter Networks, Secrets, Environment Variables, and HRM Labels.
    The commands involved would be "docker service create" and "docker service update"

    30 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. Allow named variable sets to be defined at the Project Group level and optionally shared between all projects in that group

    Within a project group it would be good to be able to define sets of variables (like in the library) which can be optionally shared between any project in the same project group. This will allow variables to be shared between similar projects and will allow easy grouping of related variables.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add "QueuedBy" system variable for obtaining user who has actually queued deployments

    I'm getting persons username when receiving deployment status email from automatically triggered deployment (by Project trigger on machine becomes available event). In the email template i'm using Octopus.Deployment.CreatedBy.Username system variable to display user who has run deployment.
    So in case of auto-triggered deployments I would like to get value "System" instead of some person's username (apparently one's who first has run the deployment manually).

    Ref: http://help.octopusdeploy.com/discussions/problems/52736-octopusdeploymentcreatedbyusername-value-is-not-system-when-deployment-fired-by-project-trigger

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. channel level permissions

    We would like the option to manage permissions for which channels can be used by certain team members within a project. We have DB deployment specific channels stored within the same project as our app deploy, but do not want devs to be able to release on the DB deploy channel. Only DBA's should be able to.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  13. Octopus Deploy Status Icon/Widget

    The ability to hot-link to publicly accessible widgets/icons that show the last Octopus deploy status for a particular project and it's environment. Very similar to how build tools do it (like TC Server, Jenkins, VSTS and Travis CI). See an example here: https://docs.travis-ci.com/user/status-images/

    40 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 →
  14. Show stats on how long a step script takes to run

    Currently the "ran for x" is accumulative.
    Whilst I agree that the UI is correct in terms of how long that block was running for it doesn't show exactly how long each deployment step is taking (essentially how long it takes to run the deploy.ps1 or some other script)

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Visualize use of Write-Progress cmdlet in task log

    PowerShell hosts such as the PS command line and ISE visualize percent complete (as a progress bar), action text, and status text if Write-Progress is used within a script. It would be nice if the Octopus task log web UI showed that as well. Just as with other PowerShell hosts, it's not something that would be part of the permanent task log so maybe it would show up as part of the header for a task running on a particular server.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Show step progression on dashboard

    It would be nice to be able to see step progression on the dashboard, not just the ajax spinner.

    Something like http://i.imgur.com/DG3QYYv.png

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow wildcards in subscription fields

    For installations with lots of things it would be helpful to filter subscription events by wildcards. For example, "Prod*" environments to include all production environments.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Improve Variable Substitution Feedback/Logging

    Currently the information included in the logs, regarding variable substation is very limited:

    Performing variable substitution on <filename>

    This could be improved in a few ways:
    - Add the number of variables substituted to the logs
    - Include the variable, and value substituted as Verbose (Sensitive values replaced with stars)
    - Add the variable names substituted to an Output variable; I could do my own lookup of the value, and email a report in a follow up script step

    In the end, I'm just looking for some way to verify an integral part of deployments.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Enhanced variable substitution in ARM template deployment

    When using an ARM resource group deployment, Octopus asks for parameters file, which is JSON, and replaces parameter values with matching variables.

    We would like to use the JSON variable substitution syntax mentioned here: https://octopus.com/docs/guides/deploying-asp.net-core-web-applications/json-configuration-variables-feature

    this would help us maintain a working parameters file that can be used outside of Octopus.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support ZIP file for external feeds

    External feeds currently only support NuGet package feeds. It would be good to support ZIP feeds, to support integration with products like Artifactory.

    153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
1 2 9 11 13 64 65
  • Don't see your idea?

Feedback and Knowledge Base