General

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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. 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 →
  7. 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 →
  8. 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 →
  9. Deployment Trigger Support Multi-Tenant

    The Deployment Trigger should support multi-tenant logic. I am sure I do not have a unique environment that a test/staging environment is in a single tenant and production can span multiple tenants.

    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 →
  10. Show worker name in Task Log

    Please add the name of the worker machine to the task log when a deployment is made. It is a small change which I think will be easy to add.

    Reason/Rationale/Context: We were working without workers/worker pool and we just had a few deployments that we were setting up to run on our Octopus server. My colleague added a worker and without me noticing what I thought was running on the Octopus server was moved to the worker. I knew I had the dependencies my script needed installed via Octopus on the Octopus Server (like a trusted root certificate 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 →
  11. Execute adhoc data updates with sql on Jira

    Hi it would be useful to have execute scripts feature on Octopus for data config changes to be picked from jira.
    This will help to select dev env and validate SQL and use as test evidence to run on prod env.
    Auditing abilities on octopus can be further enhanced by attaching script execution to Jira also. All major releases have database changes along with binary deployments, it is imperative we keep audit history for data changes also.

    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. Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

    Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

    17 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 →
  13. Allow worker pools to be compatible with ALL process steps

    Worker pools only are compatible with two OOTB Octopus process steps (deploy a script, deploy to cloud). My team heavily uses the 'Deploy a Package' step, but this step is not allowed to use worker pools. This is quite an oversight and should be a prioritized feature in the next sprint.

    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 →
  14. Add date, time and date/time variable types

    Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.

    Optionally provide a friendly interface (date picker control) for the respective values.

    8 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 variable in variable set to have a Project Group scope

    It would be useful if we could set variables in a variable set to a Project Group scope.

    The use case for this is that we have a shared variable set that sets a product ID.

    We could then scope this by product group.

    eg

    Variable Set Products
    Product Id - ATeam Scoped to Project Group A
    Product Id - BTeam Scoped to Project Group B

    Project Group A
    - Proj A1
    - Proj A2

    Project Group B
    - Proj B1
    - Proj B2

    Currently we have to override the ProductID in every project in Project Group B which sometimes…

    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 →
  16. Deploy a Release Step - Task Summary View

    We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.

    When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.

    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 inserting into an array in JSON Configuration

    Given an JSON settings file which has an array element

    e.g. { "Users": [] }

    Use Octopus variables to insert into the array rather than just replace values.

    e.g.
    define Users:0:Username = user
    define Users:0:Password = password

    Would result in the object getting inserted

    { "Users": [ { "Username: "user", "Password": "password" } ] }

    https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7

    29 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 →
  18. Support for High Priority Deployments/Tasks

    Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
    In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
    This is not possible now, the only solution now is to cancel all the existing tasks.

    116 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Better integration between runbooks and deployments

    When deploying to c:\mydirectory#{Octopus.Release.Number} Runbooks are unable to obtain the #{Octopus.Release.Number} information from the deployment. Which makes a lot of actions rather difficult.
    If it was possible for a deployment to set a variable available to Runbooks or for Runbooks to query information in releases per environment that would really be great.

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

Feedback and Knowledge Base