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.

    28 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. 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.

    6 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. EDB to PST Converter Software

    Try magical InQuit EDB to PST Converter utility which is very effective to transform EDB records into PST information record. It does now not purpose any alteration or changes inside the original statistics while you doing the conversion. Via this software the user can export the all-over records inclusive of emails, inbox, despatched the item, draft, delete-objects, attachment, calendar, notes, undertaking (To, Cc, Bcc, Date, From, Object and Time).
    Using this utility you can access your statistics into numerous document formats consisting of PST, EML, EMLX, vCard, vCal, MSG, and MBOX after the conversion process. It is like minded emigrate…

    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 →
  4. 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…

    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 →
  5. 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 →
  6. Support loading CloudFormation templates from an S3 Bucket

    Due to the API limits limiting in-call CloudFormation template length to 51200 bytes, consider enabling the option to load a CF template from an S3 bucket. This functionality already exists in the CLI, and can be done via a script step, but having it be baked in would be an enhancement.

    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.

    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. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. Kubernetes Cluster Worker Pools

    I am on a cloud account using shared worker pools. This is great, but using shared pools means Octopus Infrastructure is running my deployments and I need to wait for a worker to free up.
    Also shared workers do not have a fixed IP so I cannot limit the IP addresses that can communicate with my Kubernetes Master, an attack vector I would like to close.

    It would be great if when setting up a Kubernetes cluster, my Octopus cloud account asks if it can run workers inside my cluster.

    An issue with this is that the worker will run…

    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. 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/

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

    9 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 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.

    104 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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

    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 →
  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 →
← Previous 1 3 4 5 24 25
  • Don't see your idea?

Feedback and Knowledge Base