General

  1. 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
    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 →
  2. ATS OST to PST Converter

    The most prominent way to convert corrupt OST file into PST format is ATS OST to PST converter software. It is very trustworthy so you can trust on this for converting the data of OST mailbox along with all properties mailbox, inbox, journals, task, calendar, contact, sent items, junk mail, attachments, and etc. this software supports all version of windows up to latest Win8.1(32 and 64 bit). And MS Outlook version (97, 2000, 2002, (XP), 2003, 2007, 2010, and 2013 (32 and 64 bit).

    2 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 →
  3. 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
    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 →
  4. 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
    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 →
  5. 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
    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 →
  6. 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
    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. Runbook specific variables

    Add variables to Runbooks, so that adding new variables to the project for a specific Runbook don't cause the snapshots of other Runbooks to be old.

    For example, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email addresses to send to. The from/to dates are prompted variables, so you can do an adhoc run. If no dates are provided, it will default to the last week of data.

    These variables only have meaning for this Runbook, so it would be nice…

    1 vote
    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 →
  8. 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.

    1 vote
    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. 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.

    101 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    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. 1 vote
    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 →
  12. 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

    14 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 →
  13. Tenant variables side by side

    The idea is to have the tenant variables displayed vertically, with one column for each environment.
    Currently, it is quite tedious to compare or copy variable values from an environment to another.

    13 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 →
  14. See references to projects used in 'Deploy a Release' steps

    In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.

    Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.

    9 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 →
  15. Deployment promotion with excluded steps is not persisting chosen steps

    Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.

    We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.

    It would be great if you can persist the state of excluded steps to the next environments as part of same release?

    15 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 →
  16. Deploy a release - accessing variables from last release

    As per - https://help.octopus.com/t/deploy-a-release-accessing-variables-from-last-release/22788

    You should be able to access a previous releases Step output variables, for when a release has already been deployed.

    Either via the Deploy a release step.
    Or more generally to retrieve these values for a given release.
    E.g. an obtain Release information step

    3 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 →
  17. "Deploy a release step" allow choosing target environment

    The deploy release step assumes want to deploy to the same environment as the parent deployment.

    Add facility to pass a parameter to chose which environment to deploy the release too.
    E.g. so can deploy a single master release, which kicks off multiple deployments of other release to the defined environments specified by the parameters.

    Similar to how the community Chain step template allows for.

    3 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 →
  18. Pre-caching / Pre-acquiring of packages for scheduled deployments

    We deploy our packages to our customer environments.
    For example 1.5GB of packages to 500 targets over the internet. As the internet connections can be slow and to make sure that the deployments all take place at the same (scheduled) time I suggest that the "acquiring packages" step optionally starts as soon as a deployment is scheduled and verified again at the scheduled execution time. Should the deployment package(s) be missing or corrupt at the scheduled execution time there could also be an option "re-aquire at execution"/"fail if missing".

    3 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 →
  19. "Acquire Packages" should be first step

    Give an option (or make it default) to have the "Acquire Packages" step to always happen at the very beginning.

    Our use case:
    We uninstall a program, then extract the package and install it. If it fails on the package download (which happens automatically right before the extraction), then our deployment target had all of its files deleted, but failed the deployment.

    Our current fix:
    Make sure the "Extract Packages" step is the first thing in every project, to force "Acquire Packages" to be at the very beginning

    3 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 →
  20. Use IAM roles instead of AWS access secrets for all external resources, e.g. feeds, targets, community library tasks

    Currently, the only way to set up AWS authentication for an ECR external feed, AWS deployment target, community library task, etc, is with an IAM user secret such as API access keypair. Our product secrutiy team has exlicitly forbidden use of secrets such as keypairs like this and requires everything to use IAM role authentication via role assumption.

    It would be lovely to replace the access key and secret key inputs with a single input for an IAM role name to assume into in order to get the needed credentials. The authentication and login could then execute on workers with…

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

Feedback and Knowledge Base