General

  1. Remove the need for a server level LOGIN in the SQL Server database

    To manage LOGIN objects you need administrator access on the server level, database USER objects only needs access to the database level.

    The setup wizard fails when started with an existing database if the provided credentials are not for a LOGIN object, after some initial cleanup tasks have succeeded.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  2. Fuzzy Variable Matching

    Allow replacements to be made over different files which share the same structure, but at a higher level requires a fuzzy match.

    This would allow us to have a singular variable for repeated applications and the change would be applied to all json files that share the same structure.

    Please see the support question below for more specific details.

    https://help.octopus.com/t/fuzzy-variable-matching/26563

    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 →
  3. 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.

    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 →
  4. Bindable variables for certificates in the kubernetes deploy container step

    https://help.octopus.com/t/kubernetes-certificate-variable-binding/26581

    In the kubernetes deploy step for the certificate field I have a need to use my own single text box bindable template variable rather than the current selection of certificate type only variables. The reason being that this cannot be scoped across both tenants and environments.

    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. Include an environment variable or another method to set the server url for the docker images

    At the moment there is no way to set the server url without going into configuration -> nodes in the GUI. For Ingress this is required to be first set up before requests are directed to the URL. It would be good to have the variable or some way to do this before container start without accessing the GUI. See: https://help.octopus.com/t/server-url-env-variable-for-docker/26543/2

    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  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

    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. Add link/URI within the Octopus, deployment output to support one-click access from CI/CD tools

    If you use an Octopus, build/pipeline task within Azure DevOps Server/Services (or another CI/CD tool) to trigger a deployment, it would be useful to have a URI within the feedback output by the deployment within the Azure DevOps (or other CI/CD tool) build/pipeline.

    This would allow the Octopus deployment to be accessed via a single click of that URI (as opposed to having to navigate back into Octopus and find the project, the release and then the deployment).

    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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Deployment Time Option

    If you redeploy to Tenant and that tenant is deemed to have the latest version, then the tenant is skipped.

    Though the main reason (well for us and many other companies I've worked at using Octopus) is that we simply want to re-apply an updated variable set.

    In this scenario:
    * I don't want to redeploy the package.
    * I only want to re-run the web.config/appsetting.json transforms.

    Install of just the skip option
    (x) Skip deploy...
    ( ) Apply configuration changes only

    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. Apply the retention policy out of hours (or on a schedule)

    Applying the retention policy at the end of a deployment isn’t the best use of deployment time especially in a tenanted environment with many packages to deploy for many tenants on a single vm.

    I would love to see an option to apply the retention policy out of hours, when the environment is at a low usage.

    It would certainly speed up our deployments.

    Similar to, but using a schdule.
    https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/42726191-control-when-tentacle-retention-policy-step-will-b

    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 →
  10. Add filter for the dashboard for failed deployments

    We have a continually growing set of projects and some times I want to look through to see if any have failed so I can head off any issues before they become blocking for a team
    I would loke to be able to set a quick filter on that dashboard to only see projects with a failed deployment. It could be a simple as a checkbox or toggle button

    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  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow runbooks to be configured not to run immediately after a missed scheduled trigger

    Runbooks can use triggers to start on schedule. If the OctopusDeploy service stops for any reason, a runbook that has missed its schedule will run as soon as OctopusDeploy become available. This is suboptimal where the missed trigger was powering off some VMs overnight and runs during your core hours, for example. This behavior should be configurable, much like the "Run task as soon as possible after a scheduled start is missed" setting in Windows scheduled tasks.

    0 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  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 →
  13. Recognise when a variable is used for a feed ID or package version.

    When using a variable to specify a package feed, or selecting package versions for a release, after creating a release Octopus displays an error on the release page.

    With regard to the feed ID, it is possible to set a feed ID from variables as discussed here - https://octopus.com/docs/deployments/packages/dynamically-selecting-packages

    With regard to versions, it is possible to set a version from variables, allowing the version of a package to by dynamically updated. This is most useful on occasions where another Octopus deployment is triggered as part of the process.

    However, even though both scenarios works, after a release is created…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow variables to be set as Environment Variables

    It would be extremely useful to allow variables to be set as an environment variable before the process starts (and even allow outputs to be made environment variables). At the moment it is extremely hard to write generic scripts for both development and for use in octopus.

    Allowing variables to be set as environment variables eliminates this issue as well as allows more providers etc.

    If I take a terraform run where the provider (say digital ocean and terraform cloud) can be initialized via environment variables I do not need to litter my scripts with octopus only if conditionals. They…

    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 →
  15. Allow Users to Define Their Own Default Task Log View Settings

    When viewing a task log you offer 3 settings:
    1. Expand
    2. Log Level
    3. Log tail

    They default to Interesting, Info, Last 20

    In my position, those settings are almost always unhelpful - I have to change the selections with every task log I view, and in my position I view a ton of them a day.

    I'd like the option to set my own personal Task Log View default values so that when I click on a task log my preset selections are automatically loaded and the task log is in my preferred state on page load.

    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  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  16. visualization of build stability in octopus

    It would be great if octopus has a project wise dashboard option where we can create visualization of project build stability like status of last 100 deployments , how many passed , how many failed etc

    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 →
  17. Variable value scoped to release version

    Often times I need to update a configuration variable but, only once we are about to release a particular release.

    For example, if I'm upgrading my SQL server and moving to a new machine. I've got a release for the new SQL server version let's call it 2.0.0.0, however, I can't put my new connection string variable into Octopus configuration because I'm still deploying version 1 releases until it's time to migrate.

    What I would like to be able to do is specify that the variable for the connection string is X for all releases prior to v 2.0.0.0 and…

    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 →
  18. Immutable Step ID

    Similar to most other entities in Octopus (e.g. Projects, Machines, Feeds, etc), it would be very helpful if the steps of a deployment process or runbook had an immutable and unique ID in addition to their display name. This would make referencing a step from elsewhere (e.g. reading output variables) a lot more resilient to change over time.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  19. Depreciate Variable Sets

    Variable sets cannot be deleted until all project, release, and I assume runbook references are removed. Since it can take a long time for releases to age out, a Depreciate flag that can be set once all Project references are removed would be great. This flag would prevent adding the Variable Set to projects (and hidden from the selector).

    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  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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/

    6 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 →
  • Don't see your idea?

Feedback and Knowledge Base