Skip to content

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

522 results found

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

    55 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Deployments  ·  Admin →
  2. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  3. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  4. 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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Admin →
  5. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  6. 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?

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  7. 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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  8. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  9. 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…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  10. 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".

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  11. 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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Admin →
  12. Some of our deployments have lengthy steps that cannot yet be automated. It would be great if markdown files contained with in a package can be used as manual intervention steps in a deployment.

    I was thinking this could work by simply having an option to choose a file rather than type the instructions on a manual intervention step.

    However it would be really great if some naming standard could be introduced. For example "PreDeploy.md" would appear as a manual intervention at the start of the deployment.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  13. Add the ability to encrypt variable strings using something similar to the variable filters.

    Something like: #{VariableToEncrypt | Encrypt(#{CertificateVariable})}

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Admin →
  14. Currently you can set a condition to a step so that it is only run on tenants with certain tenant tags.

    If I know want to run one step on tenants with a tag but not run a second step with a the same tenant tag (different configuration for these tenants) I have to use conditions field instead. This gives a very unclear overview of the process as it appears to that both step run on tenants with the tag.

    Ideal would be
    * Step A run on tenants with Tag A.
    * Step B run on all tenants except…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Admin →
  15. Please can a view be added that allows a user to see all deployments in a pipeline, spanning all tenants and channels? Having to search for these seperately causes no end of headaches as I often have to line up versions and this is made harder when they have to be searched for. Making it so they are all visible from the main page of a release as an optional view would alleviate this.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  16. Delete previous install files when new install (with an artifact) occurs (offline targets). These deletion should keep in mind the configured retention policy in the corresponding lifecycle

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Admin →
  17. When you configure a "Run a Script" deployment step, you can reference a package, and add the "Substitute Variables in Files" feature. Within the help text it says "A newline-separated list of file names to transform, relative to the package contents." which is inaccurate:

    For me, using a simple, relative path here e.g. "index.html" didn't work. I needed to use the full extracted path of the package e.g:

    {Octopus.Action.Package[EdibleCode.Something].ExtractedPath}\index.html

    Also, you can reference multiple packages for a a run a script template, in which case "relative to the package contents" doesn't make sense and needs clarifying.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  18. When iterating through a collection variable using #{each var in array}, it would be helpful to have a sort by pipe
    Eg: #{each var in array | orderby var.property}

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Admin →
  19. We've been trying to ensure that any 'Step Templates' created in Octopus contain scripts/code (PowerShell) that exists within a package. That package is then referenced as part of the 'Step Template'.

    The problem we have with this is that as soon as the package is pushed, it then gets used in any new releases. This means that we have no opportunity to test this in Octopus prior to new releases in pipelines using it.

    It would be useful if within the 'Step Template' we could specify/fix the package version (or specify a range) used so that all other pipeline releases…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Admin →
  20. Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.

    I would like to be able to version octopus variables, this would include:
    - Who
    - When
    - When deployed
    - The ability to roll back/forward.

    At the moment we have to source control much of this type…

    68 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  7 comments  ·  Deployments  ·  Admin →